Table of contents
This page presents MedCom’s Acknowledgement FHIR®© standard (Danish: Kvittering). An Acknowledgement message corresponds to a receipt of a delivered message. Every time a system receives a MedCom FHIR message, e.g. a HospitalNotification or a CareCommunication, it shall be acknowledged with a MedCom Acknowledgement message, stating if the transfer was successful and the message validated correctly or not. In other words, does a MedCom Acknowledgement message hold information about how delivery of a message went. MedCom FHIR messaging complies with reliable messaging and associated governance, which describes the value and needs for acknowledge all messages.
The Acknowledgement is sent as a message and therefore follows the general MedCom FHIR messaging structure, except that the carbon-copy destination is not allowed. The Acknowledge message is released when the receiving system receives the originally sent message from the sending system. The standard will in time replace the existing; EDIFACT CTLO1-03 and XCTLO1-03.
The standard documentation below provides the necessary content to understand the needs for modernisation, the role of the Acknowledgement message, what to implement and how to get a MedCom certificate. The standard documentation for Acknowledgement includes:
Use cases describe the different scenarios in which a standard support. For a certain real-world scenario, it describes the requirements for the content of a message. The purpose of the use cases is to ensure a coherent implementation and use of the Acknowledgement. The descriptions are targeted IT-system vendors and the people responsible for the implementation in regions, hospitals and municipalities.
The use cases for the acknowledgement are part of technical uses casese for MedComMessaging.
Click here to read use cases for the Acknowledgement.
The profiles that are part of the technical specification for Acknowledgement FHIR standard are:
The link below gives an overview of the included profiles, what their purpose is, and which elements the system should support. Further the structure of the standard is described and supported with examples in different degree of technical skills.
Click here to read an introduction to the technical specifications.
Mapping from previous OIOXML standard to the MedCom Acknowledgement standard can be found below. The document is intended to help translate the previous standard to the new FHIR standard. Please notice that not all elements from XCT01 are transferred to MedCom Acknowledgement as not all elements are represented in the FHIR message. Furthermore, not all elements from the FHIR elements are represented in the document; thus, it cannot stand alone for implementation.
A certification of a system implies both an approved test protocol and run-trough of TouchStone test scripts. TouchStone describes an infrastructure that allows for automated test and validation against the IG’s developed by MedCom.
You can find a general description of the MedCom test and certification process here.
Sending an Acknowledgement
Receiving an Acknowledgement