Source | medcom.fhir.dk.messaging#current:DK MedCom Messaging (v4.0.1) |
resourceType | StructureDefinition |
id | medcom-messaging-message |
canonical | http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-message |
version | 2.0.0 |
status | active |
publisher | MedCom |
name | MedComMessagingMessage |
date | 2023-07-06T07:34:13+00:00 |
description | Base resource for all MedCom messages. |
jurisdictions | dk |
fhirVersion | 4.0.1 |
kind | resource |
abstract | false |
sdTtype | Bundle |
derivation | constraint |
base | http://hl7.org/fhir/StructureDefinition/Bundle |
Usages |
|
Name | Flags | Card. | Type |
Description & Constraints
![]() |
---|---|---|---|---|
![]() ![]() |
C | Bundle |
medcom-messaging-1:
The MessageHeader resource shall conform to medcom-messaging-messageHeader profile medcom-messaging-2: There shall be at least one Provenance resource in a MedCom message medcom-messaging-3: All Provenance resources shall conform to medcom-core-provenance profile |
|
![]() ![]() ![]() |
S | 1.. | ||
![]() ![]() ![]() |
S |
Always message Required Pattern: message |
||
![]() ![]() ![]() |
S | 1.. | ||
![]() ![]() ![]() |
S | |||
![]() ![]() ![]() ![]() |
S | Each MedCom message shall contain a MedComMessagingMessageHeader and MedComMessagingProvenance. Please refer to invariant medcom-messaging-1, medcom-messaging-2, and medcom-messaging-3. | ||
![]() |
Produced 08 Sep 2023