Skip to content

DiagnosticReport Profile

Canonical../StructureDefinition/nexus-emr-core-diagnosticreport
Statusdraft · 1.26.0
BaseDiagnosticReport (constraint)
SourceFSH · JSON

Defines the Nexus EMR FHIR profile for DiagnosticReport resources, based on CA-Core constraints, for aggregating diagnostic reports (e.g., Lab, Imaging) from multiple EMRs.

Elements / Key elements

The working view: must-support, required, modifier and sliced elements from the effective (snapshot) definition.

Element Flags Card. Type Description & Constraints
DiagnosticReport 0..* Nexus EMR Diagnostic Report Core i
Invariants: dom-2, dom-3, dom-4, dom-5, dom-6
meta 0..1 Meta Metadata about the resource
Invariants: ele-1
source S 0..1 uri Identifies EMR instance & pipeline version the resource came from i
Invariants: ele-1
implicitRules ?! 0..1 uri A set of rules under which this content was created i
Invariants: ele-1
text S 0..1 Narrative Narrative i
Invariants: ele-1
extension:reviewed S 0..1 Extension(Reviewed) Review acknowledgement (absent = unreviewed) i
Invariants: ele-1, ext-1
extension:imagingModality S 0..* Extension(Imaging Modality Extension) Acquisition modality (imaging reports; repeats for PET-CT) i
Invariants: ele-1, ext-1
identifier S 0..* Identifier Business identifier(s) for diagnostic report i
Invariants: ele-1
use ?! 0..1 code usual | official | temp | secondary | old (If known) i
Binding: identifier-use (required)
Invariants: ele-1
system 1..1 uri The namespace for the identifier value i
Invariants: ele-1
value 1..1 string The value that is unique i
Invariants: ele-1
status S ?! 1..1 code Where the report is in its lifecycle i
Binding: diagnostic-report-status (required)
Invariants: ele-1
category S 0..* CodeableConcept Service category with raw code support i
Binding: diagnostic-service-sections (example)
Invariants: ele-1
code S 1..1 CodeableConcept Diagnostic report type with raw code support i
Binding: report-codes (preferred)
Invariants: ele-1
text S 1..1 string Human-readable report type description (required) i
Invariants: ele-1
subject S 1..1 Reference(Patient Profile) The subject of the report - usually a patient i
Invariants: ele-1
encounter S 0..1 Reference(Encounter Profile) Healthcare event when report was generated i
Invariants: ele-1
effective[x] S 1..1 dateTime, Period Clinically relevant time/time-period for report i
Invariants: ele-1
media 0..* BackboneElement Key images associated with this report
Invariants: ele-1
link 1..1 Reference(Media) Reference to the image source
Invariants: ele-1
presentedForm 0..* Attachment Entire report as issued i
Invariants: ele-1
contentType 1..1 code Mime type of the content (e.g., application/pdf)
Binding: mimetypes (required)
Invariants: ele-1