Skip to content

DocumentReference Profile

Canonical../StructureDefinition/nexus-emr-core-documentreference
Statusdraft · 1.26.0
BaseDocumentReference (constraint)
CQL primary code pathtypewhat this means
SourceFSH · 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.

TypedFhir API / C#

The typed accessor surface DocumentReference exposes for DocumentReference — generated from this IG's compiled profile; each typed accessor has a validating raw-FHIR twin (xRaw) where marked. The three ports are parity-enforced.

class DocumentReference : ClinicalResourcegenerated source

Accessor Type Access Notes
EffectiveDate FuzzyDate? read-only The resource's effective date — the first present of this profile's date elements (precedence), normalized to the canonical FuzzyDatetime f…
Display string? read-only The resource's human headline — a coded concept's label, else a title / name, else undefined.
Status string? read/write Where the document reference is in its lifecycle
DocStatus string? read/write preliminary | final | amended | entered-in-error
Type Concept? read/write · raw twin Precise type of document (use category instead)
Category Concepts read/write · raw twin Document categorization (preferred over type)
Subject Reference? read/write · raw twin The patient the document is about
Date FuzzyDate? read/write When DocumentReference was created (not document date)
Author References read/write · raw twin Who wrote the document
Authenticator Reference? read/write · raw twin Practitioner who verified this document
Custodian Reference? read/write · raw twin Organization responsible for document maintenance
Description string? read/write Human-readable description of document content
SecurityLabel Concepts read/write · raw twin Document security-tags
Content Json[]? read/write Document attachment(s) -- submitted inline, stored as files, read back by URL