This fragment is not visible to the reader
This publication includes IP covered under the following statements.
Type | Reference | Content |
---|---|---|
web | snomed.info | 723506003 |
web | snomed.info | 15240007 |
web | www.medcom.dk |
![]() |
web | www.medcom.dk |
IG © 2022+ MedCom
. Package medcom.fhir.dk.terminology#1.8.1 based on FHIR 4.0.1
. Generated 2025-05-12
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 | stps.dk | CodeSystem containing codes for practionerroles (Danish:Stillingsbetegnelser) from autorisationsregistret |
web | medinfo.dk | CodeSystem containing codes for practionerroles (Danish:Stillingsbetegnelser) from SKS Administrativt-Personaleklassifikation |
web | snomed.info | 723506003 |
web | snomed.info | 15240007 |
web | www.medcom.dk | This Implementation Guide (IG) is provided by MedCom and describes the use of FHIR ®© Terminology when exchanging information within the Danish healthcare sector. |
web | medcomfhir.dk | This IG contains CodeSystems, ValueSets, and ConceptMaps defined by MedCom and used in MedComs FHIR standards such as CareCommunication , HospitalNotification , and Acknowledgement . |
web | medcomfhir.dk | This IG contains CodeSystems, ValueSets, and ConceptMaps defined by MedCom and used in MedComs FHIR standards such as CareCommunication , HospitalNotification , and Acknowledgement . |
web | medcomfhir.dk | This IG contains CodeSystems, ValueSets, and ConceptMaps defined by MedCom and used in MedComs FHIR standards such as CareCommunication , HospitalNotification , and Acknowledgement . |
web | medcomfhir.dk | CodeSystems, ValueSets, and ConceptMaps can be found under Terminology . They are provided together with their associated historical versions, which can be found under the individual CodeSystems, ValueSets, and ConceptMaps. |
web | medcomfhir.dk | CodeSystems declares the existence of a code system or code system supplement. CodeSystems defines which codes exists and how they should be understood to avoid ambiguities. An example of a CodeSystem defined by MedCom is MedComMessagingActivityCodes which defines the activity of a certain message e.g., a new-message or a admit-inpatient depending on which message is send. |
web | medcomfhir.dk | ValueSets specifies a set of codes drawn from one or more CodeSystems, intended for use in a particular context. A ValueSet constitutes the selection of possible codes that can be used for a specific codable element in a profile. An example of a ValueSet defined by MedCom is MedComHospitalNotificationMessageActivityCodes , which describes the possible activities for at HospitalNotification message e.g., an admit-inpatient message. The ValueSet MedComCareCommunicationMessageActivityCodes is another example, which includes codes to describe the possible activities for a CareCommunication message. Both ValueSets are originated from the same CodeSystem MedComMessagingActivityCodes . |
web | medcomfhir.dk | ValueSets specifies a set of codes drawn from one or more CodeSystems, intended for use in a particular context. A ValueSet constitutes the selection of possible codes that can be used for a specific codable element in a profile. An example of a ValueSet defined by MedCom is MedComHospitalNotificationMessageActivityCodes , which describes the possible activities for at HospitalNotification message e.g., an admit-inpatient message. The ValueSet MedComCareCommunicationMessageActivityCodes is another example, which includes codes to describe the possible activities for a CareCommunication message. Both ValueSets are originated from the same CodeSystem MedComMessagingActivityCodes . |
web | medcomfhir.dk | ValueSets specifies a set of codes drawn from one or more CodeSystems, intended for use in a particular context. A ValueSet constitutes the selection of possible codes that can be used for a specific codable element in a profile. An example of a ValueSet defined by MedCom is MedComHospitalNotificationMessageActivityCodes , which describes the possible activities for at HospitalNotification message e.g., an admit-inpatient message. The ValueSet MedComCareCommunicationMessageActivityCodes is another example, which includes codes to describe the possible activities for a CareCommunication message. Both ValueSets are originated from the same CodeSystem MedComMessagingActivityCodes . |
web | medcomfhir.dk | Some ValueSets are intensional defined, meaning that all codes from a CodeSystem are included. Whenever the CodeSystem is updated, so is the ValueSet. For intensional defined ValueSets, there will always only be one active ValueSets, with a date for latest update. This way of defining ValueSets will account for ValueSets used to describe the content of a message, such as MedComCareCommunicationCategoryCodes . Therefore vendors shall expect that the codes in this type of ValueSets will change, based on the requirements in the healthcare sector. |
web | medcomfhir.dk | Other ValueSets are extensional defined, meaning that codes from CodeSystems are explicitly listed in each ValueSet. Therefore, will ValueSets not be automatically updated when a CodeSystem is, it requires a change in the ValueSet. This applies for ValueSets including codes used for routing of a message and the logical setup within a system, such as MedComHospitalNotificationMessageActivityCodes . There may be more than one active ValueSet, as changes in this type of ValueSet often takes time to implement. |
web | medcomfhir.dk | ConceptMaps defines mapping between one set of concepts to one or more concepts. An example of a ConceptMaps is MedComMessagingMapFhirToSorEdi , which represents a mapping between names of MedComs FHIR messages and names of SOR-EDI messages. |
web | medcomdk.github.io | This page the governance concerning updating, maintaining and versioning CodeSystems, ValueSets and ConceptMaps. |
web | medcomfhir.dk | Currently it is possible to download the terminologies in different formats. The vendor of the system is responsible for using updated terminologies. |
web | github.com | If you want to be notified about the recent update of the terminology IG please go to the dk-medcom-terminology GitHub Repository and click 'Watch' in the upper right corner and choose the level of notifications you want. |
web | www.medcom.dk | MedCom is responsible for this site. If you have any questions, please contact fhir@medcom.dk or write to MedCom’s stream in Zulip . |