Table of Content
The MedCom Shared EKG Recording standard (DA: Deling af EKG-optagelser), named EKG Recording, enables cross-sectoral sharing of electrocardiograms (EKGs). The standard supports the establishment of a national sharing portal for EKG data in the form of PDF documents enclosed in a FHIR Document.
New to the EKG Recording standard?
Start here: Getting Started – EKG Recording. It gives you a quick overview of the documentation, tools, and helpful resources to get you started.
The standard documentation below provides the necessary content to understand the role of the EKG Recording FHIR Document, what to implement and how to obtain a MedCom certificate. The standard documentation for EKGRecording includes:
A user story is an informal, general description of a systems functionality as perceived from the user’s perspective. User stories have the end user at the centre of the dialogue about system functionality. User stories describe which needs the end user wants fulfilled, so that the developer understands the context of the development task: why they are developing the function and what value it must provide the end user. Not all user stories will be supported with this current implementation, which is noted for the specific user story.
Use cases describe the different scenarios a standard supports. 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 MedCom Shared EKG Recording standard. The descriptions are targeted at IT-system vendors and the people responsible for the implementation.
The user stories and use cases can be found here:
(Will be published when available)
The technical specification for the standard is composed of profiles originating from multiple Implementation Guides (IGs). The Implementation Guide for the MedCom EKG Recording standard is available here: MedCom EKG Recording Implementation Guide.
On the front page of this Implementation Guide, there is a description of the other relevant IGs on which the standard depends. In addition, a dependency tree can be viewed under the Dependencies tab, which is accessible via the More section of the Implementation Guide.
Certification of a system implies both an approved test protocol and a run-through of test scripts via ITB (Interoperability Test Bed). The ITB describes an infrastructure that allows for automated testing of specific use cases and validation against the IGs developed by MedCom.
Click here to find a description of getting started with ITB.
Providing an EKG Recording document
Receiving an EKG Recording document