This specification conforms to FHIR®© R4
Governance of MedCom FHIR Terminologies
Table of content
- 1 MedCom FHIR Codesystems
- 2 MedCom FHIR ValueSets
- 3 MedCom FHIR ConceptMaps
- 4 Links for MedCom FHIR Terminology
The term Terminology is in this governance a term covering all kinds of terminology, classifications, enumerations and qualifiers.
All elements of a MedCom FHIR Message SHALL be compliant with the terminologies that are pointed out by these elements.
All CodeSystems, ValueSets and ConceptMaps will have a status, and a latest changed date. The status indicates if the CodeSystems, ValueSets or ConceptMaps is draft, active, or retired. If the status is active the terminology is ready for use.
No updates will be made without consulting relevant working groups beforehand.
1 MedCom FHIR CodeSystems
No code in a CodeSystem will be deleted, nor will the meaning of a code be changed. Incompatible versions of a CodeSystem will have a unique name. However, codes in CodeSystems may be deprecated with a deprecation date and new codes may be added to the CodeSystem. In both cases will the version and date for latest change be updated.
2 MedCom FHIR ValueSets
Some ValueSets are intensional defined, meaning that all codes from a CodeSystem is 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. ValueSets used to describe the content of a message, such as Click here to read MedComCareCommunicationCategoryCodes
Other ValueSets are extensional defined, meaning that means that codes from CodeSystems are explicitly listed in each ValueSet. Therefore, will ValueSets not automatically be expanded when a CodeSystem is, it requires a change in the ValueSet. These ValueSets are used to describe the codes used for routing of a message and the logical setup within a system, such as Click here to read MedComHospitalNotificationMessageActivityCodes. There may be more than one active ValueSet, as changes may take time to implement.
In exceptional cases, it is possible to specify when defining a ValueSet that must not be changed or versioned.
3 MedCom FHIR ConceptMaps
As for ValueSets, the ConceptMaps may be more or less static, where the once used for messaging purposes will rarely change, and the once used to describe the content of a message may change more frequently.
A ConceptMap is valid until the date of a newer version of this ConceptMap is reached, then the newer version is valid. If a code in a CodeSystem is deprecated, a new version of the ConceptMaps is created, which will be valid.
4 Links for MedCom FHIR Terminology
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 MedComs stream on Zulip.Version of this documentation
The version of this documentation is: Version 1.0.6 You can finde 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"