DwDocumentReference

Purpose

Provides metadata about documents stored within the EMR. These will be documents from other sources and may include Consultation reports, discharge summaries etc.

idS Σ1..1id
id0..1string
extensionC0..*Extension
versionIdΣ0..1id
lastUpdatedΣ1..1instant
sourceΣ1..1uri
profileΣ0..*canonical(StructureDefinition)
securityΣ0..*CodingBinding
tagΣ0..*Coding
implicitRulesΣ ?!0..1uri
language0..1codeBinding
textS1..1Narrative
contained0..*Resource
ClinicianAnnotationS C0..1Extension(Annotation)
modifierExtension?! C0..*Extension
masterIdentifierΣ0..1Identifier
identifierS Σ1..1Identifier
statusΣ ?!1..1codeBinding
docStatusS Σ0..1codeBinding
typeS Σ0..1CodeableConceptBinding
id0..1string
extensionC0..*Extension
codingΣ0..*Coding
textS Σ0..1string
subjectS Σ C1..1Reference(DwPatient | DwPractitioner)
dateS Σ0..1instant
id0..1string
extensionC0..*Extension
referenceS Σ C0..1string
typeΣ0..1uriBinding
identifierΣ0..1Identifier
displayS Σ0..1string
authenticatorC0..1Reference(Organization | Practitioner | PractitionerRole)
custodianC0..1Reference(Organization)
id0..1string
extensionC0..*Extension
modifierExtensionΣ ?! C0..*Extension
codeΣ1..1codeBinding
targetΣ C1..1Reference(DocumentReference)
descriptionΣ0..1string
securityLabelΣ0..*CodeableConceptBinding
id0..1string
extensionC0..*Extension
modifierExtensionΣ ?! C0..*Extension
id0..1string
extensionC0..*Extension
contentTypeS Σ0..1codeBinding
languageΣ0..1codeBinding
dataS0..1base64Binary
urlS Σ0..1url
sizeS Σ0..1unsignedInt
hashS Σ0..1base64Binary
titleS Σ0..1string
creationS Σ0..1dateTime
formatΣ0..1CodingBinding
id0..1string
extensionC0..*Extension
modifierExtensionΣ ?! C0..*Extension
encounterS C0..*Reference(DwEncounter)
event0..*CodeableConcept
periodS Σ C0..1Period
facilityType0..1CodeableConcept
practiceSetting0..1CodeableConcept
sourcePatientInfoC0..1Reference(Patient)
relatedC0..*Reference(Resource)

Usage note

  • .docStatus This will reflect the status of the document within the EMR. When the workflow supports the various status codes they will be provided, otherwise the docStatus will be final.

    FHIR MA PSS CHR
    Preliminary Unsigned note/blue bar/unfinished note
    Final signed note/no blue bar
    Amended modified note
    Entered in Error deleted note

.category This will provide the Category of the Document within the EMR.

Bundle

DocumentReference

Examples

Example EMR
chr-on-west-DocumentReference-8001 CHR
ma-ma-schema-1-DocumentReference-12001 MA

CHR UI Navigation

The following table shows where each FHIR element comes from in CHR: the UI path a clinician follows to enter or view the data.

FHIR Path CHR Name CHR UI Navigation
DocumentReference.identifier File ID —
DocumentReference.docStatus Active / Archived Patients → select patient → chart → Files → Active/Archived toggle
DocumentReference.type Type (auto-classified from file name) Auto-classified from the file name — no dedicated Type field (keywords admission/discharge/consult/procedure map to fixed LOINC codes; otherwise left unset)
DocumentReference.type.text File Name Patients → select patient → chart → Files → file name
DocumentReference.category.text File Tags Patients → select patient → chart → Files → file tags rail
DocumentReference.subject Patient —
DocumentReference.date Date Added Patients → select patient → chart → Files → list → Date column
DocumentReference.author Uploaded By Patients → select patient → chart → Files → list → Author / Uploaded By column
DocumentReference.content.attachment.contentType File Type (auto-detected) Auto-detected from the uploaded file — no user input
DocumentReference.content.attachment.size File Size Patients → select patient → chart → Files → file details (shown on hover/preview)
DocumentReference.content.attachment.title File Name Patients → select patient → chart → Files → file name
DocumentReference.content.attachment.creation Date Added Patients → select patient → chart → Files → list → Date column
DocumentReference.context.encounter Linked Encounter Patients → select patient → chart → Files → row detail (only when the file was uploaded via an encounter's Attachments section)
DocumentReference.context.period Date Received —

MA UI Navigation

The following table shows where each FHIR element comes from in MA: the UI path a clinician follows to enter or view the data.

FHIR Path MA Name MA UI Navigation
DocumentReference.identifier Task / Report Identifier —
DocumentReference.docStatus Report Status (auto: Final) Auto-set to 'final' for every consultation report — no user input
DocumentReference.type Report Type (auto: Consult Note) Auto-set to LOINC 'Consult note' — no user input
DocumentReference.category Report Category Menu → Patients → select patient → Task Management (Consult / Result Copy / Message Copy category) → report task → category field
DocumentReference.subject Patient —
DocumentReference.date Observation / Report Date Menu → Patients → select patient → Task Management → report task → date field
DocumentReference.author Revising User Menu → Patients → select patient → Task Management → report task → assigned/revising user
DocumentReference.content.attachment.contentType Content Type (auto) Auto-set — no user input
DocumentReference.content.attachment.data Report Content Menu → Patients → select patient → Task Management → report task → observation results
DocumentReference.content.attachment.hash Content Hash (auto) Auto-computed from report content — no user input
DocumentReference.content.attachment.title Report Title Menu → Patients → select patient → Task Management → report task → search/title field
Dashboard → Imported Documents → import document (upload entry point)
DocumentReference.content.attachment.creation Report Creation Date Menu → Patients → select patient → Task Management → report task → date field
DocumentReference.context.encounter Linked Visit Menu → Patients → select patient → Task Management → report task (linked to a visit when the report date falls within a recorded visit, or via matching visit/task chain)