DocumentReference Profile¶
| Canonical | ../StructureDefinition/nexus-emr-core-documentreference |
|---|---|
| Status | draft · 1.26.0 |
| Base | DocumentReference (constraint) |
| CQL primary code path | type — what this means |
| Source | FSH · JSON |
Nexus EMR profile for an ATTACHED DOCUMENT -- a clinical document that exists as a file:
scanned paper, incoming faxes, external consult letters received as PDF, signed consent forms,
patient-uploaded files. FHIR holds the metadata and clinical context; the bytes live in
document storage and are reached through content.attachment.url.
Examples
Conforming instances (each opens inside this tab):
- Allergy Consult Letter (challenge refuted) — The letter recording that a graded oral challenge refuted the previously reported penicillin allergy. It is the source the chart-update suggestion cites when proposing that the re…
- Anemia Consultation Document — Example document reference for anemia consultation note from April 8, 2025, carrying a reviewer's sign-off in the reviewed extension -- who acknowledged the document and when, sta…
- Cardiology Consult Letter (received) — An anticoagulation review that arrived as a file from outside the practice -- a DocumentReference rather than a Composition for exactly that reason. The quoted passage is reproduc…
- Consent Withdrawal Evidence Document — Scanned signed AI Scribe consent withdrawal form referenced as evidence from the AI Scribe item consent
- Hrm discharge summary 20260618 — Discharge summary following a four-day admission for community-acquired pneumonia.
- WSIB Form 8 (filed) — A WSIB Form 8 filled for a patient and filed on the chart, marked under nexus-form with the same slug as its template and carrying no mapping -- the filled values are in the file
- WSIB Form 8 Template (with field mapping) — The tenant-wide blank of WSIB Form 8 -- subject-less, marked under nexus-form-template, readonly because it is system-provisioned -- carrying the field mapping that pre-fills the …