Extensions for Using Data Elements from FHIR R5 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-ConceptPropertyId-for-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5V3ConceptPropertyIdForR4B | ||
This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-ConceptPropertyId|2.0.0 for use in FHIR R4B.
This value set is part of the cross-version definitions generated to enable use of the
value set http://terminology.hl7.org/ValueSet/v3-ConceptPropertyId|2.0.0 as defined in FHIR R5
in FHIR R4B.
The source value set is bound to the following FHIR R5 elements:
Note that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://terminology.hl7.org/ValueSet/v3-ConceptPropertyId|2.0.0, defined in FHIR R5 does not have any mapping to FHIR R4B
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty version 📍2.0.1| Code | Display | Definition |
| OID | ISO Object Identifier | Object identifier assigned to a concept |
| _ValueSetPropertyId | ValueSetPropertyId | Property identifiers for a value sets |
| appliesTo | applies to | Entity to which a given value set or concept code applies |
| conceptStatusQualifier | concept status qualifier | **Description:** Qualifier value for concept status. |
| howApplies | how applies | Description of how set or code applies |
| inverseRelationship | inverted relationship name | Name that should be used when the relationship is used in the reverse (target to source) direction. Example: The inverse relationship of hasPart is isPartOf |
| openIssue | open issue | Outstanding issue that still needs resolution |
| specializedByDomain | specialized by domain | **Description:**specialized by domain |
This value set expansion contains 8 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | OID | ISO Object Identifier | Object identifier assigned to a concept | ||
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | _ValueSetPropertyId | ValueSetPropertyId | Property identifiers for a value sets | ||
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | appliesTo | applies to | Entity to which a given value set or concept code applies | ||
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | conceptStatusQualifier | concept status qualifier | **Description:** Qualifier value for concept status. | ||
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | howApplies | how applies | Description of how set or code applies | ||
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | inverseRelationship | inverted relationship name | Name that should be used when the relationship is used in the reverse (target to source) direction. Example: The inverse relationship of hasPart is isPartOf | ||
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | openIssue | open issue | Outstanding issue that still needs resolution | ||
http://terminology.hl7.org/CodeSystem/v3-ConceptProperty | 2.0.1 | specializedByDomain | specialized by domain | **Description:**specialized by domain |
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 |