HL7 Europe Laboratory Report
2.2.0-ci - ci-build 150

HL7 Europe Laboratory Report, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 2.2.0-ci built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/laboratory/ and changes regularly. See the Directory of published versions

EHDS ServiceRequest Mapping

EHDSServiceRequest -> ServiceRequestLabEu
Ongoing alignment: The mappings are based on the Xt-EHR models 1.0.0. The models may change with the EHDS implementing acts; this guide will follow such changes.
Yellow rows: Rows highlighted in yellow mark model elements that this guide cannot represent yet.

EHDSServiceRequest -> ServiceRequestLabEu

This page explains how conceptual elements from the EHDS Service Request logical model are expressed in the corresponding FHIR ServiceRequest profile used by this Implementation Guide.

Mapping Context
EHDSServiceRequest -> ServiceRequestLabEu
EHDSServiceRequest (Logical Model) Relationship ServiceRequestLabEu
Element Description Relation Resource Element Description Notes
header Common header inherited from EHDSDataSet. related-to ServiceRequest . General metadata container.
header.subject Patient/subject of care. equivalent ServiceRequest subject Who or what the request is about.
header.identifier Business identifier. equivalent ServiceRequest identifier Placer/filler order identifiers.
header.author[x] Author of the resource. related-to ServiceRequest requester Requester of the service. EHDSServiceRequest has no separate requester element, so the author of the request maps to its requester.
header.date Date and time of authoring. equivalent ServiceRequest authoredOn Date request was created.
header.status Status of the request. equivalent ServiceRequest status Request lifecycle state.
header.source Source of the information (e.g. patient, proxy). no-map ServiceRequest - ServiceRequest has no element for the source of the information.
header.language Language of the resource. equivalent ServiceRequest language Language of content/narrative.
description Textual description of the requested service. related-to ServiceRequest code.text Text representation of the requested service. If the description adds information beyond the requested service, ServiceRequest.note can be used.
code Code and name identifying requested service. equivalent ServiceRequest code What is being requested.
quantity Amount of requested services of same type. related-to ServiceRequest quantity[x] Requested quantity. Typically Quantity in laboratory use cases.
bodySite Anatomic location/laterality of requested procedure. related-to ServiceRequest bodySite Target site
reason[x] Reason why service is requested. equivalent ServiceRequest reasonCode Clinical justification. If reason is a coded value, it maps to reasonCode.
reason[x] Reason why service is requested. equivalent ServiceRequest reasonReference Clinical justification. Reason details are represented as references to other resources.
priority How quickly request should be addressed. equivalent ServiceRequest priority Routine | urgent | asap | stat.
supportingInformation[x] Additional clinical info relevant to interpretation. equivalent ServiceRequest supportingInfo Supporting references.
specimen Specimen(s) to be used for laboratory procedure. equivalent ServiceRequest specimen Referenced specimen resources.
encounter Encounter context of the request. equivalent ServiceRequest encounter Healthcare context of request.
occurrence[x] Expected time of the service. equivalent ServiceRequest occurrence[x] Requested occurrence timing.
patientInstructions Patient or consumer-oriented instructions. equivalent ServiceRequest patientInstruction Instructions to patient/subject.

Return to overview: EHDS Logical Models -> FHIR Profiles