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: MedComHospitalNotificationMessage

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

A message for a HospitalNotification. The message is triggered as patients are admitted, onleave or has finished a hospital stay in order to notify the relevant Municipalicy home care

Scope and usage

This profile is the root profile of MedCom HospitalNotification message. This profile is inherited from the MedComMessagingMessage. The following figure represent the profiles that shall be included in a MedCom FHIR HospitalNotification message.

Shows the structure of a HospitalNotification message. The MedComHospitalNotificationMessage includes a MedComHospitalNotificationMessageHeader and a MedComMessagingProvenance. 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.

The Bundle containing the HospitalNotification message is selfcontained, why it shall contain one instance of the MedComHospitalNotificationMessageHeader. By convention the cardinality is shown as 0..*.

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

Usage:

Formal Views of Profile Content

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

This structure is derived from MedComMessagingMessage

NameFlagsCard.TypeDescription & Constraintsdoco
.. Bundle C0..*MedComMessagingMessageContains a collection of resources
medcom-hospitalNotification-1: The message header shall conform to medcom-hospitalNotification-messageHeader profile
medcom-hospitalNotification-2: Entry shall contain exactly one patient resource
medcom-hospitalNotification-3: All provenance resources shall contain activities from medcom-hospitalNotification-messageActivities valueset
medcom-hospitalNotification-4: The system of Patient.identifier shall be 'urn:oid:1.2.208.176.1.2', which represents an official Danish CPR-number
medcom-hospitalNotification-5: The receiver of a HospitalNotification shall always be a primary receiver.
... id 1..1idA unique identifier for a bundle. The element must be updated with a new value each time a new message is sent.
... timestamp 1..1instantHolds information about when a bundle is created.
... entry 0..*BackboneElementMessage content (MedComHospitalNotificationMessageHeader, MedComMessagingOrganization, MedComMessagingProvenance, MedComHospitalNotificationEncounter, MedComCorePatient) - Open

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
medcom-hospitalNotification-1errorBundleThe message header shall conform to medcom-hospitalNotification-messageHeader profile
: entry.ofType(MessageHeader).all(resource.conformsTo('http://medcomfhir.dk/fhir/hospitalnotification/StructureDefinition/medcom-hospitalNotification-messageHeader'))
medcom-hospitalNotification-2errorBundleEntry shall contain exactly one patient resource
: entry.where(resource.is(Patient)).count() = 1
medcom-hospitalNotification-3errorBundleAll provenance resources shall contain activities from medcom-hospitalNotification-messageActivities valueset
: entry.ofType(Provenance).all(resource.activity.memberOf('http://medcomfhir.dk/fhir/dk-medcom-terminology/ValueSet/medcom-hospitalNotification-messageActivities'))
medcom-hospitalNotification-4errorBundleThe system of Patient.identifier shall be 'urn:oid:1.2.208.176.1.2', which represents an official Danish CPR-number
: entry.resource.ofType(Patient).identifier.system = 'urn:oid:1.2.208.176.1.2'
medcom-hospitalNotification-5errorBundleThe receiver of a HospitalNotification shall always be a primary receiver.
: Bundle.entry.resource.ofType(MessageHeader).destination.extension.value.code = 'primary'

 

Other representations of profile: CSV, Excel, Schematron