MedCom HospitalNotification

Table of contents

1 Standard documentation
2 Test and certification

Note: Clinical guidelines for application and use cases are available in both Danish and English. The remaining documentation will solely be in English.

This page presents MedCom’s HospitalNotification standard (Danish: Advis om sygehusophold). The standard will in time replace the existing standards called XDIS17 and XDIS20.The purpose of the standard is to notify the patient’s care and health actors in the primary sector about the start, periods of leave and end time of the patient’s stay in a hospital. The notification allows pausing current health and care services during the patient’s hospitalisation and to start the services when the hospitalisation ends. Furthermore, the notification of hospital stay can trigger the automatic sending of an admission report (XDIS16) from the recipient’s system, which gives the hospital staff an overview of the patient’s current services, functional level, and healthcare problems.

1 Standard documentation

The standard documentation below provides the necessary content to understand the needs for modernisation, the role of the HospitalNotification message, what to implement and how to get a MedCom Certificate. The standard documentation for HospitalNotification includes:

Clinical guidelines for application
Use cases
Technical Specifications in terms of the relevant IGs and clinical introduction to the content of the IG.
An overview of the codes in a FHIR HospitalNotification message which compose a certain meaning
Mapping document from XDIS17 and XDIS20 to FHIR HospitalNotification Message.

1.1 Clinical guidelines for application

The clinical guidelines for application are the foundation for the HospitalNotification standard. It describes the clinical needs for the modernisation, the requirements for the content of the standard and how the standard supports the business requirements. It is the primary textual part of the documentation for HospitalNotification. It is important for both implementers and business specialists to understand the clinical guidelines for application to ensure that the implemented standard supports the requirements.

Below you can find the clinical guidelines for application in both Danish and English:
Danish: Sundhedsfaglige retningslinjer for anvendelse
English: Clinical guidelines for application

1.2 Use cases

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 HospitalNotification. The descriptions are targeted IT-system vendors and the people responsible for the implementation in regions and municipalities.

The use cases for HospitalNotification are qualified in collaboration with EPR- and vendors catering to the municipalities.

Use cases in Danish (pdf)

Use cases in English (pdf)

1.3 Technical specification

The technical specification for HospitalNotification standard is composed by profiles form MedCom HospitalNotification IG, MedComCore IG, MedComMessaging IG and from MedCom Terminology IG.

The profiles that are part of the technical specification for MedCom HospitalNotification IG 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 specification.

1.4 HospitalNotification Codes

The HospitalNotification message notifies the care and health actors in the primary sector about the status of the patient’s hospital stay. The status is represented using HospitalNotification codes. The value of codes can be found in MedComHospitalNotificationEncounter, MedComMessagingProvenance and MedComCorePatient profile and will together form the composite understanding of a HospitalNotification message, e.g. a hospitalization of an acute patient or discharge of an inpatient. Depending on which activity has taken place, the elements should be assigned to different values.
To help vendors of the IT system implement the codes in the same way MedCom has developed an overview of the HospitalNotification codes.

Click here to see the HospitalNotification codes used in FHIR

1.5 Mapping from XDIS17 and XDIS20 to MedCom HospitalNotification

Mapping from previous OIOXML standards to the FHIR HospitalNotification 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 XDIS17 and XDIS20 are transferred to the HospitalNotification, 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.

Click here to see mapping from previous OIOXML standards to the FHIR HospitalNotification standard.

2 Test and certification

Certification of a system implies both an approved test protocol and run-through of TouchStone test scripts. TouchStone describes an infrastructure that allows for automated test and validation against the IG’s developed by MedCom. Test protocols and test scripts are used to test and certify whether systems comply to the HospitalNotification standard.

Click here to find the description of test and certification of FHIR standards in MedCom.

Sending a HospitalNotification message

Receiving a HospitalNotification message

About

Support or contact

MedCom is responsible for this page. If you have any questions regarding this page, please contact fhir@medcom.dk or write to MedComs stream on Zulip.

Version of this documentation

The version of this documentation is: Version 3.0.8 You can find the release note of the version here

"FHIR® is the registered trademark of HL7 and is used with the permission of HL7. Use of the FHIR trademark does not constitute endorsement of this implementation guide by HL7, nor affirmation that this content is conformant to the various applicable standards"