Unattributed Code Systems

• http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-message-definition-type
• http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-activityCodes
• http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-destinationUse
• http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-eventCodes

Copyright Fragment

This fragment is not visible to the reader

Copyright and Registered Trademark Uses

• IG © 2021+ MedCom. Package medcom.fhir.dk.messaging#3.0.0 based on FHIR 4.0.1. Generated 2025-05-14 Links: Table of Contents | QA Report | Accessibility statement (Tilgængelighedserklæring) ( src )
• hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
• This Implementation Guide (IG) is provided by MedCom to describe the use of FHIR ®© in message based exchange of data in Danish healthcare. ( src )

External References

Type	Reference	Content
web	medcomfhir.dk	http://medcomfhir.dk/unknown
web	www.medcom.dk
web	www.medcom.dk	IG © 2021+ MedCom . Package medcom.fhir.dk.messaging#3.0.0 based on FHIR 4.0.1 . Generated 2025-05-14 Links: Table of Contents | QA Report | Accessibility statement (Tilgængelighedserklæring)
web	www.was.digst.dk	Links: Table of Contents | QA Report | Accessibility statement (Tilgængelighedserklæring)
web	en.wikipedia.org	Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ).
web	www.omg.org	Mappings for ServD ( http://www.omg.org/spec/ServD/1.0/ )
web	medcomfhir.dk	The activitycodes used to describe the activity of the MedCom message may differ between standard e.g. HospitalNotification and CareCommunication . Due to the different requirements of activities in a standard, it should be expected that there will be different invariants pointing at specific ValueSets for the given standard.
web	medcomfhir.dk	The activitycodes used to describe the activity of the MedCom message may differ between standard e.g. HospitalNotification and CareCommunication . Due to the different requirements of activities in a standard, it should be expected that there will be different invariants pointing at specific ValueSets for the given standard.
web	medcomfhir.dk	The IG contains profiles which are used to define a general messaging model for MedCom messages, like HospitalNotification , CareCommunication and Acknowledgement .
web	medcomfhir.dk	The IG contains profiles which are used to define a general messaging model for MedCom messages, like HospitalNotification , CareCommunication and Acknowledgement .
web	medcomfhir.dk	The IG contains profiles which are used to define a general messaging model for MedCom messages, like HospitalNotification , CareCommunication and Acknowledgement .
web	hl7.dk	This IG has a dependency to the MedComCore IG and DK-core v. 2.0.0, defined by HL7 Denmark . This is currently reflected in MedComMessagingOrganization which inherits from MedComCoreOrganization.
web	hl7.dk	This IG has a dependency to the MedComCore IG and DK-core v. 2.0.0, defined by HL7 Denmark . This is currently reflected in MedComMessagingOrganization which inherits from MedComCoreOrganization.
web	medcomdk.github.io	More information about MedCom Messaging can be found here. MedComMessaging profiles does not alone constitute a standard, why the documentation is limited.
web	github.com	FHIR profiles are managed under MedCom: Source code .
web	medcomdk.github.io	A description of governance concerning change management and versioning of MedComs FHIR artefacts, can be found on the link.
web	www.medcom.dk	MedCom is responsible for this IG.

Internal Images

MedComMessageHeader.png

MedComMessagingProvenance.png

MessagingModel.png