EHMI Logo
EHMI Landingpage EHMI Core EHMI Delivery Status EHMI Addressing Service* EHMI Endpoint Register* EHMI Governance* EHMI Security* EHMI Glossary

EHMI Message Service Handler (MSH) Responsibility Specification

The following prerequisites for the Message Service Handler (MSH) apply:

EHMI Delivery Status - MSH responsibility description:

As an additional task, EHMI MSH must be able to communicate with the EHMI Delivery Status (EDS) repository (track’n’trace).

The EHMI Delivery Status (EDS) repository has a reporting API that the AP must communicate via.

For the collection of delivery status, it is required that, according to section 6.3.1 of the Architectural Vision, the delivery status is explicitly signed between the “client” and the “server” (with associated verification) at system evidence level (VOCES/FOCES/Level 3).

Furthermore, in this context, there is a requirement that the collection is carried out via an asynchronous decoupling mechanism (queue), so that it is ensured that no delivery status data is lost.

EHMI MSH’s responsibility for communicating with the XDS infrastructure

EHMI MSH must be able to handle XDS Metadata formatted as the FHIR DocumentReference resource. MedCom is profiling the FHIR DocumentReference resource. The MSH must be able to create the MedCom FHIR DocumentReference profile with the correct data. EHMI MSH must be able to insert the extra metadata in the MedCom FHIR DocumentReference resource into the designated BusinessScope/Scope in the SBDH envelope.



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."