HL7 Terminology
2.0.0 - Publication
This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/mif-conceptRelationshipKind |
Name: | MIFConceptRelationshipKind |
Title: | MIF Concept Relationship Kind |
Status: | Draft as of 2020-11-07T09:27:49+11:00 |
Definition: | Codes for use in the ext-mif-relationship-relationshipKind to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.relationshipKind values |
Source Resource: | XML / JSON / Turtle |
References
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra
where concept is-a MIF-ConceptRelationshipKindThis value set excludes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra
Code | Display | Definition |
MIF-ConceptRelationshipKind | Grouper code for MIF SupportedConceptRelationship.relationshipKind codes |
This value set contains 13 concepts
Expansion based on HL7 Terminology Maintenance Infrastructure Vocabulary v2.1.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra
Code | Display | Definition |
Specializes | The child code is a more narrow version of concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymetric. | |
ComponentOf | The child code is a part of the concept represented by the parent code. Used to determine allowed nesting, for example of address components. Must be transitive, irreflexive, antisymetric. | |
GroupedBy | The child code is a part of a grouping represented by the parent code. Used to determine navigational hierarchy not based on a specializes or component relationship. E.g. ICD9 hierarchy. Is transitive, irreflexive and antisymetric | |
LessThan | For coded ordeinal code systems, indicates that the specified code is considered less than the related code. Used to determine relationships for coded ordinals. Must be transitive, irreflexive, antisymetric. | |
DefinitionallyQualifies | Identifies a code that can act as a qualifier for the referenced code, both as part of concept definition within the code system and as part of run-time concept definition to determine concepts allowed for use as qualifiers for a concept within a CD datatype. Must be non-transitive, irreflexive. | |
NonDefinitionallyQualifies | Same as definitionally qualifies, but restricted to only being used at run-time. Must be non-transitive, irreflexive. | |
Generalizes | Inverse of Specializes. Only included as a derived relationship | |
Component | Inverse of ComponentOf. Only included as a derived relationship | |
InGroup | Inverse of GroupedBy. Only included as a derived relationship | |
GreaterThan | Inverse of LessThan. Only included as a derived relationship | |
DefinitionallyQualifiedBy | Inverse of DefinitionallyQualifies. Only included as a derived relationship | |
NonDefinitionallyQualifiedBy | Inverse of NonDefinitionallyQualifies. Only included as a derived relationship | |
Other | The child code has a relationship with the parent that does not follow one of the pre-defined stereotypical patterns. Any application behavior based on the relationship must be custom-coded. Transitivity, Reflexivity and Symmetry must be asserted |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |
History
Date | Action | Custodian | Author | Comment |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |