This fragment is not visible to the reader
This publication includes IP covered under the following statements.
Type | Reference | Content |
---|---|---|
web | www.medcom.dk |
![]() |
web | github.com | DK MedCom Core, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 2.4.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-core/ and changes regularly. See the Directory of published versions |
web | www.medcom.dk |
IG © 2021+ MedCom
. Package medcom.fhir.dk.core#2.4.0 based on FHIR 4.0.1
. Generated 2025-06-30
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 | medcomfhir.dk | In MedComCoreDiagnosticReport it is allowed to include attachments. When sending an attachment diagnosticReport.media shall be used. The DiagnosticReport.media.link reference to MedComCoreMedia resource where the atachment shall be added. It is up to the user to assess when it is relevant to send an attachment. Only an attachment of the permitted formats must be included. Click here to see the permitted formats of an attachment |
web | medcomfhir.dk | The base expectations when describing an encounter in a Danish context is to include the subject of the encounter which shall be a MedComCorePatient as well as a status and class, which are described below. For some specific purposes, such as HospitalNotification , there is a need for a specialization of the MedComCoreEncounter. In these cases, it will be explicitly described which encounter to use and which changed are applied. |
web | medcomfhir.dk | The base expectations when describing an encounter in a Danish context is to include the subject of the encounter which shall be a MedComCorePatient as well as a status and class, which are described below. For some specific purposes, such as HospitalNotification , there is a need for a specialization of the MedComCoreEncounter. In these cases, it will be explicitly described which encounter to use and which changed are applied. |
web | www.esundhed.dk | It is both possible to use a Landspatientregisteret -identifier (called LPR3-identifier) and a locally defined identifier as the EpisodeOfCare-identifier. |
web | scandihealth.github.io | Whether a LPR3-identifier or a locally defined identifier is used, it shall be an UUID. The LPR3-identifier shall obey a rule stating that the UUID shall be of version 5, here more information about the LPR3-identifier can be found . Using a locally defined identifier, a system for the identifier shall be added. |
web | medcomfhir.dk | Only an attachment of the permitted formats must be included. Click here to see the permitted formats of an attachment |
web | hl7.dk | This profile describes the MedComCoreOrganization. The MedComCorePractitioner is inherited from the DkCoreOrganization profile defined by HL7 Denmark. The base expectations when describing an organisation in a Danish context is to include an identifier, in terms of a Sundhundsvæsenets Organisations Register (SOR)-identifier. This profile is used to describe e.g. the organisation responsible for an encounter. |
web | medcomfhir.dk | When using an organisation for exchange purposes, such as a sender, receiver or carbon-copy, please refer to the MedComMessagingOrganization . |
web | hl7.dk | MedComCorePatient profile describes information about a patient or citizen in a MedCom standard. The MedComCorePatient is inherited from the DkCorePatient profile defined by HL7 Denmark. An identifier and the patients official family name ('efternavn' in Danish) shall both be present, when exchanging patient related information. |
web | hl7.dk | When a patient has an official civil person register (CPR)-number this shall be used. To represent a CPR-number, the identifier DkCoreCprIdentifier shall be used. In the identifier the system is used to describes that value is an official CPR-number, as described on cpr.dk . |
web | cpr.dk | When a patient has an official civil person register (CPR)-number this shall be used. To represent a CPR-number, the identifier DkCoreCprIdentifier shall be used. In the identifier the system is used to describes that value is an official CPR-number, as described on cpr.dk . |
web | hl7.dk | Only in cases where the patient does not have an official CPR-number, a replacement person identifier (Danish: Erstatningspersonnummer) (eCPR)-number shall be used. More information concerning the use of eCPR-numbers can be found on DkCorePatient . |
web | hl7.dk | This profile describes the MedComCorePractitioner which is used to describe a Practitioner in a MedCom standard. The MedComCorePractitioner is inherited from the DkCorePractitioner profile defined by HL7 Denmark. The only change is that MedComCorePractitioner shall include a name of the practitioner if it is available. |
web | medcomfhir.dk | It is prefered to use a code from MedComCorePractitionerRoles . If these does not cover the needs, the roles can be included in a string at PractitionerRole.code.text. |
web | hl7.dk | This IG has a dependency to DK-core v. 2.0.0, defined by HL7 Denmark . This is currently reflected in the MedComCorePatient, MedComCoreOrganization and MedComCorePractitioner which inherit from DkCorePatient, DkCoreOrganization and DkCorePractitioner, respectively. |
web | hl7.dk | This IG has a dependency to DK-core v. 2.0.0, defined by HL7 Denmark . This is currently reflected in the MedComCorePatient, MedComCoreOrganization and MedComCorePractitioner which inherit from DkCorePatient, DkCoreOrganization and DkCorePractitioner, respectively. |
web | medcomdk.github.io | More information about MedCom Core can be found here. As mentioned, MedCom Core does not alone constitute a standard, why the extra 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. |
tree-filter.png ![]() |