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 / Differential

What this profile constrains beyond DiagnosticReport. Anything not listed is unchanged from the base; muted type/cardinality values are the base's, shown for context.

Element Flags Card. Type Description & Constraints
DiagnosticReport Nexus EMR Diagnostic Report Core i
meta 0..1 Meta
source S 0..1 uri Identifies EMR instance & pipeline version the resource came from i
text S 0..1 Narrative Narrative i
extension 0..* Extension i
Slicing: value:url (open)
extension:reviewed S 0..1 Extension(Reviewed) Review acknowledgement (absent = unreviewed) i
extension:imagingModality S 0..* Extension(Imaging Modality Extension) Acquisition modality (imaging reports; repeats for PET-CT) i
identifier S 0..* Identifier Business identifier(s) for diagnostic report i
system 1..1 uri i
value 1..1 string i
status S 1..1 code Where the report is in its lifecycle i
Binding: diagnostic-report-status (required)
category S 0..* CodeableConcept Service category with raw code support i
code S 1..1 CodeableConcept Diagnostic report type with raw code support i
text S 1..1 string Human-readable report type description (required) i
subject S 1..1 Reference(Patient Profile) The subject of the report - usually a patient i
encounter S 0..1 Reference(Encounter Profile) Healthcare event when report was generated i
effective[x] S 1..1 dateTime, Period i
issued 0..1 instant DateTime report was released i
result 0..* Reference(Observation Profile) Observations that are part of this report i
imagingStudy 0..* Reference(ImagingStudy) i
conclusion 0..1 string i
conclusionCode 0..* CodeableConcept Codes for the clinical conclusion i
Binding: clinical-findings (example)
presentedForm 0..* Attachment i
contentType 1..1 code Mime type of the content (e.g., application/pdf)
data 0..1 base64Binary Data inline, base64 encoded i