This specification conforms to FHIR®© R4
Frequently asked qustions
On this page you will finde the answears to the most asked questions. Table of contents
1 Why are there Multiple Implementation Guides?
FHIR allows for a great deal of reuse. When creating a MedCom FHIR message, profiles from the MedComCore and MedComMessaging IG are used to create a complete understanding. Currently, there are three FHIR standards: HospitalNotification, CareCommunication and Acknowledgement, which all are composed of profiles from the Core and Messaging IG as well as the IG for the specific standard, and terminogy codes from the Terminology IG.
Keeping the IG’s seperate allows us to version them individually,meaning that updates in the MedComHospitalNotification IG will not affect the version of the MedComCareCommunication IG. However, an update in the MedComMessaging IG will affect all standard that use profiles or inherit profiles from this IG. Additionally, it makes it possible to reuse the profiles from the Core IG in different MedCom standard and in different exchange formats.
Figure 1 illustrates that the messaging standard uses multiple profiles from the Core and Messaging IG and uses some profiles that are specific to the given standard.
2 How does Inheritance Work and What is DKCore?
In Denmark, we have a national HL7 affiliate, called HL7-DK. The affiliate works on the development of international HL7 standards that supports healthcare. HL7-DK has focuses on profiling the international standard in a Danish context to provide a common foundation in Denmark. HL7-DK develops DK-core which are generic FHIR profiles that can be used freely for FHIR projects in Denmark. At present, DK-core includes the following profiles: DkCorePatient, DkCorePractitioner and DkCoreOrganization. The profile MedComCorePatient inherits from DKCorePatient. This means that when a MedCom standard uses a civil registration number (Danish: CPR-nummer) from DKCorePatient, it is defined in the same way as when other projects inherit from DK-core and use a civil registration number, securing consistency across projects. DKCorePatient is the foundation of MedComCorePatient,which is why MedComCorePatient is said to inherit from DKCorePatient.
Figure 2 also illustrates that there is a dependency between the IGs and the FHIR resources defined by HL7.
You can read more about the work of HL7-DK here.
About
Support or contact
MedCom is responsible for this page. If you have any questions regarding this page, please contact fhir@medcom.dk or write to MedCom's stream on Zulip.Version of this documentation
The version of this documentation is: Version 1.0.6 You can find the release note of the version here."FHIR® is the registered trademark of HL7 and is used with the permission of HL7. Use of the FHIR trademark does not constitute endorsement of this implementation guide by HL7, nor affirmation that this content is conformant to the various applicable standards"