EHDS Logical Information Models
0.3.0 - qa-preview

EHDS Logical Information Models, published by Xt-EHR. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Xt-EHR/xt-ehr-common/ and changes regularly. See the Directory of published versions

Logical Model: Laboratory report model

Official URL: http://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSLaboratoryReport Version: 0.3.0
Draft as of 2026-02-09 Computable Name: EHDSLaboratoryReport

Laboratory result report model.

Usages:

  • This Logical Model is not used by any profiles in this Implementation Guide

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSLaboratoryReport 0..* EHDSDocument Laboratory report model

Elements defined in Ancestors:header, header, presentedForm
Instances of this logical model can be the target of a Reference
... header 1..1 Base Laboratory Report header
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 1..* Identifier Unique identifier of the document
.... author[x] 1..* Author(s) by whom the laboratory result report was authored.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 1..1 dateTime Date of finalising/issuing the document
.... status 1..1 CodeableConcept Status of the document
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
.... documentType 1..1 CodeableConcept Type of document at hand, e.g. 60591-5 Patient summary document.
Binding Description: (preferred): LOINC
.... documentTitle 1..1 string Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024'
.... period 0..1 Period Time of service that is being documented
.... version 0..1 string Business version of the document. The exact algorithm for versioning is decided by the producer/custodian
.... attestation 0..* Base Document attestation details
..... attester[x] 1..1 Attester who validated the document
...... attesterEHDSHealthProfessional EHDSHealthProfessional
...... attesterEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of the approval of the document by Attester
.... legalAuthentication 0..* Base Document legal authentication details
..... legalAuthenticator[x] 1..1 The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
...... legalAuthenticatorEHDSHealthProfessional EHDSHealthProfessional
...... legalAuthenticatorEHDSOrganisation EHDSOrganisation
..... datetime 1..1 dateTime Date and time when the document was authorised
.... eventType 0..* CodeableConcept Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.
Binding Description: (preferred): SNOMED CT
.... serviceSpecialty 0..* CodeableConcept Additional details about where the content was created (e.g. clinical specialty)
Binding Description: (preferred): SNOMED CT
.... custodian 0..1 EHDSOrganisation Organisation that is in charge of maintaining the document/report.
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... intendedRecipient[x] 0..* Intended recipient
.... intendedRecipientEHDSPatient EHDSPatient
.... intendedRecipientEHDSRelatedPerson EHDSRelatedPerson
.... intendedRecipientEHDSHealthProfessional EHDSHealthProfessional
.... intendedRecipientEHDSOrganisation EHDSOrganisation
.... intendedRecipientEHDSDevice EHDSDevice
.... orderInformation 0..* Base Order Information (Laboratory Result Report could respond to multiple test orders)
..... orderId 1..* Identifier An identifier of the laboratory test order. Laboratory Result Report may respond to multiple orders.
..... orderDateAndTime 0..1 dateTime Date and time of the order placement.
..... orderPlacer[x] 0..1 The person/organisation "authorised" to place the order. Order placer could be either a health professional, health professional organisation or the patient himself.
...... orderPlacerEHDSHealthProfessional EHDSHealthProfessional
...... orderPlacerEHDSOrganisation EHDSOrganisation
...... orderPlacerEHDSPatient EHDSPatient
..... orderReason[x] 0..* An explanation or justification for why this service is being requested in coded form.
Binding Description: (preferred): SNOMED CT
...... orderReasonCodeableConcept CodeableConcept
...... orderReasonEHDSCondition EHDSCondition
...... orderReasonEHDSObservation EHDSObservation
...... orderReasonString string
..... clinicalQuestion 0..1 string Specification of clinical question (goal of the investigation) to be answered by the laboratory investigation.
.... supportingInformation 0..1 Base Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs).' This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.
..... observation 0..* EHDSObservation Clinical findings and other observations.
..... condition 0..* EHDSCondition Condition that may influence the service or result interpretation.
..... medicationAdministration 0..* EHDSMedicationAdministration Medication administered before ordering the service.
..... sexForClinicalUse 0..1 CodeableConcept A Sex Parameter for Clinical Use is a parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.. This property is intended for use in clinical decision making, and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population
Binding Description: (preferred): HL7 sex-parameter-for-clinical-use
..... vaccination 0..* EHDSImmunisation Vaccination history of the patient.
..... otherSupportingInformation 0..* Resource Any other type of relevant supporting information
.... specimen 0..* EHDSSpecimen Specimen information
.... serviceRequest 0..* EHDSServiceRequest Specification of requested service or services
.... resultData 1..1 Base Laboratory report result data
..... commentsInterpretationAndRecommendations 0..* Narrative Narrative Comments, such as a textual interpretation or advice accompanying the result report, for example.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... laboratoryTestResults 0..* EHDSLaboratoryObservation Observation details (report could consist of multiple observations)
... attachments 0..* EHDSAttachment Report attachments

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
EHDSLaboratoryReport.​header.language Base preferred Not State Unknown
EHDSLaboratoryReport.​header.documentType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.eventType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.serviceSpecialty Base preferred Not State Unknown
EHDSLaboratoryReport.​body.orderInformation.​orderReason[x] Base preferred Not State Unknown
EHDSLaboratoryReport.​body.supportingInformation.​sexForClinicalUse Base preferred Not State Unknown

This structure is derived from EHDSDocument

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSLaboratoryReport 0..* EHDSDocument Laboratory report model

Elements defined in Ancestors:header, header, presentedForm
Instances of this logical model can be the target of a Reference
... header 1..1 Base Laboratory Report header
.... author[x] 1..* EHDSHealthProfessional, EHDSOrganisation, EHDSDevice Author(s) by whom the laboratory result report was authored.
.... attestation
..... attester[x] 1..1 EHDSHealthProfessional, EHDSDevice Attester who validated the document
.... legalAuthentication
..... legalAuthenticator[x] 1..1 EHDSHealthProfessional, EHDSOrganisation The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
.... eventType 0..* CodeableConcept Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.
Binding Description: (preferred): SNOMED CT
... intendedRecipient[x] 0..* Intended recipient
.... intendedRecipientEHDSPatient EHDSPatient
.... intendedRecipientEHDSRelatedPerson EHDSRelatedPerson
.... intendedRecipientEHDSHealthProfessional EHDSHealthProfessional
.... intendedRecipientEHDSOrganisation EHDSOrganisation
.... intendedRecipientEHDSDevice EHDSDevice
... body 0..1 Base Laboratory Report structured body
.... orderInformation 0..* Base Order Information (Laboratory Result Report could respond to multiple test orders)
..... orderId 1..* Identifier An identifier of the laboratory test order. Laboratory Result Report may respond to multiple orders.
..... orderDateAndTime 0..1 dateTime Date and time of the order placement.
..... orderPlacer[x] 0..1 The person/organisation "authorised" to place the order. Order placer could be either a health professional, health professional organisation or the patient himself.
...... orderPlacerEHDSHealthProfessional EHDSHealthProfessional
...... orderPlacerEHDSOrganisation EHDSOrganisation
...... orderPlacerEHDSPatient EHDSPatient
..... orderReason[x] 0..* An explanation or justification for why this service is being requested in coded form.
Binding Description: (preferred): SNOMED CT
...... orderReasonCodeableConcept CodeableConcept
...... orderReasonEHDSCondition EHDSCondition
...... orderReasonEHDSObservation EHDSObservation
...... orderReasonString string
..... clinicalQuestion 0..1 string Specification of clinical question (goal of the investigation) to be answered by the laboratory investigation.
.... supportingInformation 0..1 Base Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs).' This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.
..... observation 0..* EHDSObservation Clinical findings and other observations.
..... condition 0..* EHDSCondition Condition that may influence the service or result interpretation.
..... medicationAdministration 0..* EHDSMedicationAdministration Medication administered before ordering the service.
..... sexForClinicalUse 0..1 CodeableConcept A Sex Parameter for Clinical Use is a parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.. This property is intended for use in clinical decision making, and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population
Binding Description: (preferred): HL7 sex-parameter-for-clinical-use
..... vaccination 0..* EHDSImmunisation Vaccination history of the patient.
..... otherSupportingInformation 0..* Resource Any other type of relevant supporting information
.... specimen 0..* EHDSSpecimen Specimen information
.... serviceRequest 0..* EHDSServiceRequest Specification of requested service or services
.... resultData 1..1 Base Laboratory report result data
..... commentsInterpretationAndRecommendations 0..* Narrative Narrative Comments, such as a textual interpretation or advice accompanying the result report, for example.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... laboratoryTestResults 0..* EHDSLaboratoryObservation Observation details (report could consist of multiple observations)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
EHDSLaboratoryReport.​header.eventType Base preferred Not State Unknown
EHDSLaboratoryReport.​body.orderInformation.​orderReason[x] Base preferred Not State Unknown
EHDSLaboratoryReport.​body.supportingInformation.​sexForClinicalUse Base preferred Not State Unknown
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSLaboratoryReport 0..* EHDSDocument Laboratory report model

Elements defined in Ancestors:header, header, presentedForm
Instances of this logical model can be the target of a Reference
... header 1..1 Base Laboratory Report header
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 1..* Identifier Unique identifier of the document
.... author[x] 1..* Author(s) by whom the laboratory result report was authored.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 1..1 dateTime Date of finalising/issuing the document
.... status 1..1 CodeableConcept Status of the document
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
.... documentType 1..1 CodeableConcept Type of document at hand, e.g. 60591-5 Patient summary document.
Binding Description: (preferred): LOINC
.... documentTitle 1..1 string Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024'
.... period 0..1 Period Time of service that is being documented
.... version 0..1 string Business version of the document. The exact algorithm for versioning is decided by the producer/custodian
.... attestation 0..* Base Document attestation details
..... attester[x] 1..1 Attester who validated the document
...... attesterEHDSHealthProfessional EHDSHealthProfessional
...... attesterEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of the approval of the document by Attester
.... legalAuthentication 0..* Base Document legal authentication details
..... legalAuthenticator[x] 1..1 The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
...... legalAuthenticatorEHDSHealthProfessional EHDSHealthProfessional
...... legalAuthenticatorEHDSOrganisation EHDSOrganisation
..... datetime 1..1 dateTime Date and time when the document was authorised
.... eventType 0..* CodeableConcept Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.
Binding Description: (preferred): SNOMED CT
.... serviceSpecialty 0..* CodeableConcept Additional details about where the content was created (e.g. clinical specialty)
Binding Description: (preferred): SNOMED CT
.... custodian 0..1 EHDSOrganisation Organisation that is in charge of maintaining the document/report.
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... intendedRecipient[x] 0..* Intended recipient
.... intendedRecipientEHDSPatient EHDSPatient
.... intendedRecipientEHDSRelatedPerson EHDSRelatedPerson
.... intendedRecipientEHDSHealthProfessional EHDSHealthProfessional
.... intendedRecipientEHDSOrganisation EHDSOrganisation
.... intendedRecipientEHDSDevice EHDSDevice
.... orderInformation 0..* Base Order Information (Laboratory Result Report could respond to multiple test orders)
..... orderId 1..* Identifier An identifier of the laboratory test order. Laboratory Result Report may respond to multiple orders.
..... orderDateAndTime 0..1 dateTime Date and time of the order placement.
..... orderPlacer[x] 0..1 The person/organisation "authorised" to place the order. Order placer could be either a health professional, health professional organisation or the patient himself.
...... orderPlacerEHDSHealthProfessional EHDSHealthProfessional
...... orderPlacerEHDSOrganisation EHDSOrganisation
...... orderPlacerEHDSPatient EHDSPatient
..... orderReason[x] 0..* An explanation or justification for why this service is being requested in coded form.
Binding Description: (preferred): SNOMED CT
...... orderReasonCodeableConcept CodeableConcept
...... orderReasonEHDSCondition EHDSCondition
...... orderReasonEHDSObservation EHDSObservation
...... orderReasonString string
..... clinicalQuestion 0..1 string Specification of clinical question (goal of the investigation) to be answered by the laboratory investigation.
.... supportingInformation 0..1 Base Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs).' This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.
..... observation 0..* EHDSObservation Clinical findings and other observations.
..... condition 0..* EHDSCondition Condition that may influence the service or result interpretation.
..... medicationAdministration 0..* EHDSMedicationAdministration Medication administered before ordering the service.
..... sexForClinicalUse 0..1 CodeableConcept A Sex Parameter for Clinical Use is a parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.. This property is intended for use in clinical decision making, and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population
Binding Description: (preferred): HL7 sex-parameter-for-clinical-use
..... vaccination 0..* EHDSImmunisation Vaccination history of the patient.
..... otherSupportingInformation 0..* Resource Any other type of relevant supporting information
.... specimen 0..* EHDSSpecimen Specimen information
.... serviceRequest 0..* EHDSServiceRequest Specification of requested service or services
.... resultData 1..1 Base Laboratory report result data
..... commentsInterpretationAndRecommendations 0..* Narrative Narrative Comments, such as a textual interpretation or advice accompanying the result report, for example.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... laboratoryTestResults 0..* EHDSLaboratoryObservation Observation details (report could consist of multiple observations)
... attachments 0..* EHDSAttachment Report attachments

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
EHDSLaboratoryReport.​header.language Base preferred Not State Unknown
EHDSLaboratoryReport.​header.documentType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.eventType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.serviceSpecialty Base preferred Not State Unknown
EHDSLaboratoryReport.​body.orderInformation.​orderReason[x] Base preferred Not State Unknown
EHDSLaboratoryReport.​body.supportingInformation.​sexForClinicalUse Base preferred Not State Unknown

This structure is derived from EHDSDocument

Summary

Mandatory: 0 element(2 nested mandatory elements)

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSLaboratoryReport 0..* EHDSDocument Laboratory report model

Elements defined in Ancestors:header, header, presentedForm
Instances of this logical model can be the target of a Reference
... header 1..1 Base Laboratory Report header
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 1..* Identifier Unique identifier of the document
.... author[x] 1..* Author(s) by whom the laboratory result report was authored.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 1..1 dateTime Date of finalising/issuing the document
.... status 1..1 CodeableConcept Status of the document
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
.... documentType 1..1 CodeableConcept Type of document at hand, e.g. 60591-5 Patient summary document.
Binding Description: (preferred): LOINC
.... documentTitle 1..1 string Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024'
.... period 0..1 Period Time of service that is being documented
.... version 0..1 string Business version of the document. The exact algorithm for versioning is decided by the producer/custodian
.... attestation 0..* Base Document attestation details
..... attester[x] 1..1 Attester who validated the document
...... attesterEHDSHealthProfessional EHDSHealthProfessional
...... attesterEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of the approval of the document by Attester
.... legalAuthentication 0..* Base Document legal authentication details
..... legalAuthenticator[x] 1..1 The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
...... legalAuthenticatorEHDSHealthProfessional EHDSHealthProfessional
...... legalAuthenticatorEHDSOrganisation EHDSOrganisation
..... datetime 1..1 dateTime Date and time when the document was authorised
.... eventType 0..* CodeableConcept Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.
Binding Description: (preferred): SNOMED CT
.... serviceSpecialty 0..* CodeableConcept Additional details about where the content was created (e.g. clinical specialty)
Binding Description: (preferred): SNOMED CT
.... custodian 0..1 EHDSOrganisation Organisation that is in charge of maintaining the document/report.
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... intendedRecipient[x] 0..* Intended recipient
.... intendedRecipientEHDSPatient EHDSPatient
.... intendedRecipientEHDSRelatedPerson EHDSRelatedPerson
.... intendedRecipientEHDSHealthProfessional EHDSHealthProfessional
.... intendedRecipientEHDSOrganisation EHDSOrganisation
.... intendedRecipientEHDSDevice EHDSDevice
.... orderInformation 0..* Base Order Information (Laboratory Result Report could respond to multiple test orders)
..... orderId 1..* Identifier An identifier of the laboratory test order. Laboratory Result Report may respond to multiple orders.
..... orderDateAndTime 0..1 dateTime Date and time of the order placement.
..... orderPlacer[x] 0..1 The person/organisation "authorised" to place the order. Order placer could be either a health professional, health professional organisation or the patient himself.
...... orderPlacerEHDSHealthProfessional EHDSHealthProfessional
...... orderPlacerEHDSOrganisation EHDSOrganisation
...... orderPlacerEHDSPatient EHDSPatient
..... orderReason[x] 0..* An explanation or justification for why this service is being requested in coded form.
Binding Description: (preferred): SNOMED CT
...... orderReasonCodeableConcept CodeableConcept
...... orderReasonEHDSCondition EHDSCondition
...... orderReasonEHDSObservation EHDSObservation
...... orderReasonString string
..... clinicalQuestion 0..1 string Specification of clinical question (goal of the investigation) to be answered by the laboratory investigation.
.... supportingInformation 0..1 Base Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs).' This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.
..... observation 0..* EHDSObservation Clinical findings and other observations.
..... condition 0..* EHDSCondition Condition that may influence the service or result interpretation.
..... medicationAdministration 0..* EHDSMedicationAdministration Medication administered before ordering the service.
..... sexForClinicalUse 0..1 CodeableConcept A Sex Parameter for Clinical Use is a parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.. This property is intended for use in clinical decision making, and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population
Binding Description: (preferred): HL7 sex-parameter-for-clinical-use
..... vaccination 0..* EHDSImmunisation Vaccination history of the patient.
..... otherSupportingInformation 0..* Resource Any other type of relevant supporting information
.... specimen 0..* EHDSSpecimen Specimen information
.... serviceRequest 0..* EHDSServiceRequest Specification of requested service or services
.... resultData 1..1 Base Laboratory report result data
..... commentsInterpretationAndRecommendations 0..* Narrative Narrative Comments, such as a textual interpretation or advice accompanying the result report, for example.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... laboratoryTestResults 0..* EHDSLaboratoryObservation Observation details (report could consist of multiple observations)
... attachments 0..* EHDSAttachment Report attachments

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
EHDSLaboratoryReport.​header.language Base preferred Not State Unknown
EHDSLaboratoryReport.​header.documentType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.eventType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.serviceSpecialty Base preferred Not State Unknown
EHDSLaboratoryReport.​body.orderInformation.​orderReason[x] Base preferred Not State Unknown
EHDSLaboratoryReport.​body.supportingInformation.​sexForClinicalUse Base preferred Not State Unknown

Differential View

This structure is derived from EHDSDocument

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSLaboratoryReport 0..* EHDSDocument Laboratory report model

Elements defined in Ancestors:header, header, presentedForm
Instances of this logical model can be the target of a Reference
... header 1..1 Base Laboratory Report header
.... author[x] 1..* EHDSHealthProfessional, EHDSOrganisation, EHDSDevice Author(s) by whom the laboratory result report was authored.
.... attestation
..... attester[x] 1..1 EHDSHealthProfessional, EHDSDevice Attester who validated the document
.... legalAuthentication
..... legalAuthenticator[x] 1..1 EHDSHealthProfessional, EHDSOrganisation The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
.... eventType 0..* CodeableConcept Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.
Binding Description: (preferred): SNOMED CT
... intendedRecipient[x] 0..* Intended recipient
.... intendedRecipientEHDSPatient EHDSPatient
.... intendedRecipientEHDSRelatedPerson EHDSRelatedPerson
.... intendedRecipientEHDSHealthProfessional EHDSHealthProfessional
.... intendedRecipientEHDSOrganisation EHDSOrganisation
.... intendedRecipientEHDSDevice EHDSDevice
... body 0..1 Base Laboratory Report structured body
.... orderInformation 0..* Base Order Information (Laboratory Result Report could respond to multiple test orders)
..... orderId 1..* Identifier An identifier of the laboratory test order. Laboratory Result Report may respond to multiple orders.
..... orderDateAndTime 0..1 dateTime Date and time of the order placement.
..... orderPlacer[x] 0..1 The person/organisation "authorised" to place the order. Order placer could be either a health professional, health professional organisation or the patient himself.
...... orderPlacerEHDSHealthProfessional EHDSHealthProfessional
...... orderPlacerEHDSOrganisation EHDSOrganisation
...... orderPlacerEHDSPatient EHDSPatient
..... orderReason[x] 0..* An explanation or justification for why this service is being requested in coded form.
Binding Description: (preferred): SNOMED CT
...... orderReasonCodeableConcept CodeableConcept
...... orderReasonEHDSCondition EHDSCondition
...... orderReasonEHDSObservation EHDSObservation
...... orderReasonString string
..... clinicalQuestion 0..1 string Specification of clinical question (goal of the investigation) to be answered by the laboratory investigation.
.... supportingInformation 0..1 Base Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs).' This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.
..... observation 0..* EHDSObservation Clinical findings and other observations.
..... condition 0..* EHDSCondition Condition that may influence the service or result interpretation.
..... medicationAdministration 0..* EHDSMedicationAdministration Medication administered before ordering the service.
..... sexForClinicalUse 0..1 CodeableConcept A Sex Parameter for Clinical Use is a parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.. This property is intended for use in clinical decision making, and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population
Binding Description: (preferred): HL7 sex-parameter-for-clinical-use
..... vaccination 0..* EHDSImmunisation Vaccination history of the patient.
..... otherSupportingInformation 0..* Resource Any other type of relevant supporting information
.... specimen 0..* EHDSSpecimen Specimen information
.... serviceRequest 0..* EHDSServiceRequest Specification of requested service or services
.... resultData 1..1 Base Laboratory report result data
..... commentsInterpretationAndRecommendations 0..* Narrative Narrative Comments, such as a textual interpretation or advice accompanying the result report, for example.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... laboratoryTestResults 0..* EHDSLaboratoryObservation Observation details (report could consist of multiple observations)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
EHDSLaboratoryReport.​header.eventType Base preferred Not State Unknown
EHDSLaboratoryReport.​body.orderInformation.​orderReason[x] Base preferred Not State Unknown
EHDSLaboratoryReport.​body.supportingInformation.​sexForClinicalUse Base preferred Not State Unknown

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSLaboratoryReport 0..* EHDSDocument Laboratory report model

Elements defined in Ancestors:header, header, presentedForm
Instances of this logical model can be the target of a Reference
... header 1..1 Base Laboratory Report header
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 1..* Identifier Unique identifier of the document
.... author[x] 1..* Author(s) by whom the laboratory result report was authored.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 1..1 dateTime Date of finalising/issuing the document
.... status 1..1 CodeableConcept Status of the document
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
.... documentType 1..1 CodeableConcept Type of document at hand, e.g. 60591-5 Patient summary document.
Binding Description: (preferred): LOINC
.... documentTitle 1..1 string Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024'
.... period 0..1 Period Time of service that is being documented
.... version 0..1 string Business version of the document. The exact algorithm for versioning is decided by the producer/custodian
.... attestation 0..* Base Document attestation details
..... attester[x] 1..1 Attester who validated the document
...... attesterEHDSHealthProfessional EHDSHealthProfessional
...... attesterEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of the approval of the document by Attester
.... legalAuthentication 0..* Base Document legal authentication details
..... legalAuthenticator[x] 1..1 The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
...... legalAuthenticatorEHDSHealthProfessional EHDSHealthProfessional
...... legalAuthenticatorEHDSOrganisation EHDSOrganisation
..... datetime 1..1 dateTime Date and time when the document was authorised
.... eventType 0..* CodeableConcept Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.
Binding Description: (preferred): SNOMED CT
.... serviceSpecialty 0..* CodeableConcept Additional details about where the content was created (e.g. clinical specialty)
Binding Description: (preferred): SNOMED CT
.... custodian 0..1 EHDSOrganisation Organisation that is in charge of maintaining the document/report.
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... intendedRecipient[x] 0..* Intended recipient
.... intendedRecipientEHDSPatient EHDSPatient
.... intendedRecipientEHDSRelatedPerson EHDSRelatedPerson
.... intendedRecipientEHDSHealthProfessional EHDSHealthProfessional
.... intendedRecipientEHDSOrganisation EHDSOrganisation
.... intendedRecipientEHDSDevice EHDSDevice
.... orderInformation 0..* Base Order Information (Laboratory Result Report could respond to multiple test orders)
..... orderId 1..* Identifier An identifier of the laboratory test order. Laboratory Result Report may respond to multiple orders.
..... orderDateAndTime 0..1 dateTime Date and time of the order placement.
..... orderPlacer[x] 0..1 The person/organisation "authorised" to place the order. Order placer could be either a health professional, health professional organisation or the patient himself.
...... orderPlacerEHDSHealthProfessional EHDSHealthProfessional
...... orderPlacerEHDSOrganisation EHDSOrganisation
...... orderPlacerEHDSPatient EHDSPatient
..... orderReason[x] 0..* An explanation or justification for why this service is being requested in coded form.
Binding Description: (preferred): SNOMED CT
...... orderReasonCodeableConcept CodeableConcept
...... orderReasonEHDSCondition EHDSCondition
...... orderReasonEHDSObservation EHDSObservation
...... orderReasonString string
..... clinicalQuestion 0..1 string Specification of clinical question (goal of the investigation) to be answered by the laboratory investigation.
.... supportingInformation 0..1 Base Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs).' This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.
..... observation 0..* EHDSObservation Clinical findings and other observations.
..... condition 0..* EHDSCondition Condition that may influence the service or result interpretation.
..... medicationAdministration 0..* EHDSMedicationAdministration Medication administered before ordering the service.
..... sexForClinicalUse 0..1 CodeableConcept A Sex Parameter for Clinical Use is a parameter that provides guidance on how a recipient should apply settings or reference ranges that are derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc.. This property is intended for use in clinical decision making, and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population
Binding Description: (preferred): HL7 sex-parameter-for-clinical-use
..... vaccination 0..* EHDSImmunisation Vaccination history of the patient.
..... otherSupportingInformation 0..* Resource Any other type of relevant supporting information
.... specimen 0..* EHDSSpecimen Specimen information
.... serviceRequest 0..* EHDSServiceRequest Specification of requested service or services
.... resultData 1..1 Base Laboratory report result data
..... commentsInterpretationAndRecommendations 0..* Narrative Narrative Comments, such as a textual interpretation or advice accompanying the result report, for example.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... laboratoryTestResults 0..* EHDSLaboratoryObservation Observation details (report could consist of multiple observations)
... attachments 0..* EHDSAttachment Report attachments

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
EHDSLaboratoryReport.​header.language Base preferred Not State Unknown
EHDSLaboratoryReport.​header.documentType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.eventType Base preferred Not State Unknown
EHDSLaboratoryReport.​header.serviceSpecialty Base preferred Not State Unknown
EHDSLaboratoryReport.​body.orderInformation.​orderReason[x] Base preferred Not State Unknown
EHDSLaboratoryReport.​body.supportingInformation.​sexForClinicalUse Base preferred Not State Unknown

This structure is derived from EHDSDocument

Summary

Mandatory: 0 element(2 nested mandatory elements)

 

Other representations of profile: CSV, Excel