HL7 FHIR Implementation Guide: ZM-Core Release 1 - Zambia
​0.1.0 - Zambia flag

HL7 FHIR Implementation Guide: ZM-Core Release 1 - Zambia - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: ZM-Core Diagnostic Report Profile

Official URL: http://hapi.moh.gov.zm/fhir/StructureDefinition/zm-core-diagnostic-report Version: 0.1.0
Active as of 2026-08-12 Computable Name: ZMCoreDiagnosticReport

Zambia diagnostic report profile for laboratory, imaging, pathology, and other diagnostic services.

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and their representations.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DiagnosticReport C 0..* DiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
Constraints: dgr-1
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contained 0..* Resource Contained, inline Resources
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
.... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
.... system SΣ 1..1 uri The namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣC 1..1 string The value that is unique
Example General: 123456
... basedOn S 1..* Reference(ZM-Core Service Request Profile) What was requested
... status ?!SΣ 1..1 code registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
... category SΣ 1..* CodeableConcept Service category
Binding: DiagnosticServiceSectionCodes (example): HL7 V2 table 0074
... code SΣ 1..1 CodeableConcept Name/Code for this diagnostic report
Binding: LOINCDiagnosticReportCodes (preferred): LOINC Codes for Diagnostic Reports
... subject SΣ 1..1 Reference(ZM-Core Patient Profile | ZM-Core Recipient Group Profile | Device | ZM-Core Location Profile | ZM-Core Organization Profile | ZM-Core Practitioner Profile | ZM-Core Medication Profile | Substance | BiologicallyDerivedProduct) The subject of the report - usually, but not always, the patient
... encounter SΣ 0..1 Reference(ZM-Core Encounter Profile) Health care event when test ordered
... effective[x] SΣ 1..1 Clinically relevant time/time-period for report
.... effectiveDateTime dateTime
.... effectivePeriod Period
... issued SΣ 1..1 instant DateTime this version was made
... performer SΣ 1..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Responsible Diagnostic Service
... resultsInterpreter SΣ 0..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Primary result interpreter
... specimen S 0..* Reference(ZM-Core Specimen Profile) Specimens this report is based on
... result SC 0..* Reference(ZM-Core Observation Profile) Observations
... note S 0..* Annotation Comments about the diagnostic report
... study S 0..* Reference(GenomicStudy | ImagingStudy) Reference to full details of an analysis associated with the diagnostic report
... supportingInfo S 0..* BackboneElement Additional information supporting the diagnostic report
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... type 1..1 CodeableConcept Supporting information role code
Binding: hl7VS-VS-observationType (example): The code value for the role of the supporting information in the diagnostic report.
.... reference 1..1 Reference(Procedure | Observation | DiagnosticReport | Citation) Supporting information reference
... media SΣ 0..* BackboneElement Key images or data associated with this report
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... link Σ 1..1 Reference(DocumentReference) Reference to the image or data source
... composition SC 0..1 Reference(Composition) Reference to a Composition resource for the DiagnosticReport structure
... conclusion S 0..1 markdown Clinical conclusion (interpretation) of test results
... conclusionCode S 0..* CodeableConcept Codes for the clinical conclusion of test results
Binding: SNOMEDCTClinicalFindings (example): SNOMED CT Clinical Findings
... presentedForm S 0..* Attachment Entire report as issued

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
DiagnosticReport.identifier.​use Base required IdentifierUse 📍5.0.0 FHIR Std.
DiagnosticReport.status Base required Diagnostic Report Status 📍5.0.0 FHIR Std.
DiagnosticReport.category Base example Diagnostic Service Section Codes 📍5.0.0 FHIR Std.
DiagnosticReport.code Base preferred LOINC Diagnostic Report Codes 📍5.0.0 FHIR Std.
DiagnosticReport.supportingInfo.​type Base example hl7VS-VS-observationType 📦3.0.0 THO v7.1
DiagnosticReport.conclusionCode Base example SNOMED CT Clinical Findings 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
dgr-1 error DiagnosticReport When a Composition is referenced in `Diagnostic.composition`, all Observation resources referenced in `Composition.entry` must also be referenced in `Diagnostic.entry` or in the references Observations in `Observation.hasMember` composition.exists() implies (composition.resolve().section.entry.reference.where(resolve() is Observation) in (result.reference|result.reference.resolve().hasMember.reference))
dom-2 error DiagnosticReport If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error DiagnosticReport If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice DiagnosticReport A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DiagnosticReport 0..* DiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
... identifier S 1..* Identifier Business identifier for report
.... system S 1..1 uri The namespace for the identifier value
.... value S 1..1 string The value that is unique
... basedOn S 1..* Reference(ZM-Core Service Request Profile) What was requested
... status S 1..1 code registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
... code S 1..1 CodeableConcept Name/Code for this diagnostic report
... subject S 1..1 Reference(ZM-Core Patient Profile | ZM-Core Recipient Group Profile | Device | ZM-Core Location Profile | ZM-Core Organization Profile | ZM-Core Practitioner Profile | ZM-Core Medication Profile | Substance | BiologicallyDerivedProduct) The subject of the report - usually, but not always, the patient
... encounter S 0..1 Reference(ZM-Core Encounter Profile) Health care event when test ordered
... effective[x] S 1..1 dateTime, Period Clinically relevant time/time-period for report
... issued S 1..1 instant DateTime this version was made
... performer S 1..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Responsible Diagnostic Service
... resultsInterpreter S 0..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Primary result interpreter
... specimen S 0..* Reference(ZM-Core Specimen Profile) Specimens this report is based on
... result S 0..* Reference(ZM-Core Observation Profile) Observations
... note S 0..* Annotation Comments about the diagnostic report
... study S 0..* Reference(GenomicStudy | ImagingStudy) Reference to full details of an analysis associated with the diagnostic report
... supportingInfo S 0..* BackboneElement Additional information supporting the diagnostic report
... media S 0..* BackboneElement Key images or data associated with this report
... composition S 0..1 Reference(Composition) Reference to a Composition resource for the DiagnosticReport structure
... conclusion S 0..1 markdown Clinical conclusion (interpretation) of test results
... conclusionCode S 0..* CodeableConcept Codes for the clinical conclusion of test results
... presentedForm S 0..* Attachment Entire report as issued

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DiagnosticReport C 0..* DiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
Constraints: dgr-1
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: AllLanguages (required): IETF language tag for a human language
Additional BindingsPurpose
CommonLanguages Starter
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
... identifier SΣ 1..* Identifier Business identifier for report
.... id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
.... type Σ 0..1 CodeableConcept Description of identifier
Binding: IdentifierTypeCodes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
.... system SΣ 1..1 uri The namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣC 1..1 string The value that is unique
Example General: 123456
.... period Σ 0..1 Period Time period when id is/was valid for use
.... assigner Σ 0..1 Reference(Organization) Organization that issued id (may be just text)
... basedOn S 1..* Reference(ZM-Core Service Request Profile) What was requested
... status ?!SΣ 1..1 code registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
... category SΣ 1..* CodeableConcept Service category
Binding: DiagnosticServiceSectionCodes (example): HL7 V2 table 0074
... code SΣ 1..1 CodeableConcept Name/Code for this diagnostic report
Binding: LOINCDiagnosticReportCodes (preferred): LOINC Codes for Diagnostic Reports
... subject SΣ 1..1 Reference(ZM-Core Patient Profile | ZM-Core Recipient Group Profile | Device | ZM-Core Location Profile | ZM-Core Organization Profile | ZM-Core Practitioner Profile | ZM-Core Medication Profile | Substance | BiologicallyDerivedProduct) The subject of the report - usually, but not always, the patient
... encounter SΣ 0..1 Reference(ZM-Core Encounter Profile) Health care event when test ordered
... effective[x] SΣ 1..1 Clinically relevant time/time-period for report
.... effectiveDateTime dateTime
.... effectivePeriod Period
... issued SΣ 1..1 instant DateTime this version was made
... performer SΣ 1..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Responsible Diagnostic Service
... resultsInterpreter SΣ 0..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Primary result interpreter
... specimen S 0..* Reference(ZM-Core Specimen Profile) Specimens this report is based on
... result SC 0..* Reference(ZM-Core Observation Profile) Observations
... note S 0..* Annotation Comments about the diagnostic report
... study S 0..* Reference(GenomicStudy | ImagingStudy) Reference to full details of an analysis associated with the diagnostic report
... supportingInfo S 0..* BackboneElement Additional information supporting the diagnostic report
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... type 1..1 CodeableConcept Supporting information role code
Binding: hl7VS-VS-observationType (example): The code value for the role of the supporting information in the diagnostic report.
.... reference 1..1 Reference(Procedure | Observation | DiagnosticReport | Citation) Supporting information reference
... media SΣ 0..* BackboneElement Key images or data associated with this report
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... comment 0..1 string Comment about the image or data (e.g. explanation)
.... link Σ 1..1 Reference(DocumentReference) Reference to the image or data source
... composition SC 0..1 Reference(Composition) Reference to a Composition resource for the DiagnosticReport structure
... conclusion S 0..1 markdown Clinical conclusion (interpretation) of test results
... conclusionCode S 0..* CodeableConcept Codes for the clinical conclusion of test results
Binding: SNOMEDCTClinicalFindings (example): SNOMED CT Clinical Findings
... presentedForm S 0..* Attachment Entire report as issued

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
DiagnosticReport.language Base required All Languages 📍5.0.0 FHIR Std.
DiagnosticReport.identifier.​use Base required IdentifierUse 📍5.0.0 FHIR Std.
DiagnosticReport.identifier.​type Base extensible Identifier Type Codes 📍5.0.0 FHIR Std.
DiagnosticReport.status Base required Diagnostic Report Status 📍5.0.0 FHIR Std.
DiagnosticReport.category Base example Diagnostic Service Section Codes 📍5.0.0 FHIR Std.
DiagnosticReport.code Base preferred LOINC Diagnostic Report Codes 📍5.0.0 FHIR Std.
DiagnosticReport.supportingInfo.​type Base example hl7VS-VS-observationType 📦3.0.0 THO v7.1
DiagnosticReport.conclusionCode Base example SNOMED CT Clinical Findings 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
dgr-1 error DiagnosticReport When a Composition is referenced in `Diagnostic.composition`, all Observation resources referenced in `Composition.entry` must also be referenced in `Diagnostic.entry` or in the references Observations in `Observation.hasMember` composition.exists() implies (composition.resolve().section.entry.reference.where(resolve() is Observation) in (result.reference|result.reference.resolve().hasMember.reference))
dom-2 error DiagnosticReport If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error DiagnosticReport If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice DiagnosticReport A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DiagnosticReport C 0..* DiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
Constraints: dgr-1
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contained 0..* Resource Contained, inline Resources
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
.... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
.... system SΣ 1..1 uri The namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣC 1..1 string The value that is unique
Example General: 123456
... basedOn S 1..* Reference(ZM-Core Service Request Profile) What was requested
... status ?!SΣ 1..1 code registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
... category SΣ 1..* CodeableConcept Service category
Binding: DiagnosticServiceSectionCodes (example): HL7 V2 table 0074
... code SΣ 1..1 CodeableConcept Name/Code for this diagnostic report
Binding: LOINCDiagnosticReportCodes (preferred): LOINC Codes for Diagnostic Reports
... subject SΣ 1..1 Reference(ZM-Core Patient Profile | ZM-Core Recipient Group Profile | Device | ZM-Core Location Profile | ZM-Core Organization Profile | ZM-Core Practitioner Profile | ZM-Core Medication Profile | Substance | BiologicallyDerivedProduct) The subject of the report - usually, but not always, the patient
... encounter SΣ 0..1 Reference(ZM-Core Encounter Profile) Health care event when test ordered
... effective[x] SΣ 1..1 Clinically relevant time/time-period for report
.... effectiveDateTime dateTime
.... effectivePeriod Period
... issued SΣ 1..1 instant DateTime this version was made
... performer SΣ 1..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Responsible Diagnostic Service
... resultsInterpreter SΣ 0..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Primary result interpreter
... specimen S 0..* Reference(ZM-Core Specimen Profile) Specimens this report is based on
... result SC 0..* Reference(ZM-Core Observation Profile) Observations
... note S 0..* Annotation Comments about the diagnostic report
... study S 0..* Reference(GenomicStudy | ImagingStudy) Reference to full details of an analysis associated with the diagnostic report
... supportingInfo S 0..* BackboneElement Additional information supporting the diagnostic report
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... type 1..1 CodeableConcept Supporting information role code
Binding: hl7VS-VS-observationType (example): The code value for the role of the supporting information in the diagnostic report.
.... reference 1..1 Reference(Procedure | Observation | DiagnosticReport | Citation) Supporting information reference
... media SΣ 0..* BackboneElement Key images or data associated with this report
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... link Σ 1..1 Reference(DocumentReference) Reference to the image or data source
... composition SC 0..1 Reference(Composition) Reference to a Composition resource for the DiagnosticReport structure
... conclusion S 0..1 markdown Clinical conclusion (interpretation) of test results
... conclusionCode S 0..* CodeableConcept Codes for the clinical conclusion of test results
Binding: SNOMEDCTClinicalFindings (example): SNOMED CT Clinical Findings
... presentedForm S 0..* Attachment Entire report as issued

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
DiagnosticReport.identifier.​use Base required IdentifierUse 📍5.0.0 FHIR Std.
DiagnosticReport.status Base required Diagnostic Report Status 📍5.0.0 FHIR Std.
DiagnosticReport.category Base example Diagnostic Service Section Codes 📍5.0.0 FHIR Std.
DiagnosticReport.code Base preferred LOINC Diagnostic Report Codes 📍5.0.0 FHIR Std.
DiagnosticReport.supportingInfo.​type Base example hl7VS-VS-observationType 📦3.0.0 THO v7.1
DiagnosticReport.conclusionCode Base example SNOMED CT Clinical Findings 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
dgr-1 error DiagnosticReport When a Composition is referenced in `Diagnostic.composition`, all Observation resources referenced in `Composition.entry` must also be referenced in `Diagnostic.entry` or in the references Observations in `Observation.hasMember` composition.exists() implies (composition.resolve().section.entry.reference.where(resolve() is Observation) in (result.reference|result.reference.resolve().hasMember.reference))
dom-2 error DiagnosticReport If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error DiagnosticReport If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice DiagnosticReport A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

Differential View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DiagnosticReport 0..* DiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
... identifier S 1..* Identifier Business identifier for report
.... system S 1..1 uri The namespace for the identifier value
.... value S 1..1 string The value that is unique
... basedOn S 1..* Reference(ZM-Core Service Request Profile) What was requested
... status S 1..1 code registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
... code S 1..1 CodeableConcept Name/Code for this diagnostic report
... subject S 1..1 Reference(ZM-Core Patient Profile | ZM-Core Recipient Group Profile | Device | ZM-Core Location Profile | ZM-Core Organization Profile | ZM-Core Practitioner Profile | ZM-Core Medication Profile | Substance | BiologicallyDerivedProduct) The subject of the report - usually, but not always, the patient
... encounter S 0..1 Reference(ZM-Core Encounter Profile) Health care event when test ordered
... effective[x] S 1..1 dateTime, Period Clinically relevant time/time-period for report
... issued S 1..1 instant DateTime this version was made
... performer S 1..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Responsible Diagnostic Service
... resultsInterpreter S 0..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Primary result interpreter
... specimen S 0..* Reference(ZM-Core Specimen Profile) Specimens this report is based on
... result S 0..* Reference(ZM-Core Observation Profile) Observations
... note S 0..* Annotation Comments about the diagnostic report
... study S 0..* Reference(GenomicStudy | ImagingStudy) Reference to full details of an analysis associated with the diagnostic report
... supportingInfo S 0..* BackboneElement Additional information supporting the diagnostic report
... media S 0..* BackboneElement Key images or data associated with this report
... composition S 0..1 Reference(Composition) Reference to a Composition resource for the DiagnosticReport structure
... conclusion S 0..1 markdown Clinical conclusion (interpretation) of test results
... conclusionCode S 0..* CodeableConcept Codes for the clinical conclusion of test results
... presentedForm S 0..* Attachment Entire report as issued

doco Documentation for this format

Snapshot ViewView

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DiagnosticReport C 0..* DiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
Constraints: dgr-1
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: AllLanguages (required): IETF language tag for a human language
Additional BindingsPurpose
CommonLanguages Starter
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
... identifier SΣ 1..* Identifier Business identifier for report
.... id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
.... type Σ 0..1 CodeableConcept Description of identifier
Binding: IdentifierTypeCodes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
.... system SΣ 1..1 uri The namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣC 1..1 string The value that is unique
Example General: 123456
.... period Σ 0..1 Period Time period when id is/was valid for use
.... assigner Σ 0..1 Reference(Organization) Organization that issued id (may be just text)
... basedOn S 1..* Reference(ZM-Core Service Request Profile) What was requested
... status ?!SΣ 1..1 code registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
... category SΣ 1..* CodeableConcept Service category
Binding: DiagnosticServiceSectionCodes (example): HL7 V2 table 0074
... code SΣ 1..1 CodeableConcept Name/Code for this diagnostic report
Binding: LOINCDiagnosticReportCodes (preferred): LOINC Codes for Diagnostic Reports
... subject SΣ 1..1 Reference(ZM-Core Patient Profile | ZM-Core Recipient Group Profile | Device | ZM-Core Location Profile | ZM-Core Organization Profile | ZM-Core Practitioner Profile | ZM-Core Medication Profile | Substance | BiologicallyDerivedProduct) The subject of the report - usually, but not always, the patient
... encounter SΣ 0..1 Reference(ZM-Core Encounter Profile) Health care event when test ordered
... effective[x] SΣ 1..1 Clinically relevant time/time-period for report
.... effectiveDateTime dateTime
.... effectivePeriod Period
... issued SΣ 1..1 instant DateTime this version was made
... performer SΣ 1..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Responsible Diagnostic Service
... resultsInterpreter SΣ 0..* Reference(ZM-Core Practitioner Profile | ZM-Core Practitioner Role Profile | ZM-Core Organization Profile | CareTeam) Primary result interpreter
... specimen S 0..* Reference(ZM-Core Specimen Profile) Specimens this report is based on
... result SC 0..* Reference(ZM-Core Observation Profile) Observations
... note S 0..* Annotation Comments about the diagnostic report
... study S 0..* Reference(GenomicStudy | ImagingStudy) Reference to full details of an analysis associated with the diagnostic report
... supportingInfo S 0..* BackboneElement Additional information supporting the diagnostic report
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... type 1..1 CodeableConcept Supporting information role code
Binding: hl7VS-VS-observationType (example): The code value for the role of the supporting information in the diagnostic report.
.... reference 1..1 Reference(Procedure | Observation | DiagnosticReport | Citation) Supporting information reference
... media SΣ 0..* BackboneElement Key images or data associated with this report
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... comment 0..1 string Comment about the image or data (e.g. explanation)
.... link Σ 1..1 Reference(DocumentReference) Reference to the image or data source
... composition SC 0..1 Reference(Composition) Reference to a Composition resource for the DiagnosticReport structure
... conclusion S 0..1 markdown Clinical conclusion (interpretation) of test results
... conclusionCode S 0..* CodeableConcept Codes for the clinical conclusion of test results
Binding: SNOMEDCTClinicalFindings (example): SNOMED CT Clinical Findings
... presentedForm S 0..* Attachment Entire report as issued

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
DiagnosticReport.language Base required All Languages 📍5.0.0 FHIR Std.
DiagnosticReport.identifier.​use Base required IdentifierUse 📍5.0.0 FHIR Std.
DiagnosticReport.identifier.​type Base extensible Identifier Type Codes 📍5.0.0 FHIR Std.
DiagnosticReport.status Base required Diagnostic Report Status 📍5.0.0 FHIR Std.
DiagnosticReport.category Base example Diagnostic Service Section Codes 📍5.0.0 FHIR Std.
DiagnosticReport.code Base preferred LOINC Diagnostic Report Codes 📍5.0.0 FHIR Std.
DiagnosticReport.supportingInfo.​type Base example hl7VS-VS-observationType 📦3.0.0 THO v7.1
DiagnosticReport.conclusionCode Base example SNOMED CT Clinical Findings 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
dgr-1 error DiagnosticReport When a Composition is referenced in `Diagnostic.composition`, all Observation resources referenced in `Composition.entry` must also be referenced in `Diagnostic.entry` or in the references Observations in `Observation.hasMember` composition.exists() implies (composition.resolve().section.entry.reference.where(resolve() is Observation) in (result.reference|result.reference.resolve().hasMember.reference))
dom-2 error DiagnosticReport If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error DiagnosticReport If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error DiagnosticReport If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice DiagnosticReport A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

 

Other representations of profile: CSV, Excel, Schematron