Terminology Change Set Exchange, published by HL7 International / Terminology Infrastructure. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/termchangeset-ig/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/uv/termchangeset/ValueSet/defining-relationship-type-vs | Version: 1.0.0 | |||
Standards status: Draft | Maturity Level: 0 | Computable Name: DefiningRelationshipTypeVS | ||
Copyright/Legal: This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement |
Codes describing the nature of a relationship used to define a terminology concept. The value set includes all codes from the SNOMED CT descending from 900000000000006009 Defining relationship.
References
Generated Narrative: ValueSet defining-relationship-type-vs
http://snomed.info/sct
where concept descends from 900000000000006009 (Defining relationship)
Generated Narrative: ValueSet
Expansion based on SNOMED CT International edition 01-Aug 2024
This value set expansion contains 2 concepts.
Code | System | Display |
900000000000010007 | http://snomed.info/sct | Stated relationship (core metadata concept) |
900000000000011006 | http://snomed.info/sct | Inferred relationship |
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 |
System | 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 |