Scope and Usage

The DkCoreDiagnosticReport profile is used for diagnostic reports communicated within the Danish healthcare sector. Several use cases exist:

• Laboratory reports
• Personal health monitoring reports
• Other reports conveying observations between healthcare providers

The most typical is the laboratory report used to convey the laboratory’s response to a request for one or more analyses. It represents the report at a specific point in time and provides the overall context for the results produced. The report contains information about the report itself, the subject, and the specimen(s) on which the analyses are based.

In this case, a DiagnosticReport serves as the primary structure that links the requested analyses, the underlying specimens, and the resulting observations into a coherent laboratory response.

In other use cases, the DiagnosticReport is still a coherent report of resulting observations. However, these use cases are typically characterized by more relaxed requirements than within laboratory medicine.

Identifier

In Denmark, traditional laboratory reports such as MedCom's RPT01, repeat the requisition number in the laboratory report to ensure traceability. In FHIR, it is more consistent with the standard to use DiagnosticReport.basedOn to reference the actual requisition. As a result, HL7 Denmark recommends not repeating the requisition number as a DiagnosticReport.identifier.

In Danish laboratories, a laboratory report is sometimes assigned a unique identifier that is not the requisition number. This practice is especially useful when more than one report is associated with a single requisition. This is an example of a business identifier associated with the report itself. As such, it could be relevant to express as a DiagnosticReport.identifier.

Status Codes

The DiagnosticReport resource must contain the status of the report and use the required FHIR ValueSet. For all new use cases this is the only requirement.

However, if legacy data requires a mapping to and from the MedCom standard for laboratory results (RPT01/XRPT01), the following codes should be considered equivalent:

• registered: As soon as the specimen is received by the laboratory, a DiagnosticReport is created with the status 'registered'. This reflects that the order has entered the laboratory workflow and initial processing has begun. This corresponds to MedCom's 'modtaget'.
• partial: The status 'partial' is used when some, but not all, Observations within the DiagnosticReport have been finalized. At least one Observation result must still be pending for the status to remain 'partial'. This corresponds to MedCom's 'delsvar'.
• final: When all observations included in the DiagnosticReport have completed processing and all results are available, the status is set to 'final'. This represents the finalization of the entire laboratory response, corresponding to MedCom’s 'komplet_svar'.
• amended: If a previously finalized DiagnosticReport is updated because one or more referenced results have been corrected, the status becomes 'amended'. This ensures that receivers are aware that a new version replaces an earlier final report. There is no single corresponding code in MedCom's laboratory standards on the entire report. Nevertheless, to ensure FHIR compliance, the 'amended' code should be used as described here.

In a MedCom context, there are several ways of showing that a report has corrected results, but only at the result level. In FHIR, these results are Observations that may be referred to in DiagnosticReport.result.

Category

The category is used to classify the report. It is divided into three distinct slices: studyType, specialty, and danishSpecialty. The first two are derived directly from the specification of laboratory reports from HL7 Europe, and they should only be used for laboratory reports:

• studyType: A classification of the type of tests or services performed, grouped into clinically meaningful categories. It represents a typology of test results rather than the laboratory itself.
• specialty: Describes the clinical or professional domain of the laboratory that produced the results. It reflects the specific area of laboratory expertise that executed the tests (e.g., microbiology, chemistry, or hematology).

The third category is Danish Specialties as expressed in Clinical Speciality in SOR (Sundhedsvæsenets Organisationsregister) excluding the Laboratory specialities since they are already expressed in the speciality-slice. These may be used for non-laboratory use cases as needed.

Code

DiagnosticReport.code may hold different values. In the HL7 Europe laboratory standard, the code 'laboratory report' is always used. To support common Danish use cases, the value set includes two more valid values:

• 'personal health monitoring report' for collections of data produced by the patients themselves, typically in telehealth projects.
• 'progress note' for clinical situations where a collection of observation results originates from an encounter and needs to be communicated to other actors in the health sector. Examples could be acute nursing encounters where measurements are shared with the general practitioner. It could also be a general practitioner visit or hospital encounter where a number of different observations are made and need to be shared afterwards.

The value set is extensible. This means that if a specific use case can make use of either of the three codes already included in the value set, they shall be used. However, if a use case cannot meaningfully use either of the three cades, the value set may be extended. To ensure consistency, HL7 Denmark recommends using LOINC document codes for such additional codes.

Note that if a general practitioner visit originates in a report containing only laboratory results, it is recommended to use the code 'laboratory-report'. To differentiate from laboratory reports made in laboratories, use an appropriate category instead e.g. ´408443003 almen lægepraksis´.

Other documentation about attributes

Note that different timestamps are allowed. Match them to your specific use case. MedCom's laboratory report uses 'brevDannetTid'. In this case, DiagnosticReport.issued is recommended as the equivalent. For MedCom's 'svarTid', using DiagnosticReport.effectiveDateTime is recommended.

• Key Elements Table
• Differential Table
• Snapshot Table
• Statistics/References
• All

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
DiagnosticReport		0..*	DiagnosticReport	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
basedOn		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | Danish Core Person ServiceRequest Profile)	What was requested
status	?!Σ	1..1	code	registered | partial | preliminary | final + Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
Slices for category	Σ	0..*	CodeableConcept	Service category Slice: Unordered, Open by value:$this Binding: DiagnosticServiceSectionCodes (example): Codes for diagnostic service sections.
category:studyType	Σ	0..*	CodeableConcept	The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Binding: DK Core Laboratory study types (required)
category:specialty	Σ	0..*	CodeableConcept	The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Binding: SNOMED CT Laboratory Specialities (required)
category:danishSpecialty	Σ	0..*	CodeableConcept	The clinical domain of a Danish practise setting in which a DiagnosticReport is produced Binding: DK SOR Practice Setting Code excluding laboratory codes (required)
code	Σ	1..1	CodeableConcept	Name/Code for this diagnostic report Binding: DK Core LOINC Diagnostic Document Types (extensible)
subject	Σ	1..1	Reference(Danish Core Patient Profile | Group | Danish Core Location Profile | Device)	The subject of the report - usually, but not always, the patient
encounter	Σ	0..1	Reference(Danish Core Encounter Profile)	Health care event when test ordered
performer	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Responsible Diagnostic Service
resultsInterpreter	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Primary result interpreter
result		0..*	Reference(Danish Core Observation Profile)	Observations
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
DiagnosticReport.status	Base	required	DiagnosticReportStatus	📍4.0.1	FHIR Std.
DiagnosticReport.category	Base	example	Diagnostic Service Section Codes	📍4.0.1	FHIR Std.
DiagnosticReport.category:studyType	Base	required	DK Core Laboratory study types	📦3.7.0	This IG
DiagnosticReport.category:specialty	Base	required	SNOMED CT Laboratory Specialities	📦3.7.0	This IG
DiagnosticReport.category:danishSpecialty	Base	required	DK SOR Practice Setting Code excluding laboratory codes	📦3.7.0	This IG
DiagnosticReport.code	Base	extensible	DK Core LOINC Diagnostic Document Types	📦3.7.0	This IG

Constraints

Id	Grade	Path(s)	Description	Expression
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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(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()

This structure is derived from DiagnosticReport

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
DiagnosticReport		0..*	DiagnosticReport	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
basedOn		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | Danish Core Person ServiceRequest Profile)	What was requested
Slices for category		0..*	CodeableConcept	Service category Slice: Unordered, Open by value:$this
category:studyType		0..*	CodeableConcept	The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Binding: DK Core Laboratory study types (required)
category:specialty		0..*	CodeableConcept	The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Binding: SNOMED CT Laboratory Specialities (required)
category:danishSpecialty		0..*	CodeableConcept	The clinical domain of a Danish practise setting in which a DiagnosticReport is produced Binding: DK SOR Practice Setting Code excluding laboratory codes (required)
code		1..1	CodeableConcept	Name/Code for this diagnostic report Binding: DK Core LOINC Diagnostic Document Types (extensible)
subject		1..1	Reference(Danish Core Patient Profile | Group | Danish Core Location Profile | Device)	The subject of the report - usually, but not always, the patient
encounter		0..1	Reference(Danish Core Encounter Profile)	Health care event when test ordered
performer		0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Responsible Diagnostic Service
resultsInterpreter		0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Primary result interpreter
result		0..*	Reference(Danish Core Observation Profile)	Observations
Documentation for this format

Terminology Bindings (Differential)

Path	Status	Usage	ValueSet	Version	Source
DiagnosticReport.category:studyType	Base	required	DK Core Laboratory study types	📦3.7.0	This IG
DiagnosticReport.category:specialty	Base	required	SNOMED CT Laboratory Specialities	📦3.7.0	This IG
DiagnosticReport.category:danishSpecialty	Base	required	DK SOR Practice Setting Code excluding laboratory codes	📦3.7.0	This IG
DiagnosticReport.code	Base	extensible	DK Core LOINC Diagnostic Document Types	📦3.7.0	This IG

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
DiagnosticReport		0..*	DiagnosticReport	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
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: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
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	Σ	0..*	Identifier	Business identifier for report
basedOn		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | Danish Core Person ServiceRequest Profile)	What was requested
status	?!Σ	1..1	code	registered | partial | preliminary | final + Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
Slices for category	Σ	0..*	CodeableConcept	Service category Slice: Unordered, Open by value:$this Binding: DiagnosticServiceSectionCodes (example): Codes for diagnostic service sections.
category:studyType	Σ	0..*	CodeableConcept	The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Binding: DK Core Laboratory study types (required)
category:specialty	Σ	0..*	CodeableConcept	The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Binding: SNOMED CT Laboratory Specialities (required)
category:danishSpecialty	Σ	0..*	CodeableConcept	The clinical domain of a Danish practise setting in which a DiagnosticReport is produced Binding: DK SOR Practice Setting Code excluding laboratory codes (required)
code	Σ	1..1	CodeableConcept	Name/Code for this diagnostic report Binding: DK Core LOINC Diagnostic Document Types (extensible)
subject	Σ	1..1	Reference(Danish Core Patient Profile | Group | Danish Core Location Profile | Device)	The subject of the report - usually, but not always, the patient
encounter	Σ	0..1	Reference(Danish Core Encounter Profile)	Health care event when test ordered
effective[x]	Σ	0..1		Clinically relevant time/time-period for report
effectiveDateTime			dateTime
effectivePeriod			Period
issued	Σ	0..1	instant	DateTime this version was made
performer	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Responsible Diagnostic Service
resultsInterpreter	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Primary result interpreter
specimen		0..*	Reference(Specimen)	Specimens this report is based on
result		0..*	Reference(Danish Core Observation Profile)	Observations
imagingStudy		0..*	Reference(ImagingStudy)	Reference to full details of imaging associated with the diagnostic report
media	Σ	0..*	BackboneElement	Key images 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 (e.g. explanation)
link	Σ	1..1	Reference(Media)	Reference to the image source
conclusion		0..1	string	Clinical conclusion (interpretation) of test results
conclusionCode		0..*	CodeableConcept	Codes for the clinical conclusion of test results Binding: SNOMEDCTClinicalFindings (example): Diagnosis codes provided as adjuncts to the report.
presentedForm		0..*	Attachment	Entire report as issued
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
DiagnosticReport.language	Base	preferred	Common Languages	📍4.0.1	FHIR Std.
DiagnosticReport.status	Base	required	DiagnosticReportStatus	📍4.0.1	FHIR Std.
DiagnosticReport.category	Base	example	Diagnostic Service Section Codes	📍4.0.1	FHIR Std.
DiagnosticReport.category:studyType	Base	required	DK Core Laboratory study types	📦3.7.0	This IG
DiagnosticReport.category:specialty	Base	required	SNOMED CT Laboratory Specialities	📦3.7.0	This IG
DiagnosticReport.category:danishSpecialty	Base	required	DK SOR Practice Setting Code excluding laboratory codes	📦3.7.0	This IG
DiagnosticReport.code	Base	extensible	DK Core LOINC Diagnostic Document Types	📦3.7.0	This IG
DiagnosticReport.conclusionCode	Base	example	SNOMED CT Clinical Findings	📍4.0.1	FHIR Std.

Constraints

Id	Grade	Path(s)	Description	Expression
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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(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

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
DiagnosticReport		0..*	DiagnosticReport	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
basedOn		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | Danish Core Person ServiceRequest Profile)	What was requested
status	?!Σ	1..1	code	registered | partial | preliminary | final + Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
Slices for category	Σ	0..*	CodeableConcept	Service category Slice: Unordered, Open by value:$this Binding: DiagnosticServiceSectionCodes (example): Codes for diagnostic service sections.
category:studyType	Σ	0..*	CodeableConcept	The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Binding: DK Core Laboratory study types (required)
category:specialty	Σ	0..*	CodeableConcept	The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Binding: SNOMED CT Laboratory Specialities (required)
category:danishSpecialty	Σ	0..*	CodeableConcept	The clinical domain of a Danish practise setting in which a DiagnosticReport is produced Binding: DK SOR Practice Setting Code excluding laboratory codes (required)
code	Σ	1..1	CodeableConcept	Name/Code for this diagnostic report Binding: DK Core LOINC Diagnostic Document Types (extensible)
subject	Σ	1..1	Reference(Danish Core Patient Profile | Group | Danish Core Location Profile | Device)	The subject of the report - usually, but not always, the patient
encounter	Σ	0..1	Reference(Danish Core Encounter Profile)	Health care event when test ordered
performer	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Responsible Diagnostic Service
resultsInterpreter	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Primary result interpreter
result		0..*	Reference(Danish Core Observation Profile)	Observations
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
DiagnosticReport.status	Base	required	DiagnosticReportStatus	📍4.0.1	FHIR Std.
DiagnosticReport.category	Base	example	Diagnostic Service Section Codes	📍4.0.1	FHIR Std.
DiagnosticReport.category:studyType	Base	required	DK Core Laboratory study types	📦3.7.0	This IG
DiagnosticReport.category:specialty	Base	required	SNOMED CT Laboratory Specialities	📦3.7.0	This IG
DiagnosticReport.category:danishSpecialty	Base	required	DK SOR Practice Setting Code excluding laboratory codes	📦3.7.0	This IG
DiagnosticReport.code	Base	extensible	DK Core LOINC Diagnostic Document Types	📦3.7.0	This IG

Constraints

Id	Grade	Path(s)	Description	Expression
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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(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

This structure is derived from DiagnosticReport

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
DiagnosticReport		0..*	DiagnosticReport	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
basedOn		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | Danish Core Person ServiceRequest Profile)	What was requested
Slices for category		0..*	CodeableConcept	Service category Slice: Unordered, Open by value:$this
category:studyType		0..*	CodeableConcept	The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Binding: DK Core Laboratory study types (required)
category:specialty		0..*	CodeableConcept	The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Binding: SNOMED CT Laboratory Specialities (required)
category:danishSpecialty		0..*	CodeableConcept	The clinical domain of a Danish practise setting in which a DiagnosticReport is produced Binding: DK SOR Practice Setting Code excluding laboratory codes (required)
code		1..1	CodeableConcept	Name/Code for this diagnostic report Binding: DK Core LOINC Diagnostic Document Types (extensible)
subject		1..1	Reference(Danish Core Patient Profile | Group | Danish Core Location Profile | Device)	The subject of the report - usually, but not always, the patient
encounter		0..1	Reference(Danish Core Encounter Profile)	Health care event when test ordered
performer		0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Responsible Diagnostic Service
resultsInterpreter		0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Primary result interpreter
result		0..*	Reference(Danish Core Observation Profile)	Observations
Documentation for this format

Terminology Bindings (Differential)

Path	Status	Usage	ValueSet	Version	Source
DiagnosticReport.category:studyType	Base	required	DK Core Laboratory study types	📦3.7.0	This IG
DiagnosticReport.category:specialty	Base	required	SNOMED CT Laboratory Specialities	📦3.7.0	This IG
DiagnosticReport.category:danishSpecialty	Base	required	DK SOR Practice Setting Code excluding laboratory codes	📦3.7.0	This IG
DiagnosticReport.code	Base	extensible	DK Core LOINC Diagnostic Document Types	📦3.7.0	This IG

Snapshot View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
DiagnosticReport		0..*	DiagnosticReport	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
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: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
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	Σ	0..*	Identifier	Business identifier for report
basedOn		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | Danish Core Person ServiceRequest Profile)	What was requested
status	?!Σ	1..1	code	registered | partial | preliminary | final + Binding: DiagnosticReportStatus (required): The status of the diagnostic report.
Slices for category	Σ	0..*	CodeableConcept	Service category Slice: Unordered, Open by value:$this Binding: DiagnosticServiceSectionCodes (example): Codes for diagnostic service sections.
category:studyType	Σ	0..*	CodeableConcept	The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Binding: DK Core Laboratory study types (required)
category:specialty	Σ	0..*	CodeableConcept	The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Binding: SNOMED CT Laboratory Specialities (required)
category:danishSpecialty	Σ	0..*	CodeableConcept	The clinical domain of a Danish practise setting in which a DiagnosticReport is produced Binding: DK SOR Practice Setting Code excluding laboratory codes (required)
code	Σ	1..1	CodeableConcept	Name/Code for this diagnostic report Binding: DK Core LOINC Diagnostic Document Types (extensible)
subject	Σ	1..1	Reference(Danish Core Patient Profile | Group | Danish Core Location Profile | Device)	The subject of the report - usually, but not always, the patient
encounter	Σ	0..1	Reference(Danish Core Encounter Profile)	Health care event when test ordered
effective[x]	Σ	0..1		Clinically relevant time/time-period for report
effectiveDateTime			dateTime
effectivePeriod			Period
issued	Σ	0..1	instant	DateTime this version was made
performer	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Responsible Diagnostic Service
resultsInterpreter	Σ	0..*	Reference(Danish Core Practitioner Profile | Danish Core Organization Profile | Danish Core PractitionerRole Profile | CareTeam)	Primary result interpreter
specimen		0..*	Reference(Specimen)	Specimens this report is based on
result		0..*	Reference(Danish Core Observation Profile)	Observations
imagingStudy		0..*	Reference(ImagingStudy)	Reference to full details of imaging associated with the diagnostic report
media	Σ	0..*	BackboneElement	Key images 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 (e.g. explanation)
link	Σ	1..1	Reference(Media)	Reference to the image source
conclusion		0..1	string	Clinical conclusion (interpretation) of test results
conclusionCode		0..*	CodeableConcept	Codes for the clinical conclusion of test results Binding: SNOMEDCTClinicalFindings (example): Diagnosis codes provided as adjuncts to the report.
presentedForm		0..*	Attachment	Entire report as issued
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
DiagnosticReport.language	Base	preferred	Common Languages	📍4.0.1	FHIR Std.
DiagnosticReport.status	Base	required	DiagnosticReportStatus	📍4.0.1	FHIR Std.
DiagnosticReport.category	Base	example	Diagnostic Service Section Codes	📍4.0.1	FHIR Std.
DiagnosticReport.category:studyType	Base	required	DK Core Laboratory study types	📦3.7.0	This IG
DiagnosticReport.category:specialty	Base	required	SNOMED CT Laboratory Specialities	📦3.7.0	This IG
DiagnosticReport.category:danishSpecialty	Base	required	DK SOR Practice Setting Code excluding laboratory codes	📦3.7.0	This IG
DiagnosticReport.code	Base	extensible	DK Core LOINC Diagnostic Document Types	📦3.7.0	This IG
DiagnosticReport.conclusionCode	Base	example	SNOMED CT Clinical Findings	📍4.0.1	FHIR Std.

Constraints

Id	Grade	Path(s)	Description	Expression
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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(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()

This structure is derived from DiagnosticReport

Summary

Mandatory: 1 element

Structures

This structure refers to these other structures:

• Danish Core Person ServiceRequest Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-person-servicerequest)
• Danish Core Patient Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-patient)
• Danish Core Location Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-location)
• Danish Core Encounter Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-encounter)
• Danish Core Practitioner Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-practitioner)
• Danish Core Organization Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-organization)
• Danish Core PractitionerRole Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-practitioner-role)
• Danish Core Observation Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-observation)

Slices

This structure defines the following Slices:

• The element 1 is sliced based on the value of DiagnosticReport.category