This specification conforms to FHIR®© R4
Clinical Guidelines for application
Table of contents
- 1 Introduction
- 2 Purpose
- 3 Background
- 4 Legal framework
- 5 Contents and functionality
- 6 Business rules for application
- 7 Example
1 Introduction
The health professional guidelines for using the standard Hospital Notification (DAN: Advis om sygehusophold) are described here. This includes the purpose, back-ground, legal basis for exchange as well as the content and functionality of Hospital Notification. The target group is IT system vendors and those responsible for im-plementation in regions and municipalities. The ‘Hospital Notification’ replaces the previous MedCom standards, Notification of Admission DIS20 and XDIS20, and Notification of Discharge DIS17 and XDIS17.
Please note that for the technical implementation, a number of use cases have been prepared, where functionalitites and business rules for use have been translated into a number of detailed use cases for sender and receiver systems.Click here to read use cases.
Also note that the total content is described in the technical specifications. Click here to read the technical specifications.
Note: In case of any discrepancies between the two documents, the Danish document is the document in force.
2 Purpose
Hospital Notification is a central and business-critical message which - automatically - informs the citizen’s current care and health actors in the municipality when a citi-zen starts and ends his/hers hospital stay (acute ambulant or inpatient). This gives the citizen’s actors in the municipality the opportunity to pause the citizen’s current care and health services during the hospital stay and resume them when it ends. Hospital Notification can also trigger the automatic sending of an admission report (XDIS16) from the recipient’s system, which gives the hospital staff an overview of the citizen’s current services, functional level, and healthcare problems. Hospital Notification ensures that the business needs for notification are supported and includes notification by:
- Admission
- Acute ambulant hospital stay
- Leave – start and end
- End of hospital stay
3 Background
In line with the fact that more and more patients are not admitted, but is treated acute ambulant at the hospital, a need has arisen for notification of citizens not admitted. The development of ‘Hospital Notification’ was initiated in 2018 under the auspices of MedCom’s home care-hospital group (DAN: hjemmepleje-sygehusgruppen) and municipal hospital supplier group (DAN: Kommune-sygehusleverandørgruppen), which have defined requirements for content and clinical guidelines for application. Note regarding LPR3 : Registration of hospital stays in the EPR system is linked to the reporting to the National Patient Registry, LPR. By transition to LPR3 (2019), the concepts ‘admitted’ and ‘outpatient’ are removed in the reporting to LPR and replaced by physical attendance. In practice, all regions continue to register the hospital stay as outpatient and admission respectively. It is agreed among the parties behind the development of the Hospital Notification that the scope of the hospital stays, which will be supported by a notification, is:
“All current hospital stays with physical attendance by the patient and all planned hospital stays with physical attendance by the patient for the purpose of admission.”
4 Legal framework
Hospital Notification are exchanged on the basis of the Danish Health Act and Danish Legal Protection Act §12c:
For use in the planning of care services etc pursuant to § 79 a, chapter 16 and §§ 107 and 108 in the social services and health care act as well as for follow-ups of cases pursuant to §§ 8-10 in the act on sickness benefits, the municipal council and hospital can exchange information about citizens admission and discharge from hospitals within the municipality and about the citizen's acute hospital stay, where the citizen stays at the hospital for assessment and treatment without being admitted. The exchange can take place automatic and without the consent of the citizen. (Danish Legal Act 12c LBK 265 25/02/2022)
The service act §79 a includes preventive home visits, chapter 16 includes §§ 83-99, which covers personal help, care and nursing as well as care wills, and §§ 107 and 108 covers temporary and long-term sheltered residence.
5 Contents and functionality
Hospital Notification is sent automatically and in real-time from the hospital’s EPR system to the patient’s municipality of residence. As the hospital is not able to determine in advance which citizens currently receive services from the primary sector, a Hospital Notification is generated for all citizens with a personal identification number (CPR) and home address in Denmark when registered in the hospital’s EPR system. The receiving system ensures that the Hospital Notification stay is only downloaded and shown for citizens receiving services within the valid legal framework. Hospital Notification will - for the recipient in the municipality - appear with the following content (see section 7 for example)
- The patient’s personal identification number
- Status of the hospital stay
- Date and time of start/end of hospital stay
- Name of the hospital department/section and the hospital where the patient is staying
Hospital Notification indicates one of the following possible outcomes:
- Start hospital stay – acute ambulant
- Start hospital stay - admitted
- End hospital stay – patient completed to home/primary sector
- Death
- Start leave
- End leave Admission report (XDIS16) is requested for a number of predefined events. An overview of which events trigger which types of/statuses for Hospital Notification, as well as when an admission report is requested, can be found in Table 1.
Note: Danish code names, which can be related to overview of notification codes and HL7 FHIR resources.
| Event | Code* | Status for stay (type of Hospital Notification) |
Request for admission report(XDIS16) | Benefit |
|---|---|---|---|---|
| Start hospital stay | ||||
| Acute ambulant patient | STAA | Start hospital stay – acute ambulant | Yes | The receiver is informed that the citizen is registered as ‘acute ambulant’ at the hospital. The specific status allows the receiving system to set rules for the system management. |
| Admit patient | STIN | Start hospital stay - admitted | Yes | The receiver is informed that the citizen is registered as ‘admitted to hospital’. The specific status allows the receiving system to set rules for the system management. |
| Admit patient from another region | STIN | Start hospital stay - admitted | Yes | The receiver is informed that the citizen is transferred to another hospital in another region. |
| Admit patient from another hospital in the same region | STIN | Start hospital stay - admitted | No | The receiver is informed that the citizen is transferred to another hospital in the same region. |
| Admit patient from another department at the same hospital | No notification | No notification | Not relevant | |
| End hospital stay | ||||
| End stay | SLHJ | End hospital stay - patient completed to home/primary sector | No | The receiver is informed that the citizen’s hospital stay is ended and is transferred to either home or primary sector. It allows the receiving system to set rules for the system management, for example resuming care services. Not used for transfer. |
| Death | ||||
| The patient dies (on arrival or during hospital stay) | MORS | Death | No | The receiver is informed that the citizen is dead. Used both for death on arrival and death during the hospital stay. |
| Leave | ||||
| Patient starts leave | STOR | Start leave | No | Information about current leave is useful when/if relatives/the citizen reaches out during the leave. The treatment responsibility for the patient on leave lies at the hospital and must be communicated separately if actors other than the hospital delivers care services during the patient’s leave. |
| Patient ends leave | SLOR | End leave | No | |
| Cancellations | ||||
| Send cancellation (used for wring patient/CPR.number or incorrect type of ‘Hosital Notification’) | AN_XX | Cancellation ’XX’, e.g Cancellation Start hospital stay - admitted | No | Cancellation of previously sent notifications. Is used in case of wrong choice of hospital stay or wrong personal identification number (CPR). |
| Corrections | ||||
| Send correction (wrong department or time) | RE_XX | Correction ’XX’, e.g Correction Start hospital stay - admitted | No | Corrects content in previously sent notifications, for example hospital department or time. |
*represents danish codes names described in the overview of HospitalNotification codes
6 Business rules for application
The following business rules have been agreed for the application of ‘Hospital Notification’. Please note that for the technical implementation, a number of use cases have been prepared, where functionalities and business rules for use have been translated into a number of detailed use cases for sender and receiver systems.Click here too read the use cases.
| # | Business rule |
|---|---|
| 1 | Hospital Notifications are generated based on real-time registration in the EPR/PAS system. If EPR uses future registrations of planned contacts, ‘Hospital Notifications’ should only be triggered when the time occurs, i.e. at the patient's physical attendance. |
| 2 | ‘End hospital stay’ (admission and acute ambulant care) is only used when the patient is discharged (and sent home/to the primary sector). Notification of this type cannot be used in case of transfers[1]. |
| 3 | If an acute ambulant stay is changed to the patient being admitted, a new 'Start hospital stay – admitted' notification is sent. No ‘End hospital stay' notification should be sent when the acute ambulant stay changes to the patient being admitted. Notification ‘End hospital stay’ is sent when the patient is subsequently discharged (sent home/to the primary sector) |
| 4 | If an admission changes to acute ambulant care, a new 'Start hospital stay – acute ambulant' notification is sent. No ‘End hospital stay' notification should be sent when the admission changes to acute ambulant care. Notification 'End hospital stay' is sent when the patient is subsequently discharged (sent home/to the primary sector). This occurrence is seen as rare. |
| 5 | If the patient is declared dead on arrival, dies after arrival or during the hospital stay, the notification of the type 'Death' is sent. The notification type 'Death' should be used in all cases where the patient is dead or dies. |
| 6 | If the patient is registered as on leave in the EPR, a notification is sent when the patient starts ('Start leave') and finishes ('End leave') his/hers leave (at home). Leave notifications are only sent when the patient is registered as being on leave at home. Leave in case of a double admission[2] must not trigger a leave notification. Leave notifications should not activate care services in the municipality unless otherwise agreed. |
| 7 | If an incorrect registration has happened, which has caused an incorrect ‘Hospital Notification’, a correction or cancellation must be sent on the following principles: a. If a ‘Hospital Notification’ has been sent because of a wrongly entered personal identification number (CPR) or wrong choice of hospital stay, a cancellation is sent. b.If a ‘Hospital Notification’ with the wrongly stated hospital department or time of stay is sent, a correction is sent, i.e. a new correct notification that replaces previous notifications. Cancellation is not sent prior to the correction. |
| 8 | No specific transfer notification is used. It is required that a new ‘Hospital Notification’ is sent from the hospital that the patient is transferred to, whether it is in the same or another region). No ‘Hospital Notification’ is sent from the hospital that the patient is transferred from[3]. |
| 9 | Discharge to hospice Same flow as for transfer to another hospital in the same or another region is used. Hospice sends 'Start hospital stay – admitted' when the patient arrives. |
1 If the patient is responsible for transport from hospital A to hospital B him-/herself, ‘End hospital stay’ can be used. The planned transfer should be communicated to the receiver in the care process plan or in a correspondence message. 2 Admission in psychiatric and somatic departments at the same time. 3 If the patient is responsible for transport from hospital A to hospital B him-/herself, ‘End hospital stay’ can be used. The planned transfer should be communicated to the receiver in the care process plan or in a correspondence message.
7 Example
Figure 1 shows an example of what a HospitalNotification could look like.
Note This is an example of what the HospitalNotification could look like. In the notification, the 'status on hospital stay' will indicate which event has caused the electronic notification.
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.7 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"