MedCom MessageDefinitions
1.0.0 - trial-use Denmark flag

MedCom MessageDefinitions, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-medcom-messagedefinitions/ and changes regularly. See the Directory of published versions

Resource Profile: MedComMessagingMessageDefinition - Mappings

Draft as of 2025-09-24

Mappings for the medcom-messaging-messagedefinition resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameHL7 v2 MappingRIM MappingWorkflow PatternFiveWs Pattern MappingObject Implementation Informationdoco
.. MessageDefinition
N/A
N/A
... id
... meta
... implicitRules
... language
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... url
Definition.url
FiveWs.identifier
... identifier
Definition.identifier
FiveWs.identifier
no-gen-base
.... id
n/a
.... extension
n/a
.... use
N/A
Role.code or implied by context
.... type
CX.5
Role.code or implied by context
..... id
n/a
..... extension
n/a
..... coding
  • C*E.1-8
  • C*E.10-22
  • union(.
  • ./translation)
...... id
n/a
...... extension
n/a
...... system
C*E.3
./codeSystem
...... version
C*E.7
./codeSystemVersion
...... code
C*E.1
./code
...... display
C*E.2 - but note this is not well followed
CV.displayName
...... userSelected
Sometimes implied by being first
CD.codingRationale
..... text
C*E.9. But note many systems use C*E.2 for this
./originalText[mediaType/code="text/plain"]/data
.... system
CX.4 / EI-2-4
II.root or Role.id.root
.... value
CX.1 / EI.1
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
.... period
CX.7 + CX.8
Role.effectiveTime or implied by context
..... id
n/a
..... extension
n/a
..... start
DR.1
./low
..... end
DR.2
./high
.... assigner
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
... version
Definition.version
FiveWs.version
... name
... title
Definition.title
... replaces
.... id
.... extension
.... value
... status
Definition.status
FiveWs.status
... experimental
Definition.experimental
FiveWs.class
... date
Definition.date
FiveWs.recorded
... publisher
Definition.publisher
FiveWs.witness
... Slices for contact
Definition.contact
.... contact:AuthorOrganization
Definition.contact
..... id
n/a
..... extension
n/a
..... name
..... telecom
...... id
n/a
...... extension
n/a
...... system
XTN.3
./scheme
...... value
XTN.1 (or XTN.12)
./url
...... use
XTN.2 - but often indicated by field
unique(./use)
...... rank
n/a
n/a
...... period
N/A
./usablePeriod[type="IVL<TS>"]
... description
Definition.description
... useContext
Definition.useContext
.... id
n/a
.... extension
n/a
.... code
..... id
n/a
..... extension
n/a
..... system
C*E.3
./codeSystem
..... version
C*E.7
./codeSystemVersion
..... code
C*E.1
./code
..... display
C*E.2 - but note this is not well followed
CV.displayName
..... userSelected
Sometimes implied by being first
CD.codingRationale
.... value[x]
... jurisdiction
Definition.jurisdiction
... purpose
Definition.purpose
FiveWs.why[x]
no-gen-base
... copyright
Definition.copyright
no-gen-base
... base
... parent
... event[x]
... category
... focus
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... code
.... profile
.... min
.... max
... responseRequired
MSH-16
... allowedResponse
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... message
.... situation
... graph

doco Documentation for this format