EHMI End User Application Responsibility Specification (EUA)
In MedCom13, MedCom has a joint testing project ‘Municipal test responses on new infrastructure’, where MedCom’s two central modernization tracks are linked: FHIR and EHMI, where both message communication and the infrastructure are modernized. The modernization is due to the need for quality improvement in, among other things, security, transparency, robustness and efficient, international digital message communication. The project will conduct an operational test from March 1 to May 31, 2025. In the test, the new FHIR standard for municipal test responses must be sent from municipal emergency functions (EOJ) to general medical practices (LPS) via the new infrastructure EHMI (Enhanced Healthcare Messaging Infrastructure). The standard must be sent via eDelivery, and EHMI functionalities such as document sharing and shipment status (Track’n’Trace) must also be tested.
This page describes the required EHMI tasks and responsibilities for the End User Application . Relevant links can be found at the end of the document.
Background information - illustration and explanation of components
There are 3 components involved in sending/receiving a message:
- EUA (Sender/receiver system)
- MSH (Message Service Handler)
- AP (Access Point)
These components can be combined in different ways by the suppliers. Regardless of the combination, the suppliers must comply with the responsibility specification.
EHMI Delivery Status - EUA responsibility description:
The following prerequisites for the End User Application apply:
- The End User Application is a component that is assumed to be relevant to the clinical users in a healthcare domain. It can be a stand-alone application, integrated with MSH, integrated with an EHMI AP or integrated with both (both MSH and EHMI AP)
- The End User Application must be able to generate MedCom messages or data content corresponding to a MedCom message. It must be able to pass on a MedCom message or the data content of a MedCom message via an interface to MSH.
- The End User Application must be able to provide MSH with sufficient metadata to be able to create an SBDH envelope for both primary recipient and secondary recipient in the form of XDS metadata for document sharing via an interface to MSH.
As an additional task, the End User Application (EUA) must be able to communicate with the EHMI Delivery Status repository (track’n’trace).
The EHMI Delivery Status repository has a reporting API that the End User Application (EUA) must communicate via. It is based on an OAuth-secured REST interface and SMART-on-FHIR.
For the collection of EHMI Delivery Status, it is required that, cf. section 6.3.1 of the Architectural Vision, explicit signing is made between the EHMI Delivery Status “client” and the “server” (with associated verification) at system evidence level (VOCES/FOCES/Level 3).
In addition, in this context, there is a requirement that the collection is carried out via an asynchronous decoupling mechanism (queue) to ensure that no EHMI Delivery Status data is lost.
In the test, the display of shipment status is expected to be done via a central solution, but there is a possibility that the business system can implement a local display in the business system. Access to the display will be subject to the same security requirements as for reporting, see 6.3.3 in the MB.
EHMI Addressing Service - EUA responsibility description:
The End User Application must be able to integrate with the EHMI Addressing Service (EAS). The EHMI Addressing Service (EAS) will offer a search functionality that in the first version can retrieve shipping data for your own general practitioner. The EHMI Addressing Service (EAS) is currently being specified.
Relevante links:
_Danish:_
_English:_
About
Support or contact
MedCom is responsible for this page. If you have any questions regarding this page, please contact ehmi@medcom.dk.If you want to report an issue regarding this page, please report it at GitHub issues for EHMI®
Version of this documentation
The version of this documentation is: Version 0.9.0 You can find the release note of the version here."EHMI® is the registered trademark of MedCom and is used with the permission of MedCom."