FHIR Document Resources in ESUS
ESUS implements the following resources for clinical and administrative documents:
| Resource | Purpose |
|---|---|
| DocumentReference | Metadata about a document and a pointer to its content |
| Composition | Structured clinical document (grouped sections) |
| DiagnosticReport | Lab, imaging, pathology, and other diagnostic reports |
| Media | Clinical audio, video, and images |
Document content (PDF, images, DICOM, etc.) is uploaded through the dedicated file-storage endpoints (/files/upload), and then referenced from a DocumentReference via content.attachment.url.
Document Lifecycle
- Upload the binary content to
/files/upload. - Create a
DocumentReference(orComposition,DiagnosticReport,Media) that points to the uploaded file. - Link the document to the relevant patient and encounter.
- Access through authorized reads; every access is audited.
Document Types
| Type | Typical resource |
|---|---|
| Clinical notes — progress, consult, H&P | DocumentReference + /files/upload |
| Structured clinical document | Composition |
| Lab, imaging, pathology reports | DiagnosticReport |
| Images and media | Media |
| Administrative (consent forms, referrals) | DocumentReference |
Common Standards
- HL7 CDA — Clinical Document Architecture.
- CCDA — Consolidated CDA.
- FHIR Documents — a
Compositionthat bundles references to other FHIR resources (typically packaged as aBundleof typedocument).