DK MedCom HospitalNotification
3.0.1 - Release Denmark flag

This page is part of the DK MedCom HospitalNotification (v3.0.1: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Resource Profile: MedComHospitalNotificationMessageHeader

Official URL: http://medcomfhir.dk/ig/hospitalnotification/StructureDefinition/medcom-hospitalNotification-messageHeader Version: 3.0.1
Active as of 2023-03-02 Computable Name: MedComHospitalNotificationMessageHeader

MessageHeader for a HospitalNotification message.

Scope and usage

This profile is used as the MessageHeader resource for the MedCom HospitalNotification message. Constraints and rules from MedComMessagingMessageHeader are inherited to this profile, but MedComHospitalNotificationMessageHeader is further restricted as carbon-copy is not allowed. The MedComHospitalNotificationMessageHeader contains an id which shall be globally unique for each message and an event code which shall be hospital-notification-message for a HospitalNotification message. Additionally, is it required to include a serviceprovider organization in the message.

MedComHospitalNotificationMessageHeader references a sender and receiver organization in terms of the MedComMessagingOrganization, and a focus which is a reference to a MedComHospitalNotificationEncounter. From the MedComHospitalNotificationEncounter is a MedComCorePatient and a MedComCoreOrganization referenced.

Please refer to the tab “Snapshot Table(Must support)” below for the definition of the required content of a MedComHospitalNotificationMessageHeader.

Report of admission

The request for a report of admission from a municipality shall be sent when a patient is initially admitted either as an inpatient or emergency admission or when an patient admitted as an inpatient is moved to a hospital in another region. Technically this includes setting the MessageHeader.extension.reportOfAdmissionFlag to ‘true’ and include a reference to the receiver of the report of admission in the element MessageHeader.extension.reportOfAdmissionRecipient. Section 2.1, in the use case document describes more thoroughly in which cases the report of admission flag shall be sat to ‘true’. The request for a report of admission should be made automatically.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from MedComMessagingMessageHeader

NameFlagsCard.TypeDescription & Constraintsdoco
.. MessageHeader 0..*MedComMessagingMessageHeaderA resource that describes a message that is exchanged between systems
... id 1..1idA unique identifier for each message. This identifier should be globally unique.
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... reportOfAdmissionFlag SΣ0..1booleanMedComReportOfAdmissionExtension
URL: http://medcomfhir.dk/ig/hospitalnotification/StructureDefinition/medcom-messaging-reportOfAdmissionExtension
... event[x] 1..1CodingThe MedComMessagingMessageHeader shall contain the event value hospital-notification-message
... eventCoding 1..1CodingCode for the event this message represents or link to event definition
Required Pattern: At least the following
.... system1..1uriIdentity of the terminology system
Fixed Value: http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-eventCodes
.... code1..1codeSymbol in syntax defined by the system
Fixed Value: hospital-notification-message
... destination:cc 0..0
... focus S1..1Reference(MedComHospitalNotificationEncounter) {b}The actual content of the message

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron