Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR R5 - Downloaded Version null See the Directory of published versions

ValueSet: R4V3Hl7CMETAttributionForR5

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R4-v3-hl7CMETAttribution-for-R5 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Responsible: HL7 International / Terminology Infrastructure Computable Name: R4V3Hl7CMETAttributionForR5

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-hl7CMETAttribution|2018-08-12 for use in FHIR R5.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/v3-hl7CMETAttribution|2018-08-12 as defined in FHIR R4 in FHIR R5.

The source value set is bound to the following FHIR R4 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-hl7CMETAttribution|2018-08-12, defined in FHIR R4 does not have any mapping to FHIR R5

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution version 📍2018-08-12
    CodeDisplayDefinition
    contactcontactDescription: Provides sufficient information to allow the object identified to be contacted. This is likely to have the content of identified and confirmable plus telephone number.
    identifiedidentifiedDescription: This variant is a proper subset of universal and is intended to provide sufficient information to identify the object(s) modeled by the CMET. This variant is only suitable for use within TIGHTLY COUPLED SYSTEMS ONLY. This variant provides ONLY the ID (and code where applicable) and Name. Other variants may not be substituted at runtime.
    identified-confirmableidentified-confirmableDescription: This extends the identified variant by adding just sufficient additional information to allow the identity of object modeled to be confirmed by a number of corroborating items of data; for instance a patient's date of birth and current address. However, specific contact information, such as telephone number, are not viewed as confirming information.
    identified-informationalidentified-informationalDescription: Generally the same information content as "contactable" but using new "informational" CMETs as dependant CMETs. This flavor allows expression of the CMET when non-focal class information is not known.
    informationalinformationalDescription: Generally the same information content as "contactable", but with required (not mandatory) ids on entry point class. This flavor allows expression of the CMET even when mandatory information is not known.
    minimalminimalDescription: Provides more than identified, but not as much as universal. There are not expected to be many of these.
    universaluniversalDescription: This variant includes all attributes and associations present in the R-MIM. Any of non-mandatory and non-required attributes and/or associations may be present or absent, as permitted in the cardinality constraints.

 

Expansion

This value set expansion contains 7 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution2018-08-12  contactcontactDescription: Provides sufficient information to allow the object identified to be contacted. This is likely to have the content of identified and confirmable plus telephone number.
http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution2018-08-12  identifiedidentifiedDescription: This variant is a proper subset of universal and is intended to provide sufficient information to identify the object(s) modeled by the CMET. This variant is only suitable for use within TIGHTLY COUPLED SYSTEMS ONLY. This variant provides ONLY the ID (and code where applicable) and Name. Other variants may not be substituted at runtime.
http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution2018-08-12  identified-confirmableidentified-confirmableDescription: This extends the identified variant by adding just sufficient additional information to allow the identity of object modeled to be confirmed by a number of corroborating items of data; for instance a patient's date of birth and current address. However, specific contact information, such as telephone number, are not viewed as confirming information.
http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution2018-08-12  identified-informationalidentified-informationalDescription: Generally the same information content as "contactable" but using new "informational" CMETs as dependant CMETs. This flavor allows expression of the CMET when non-focal class information is not known.
http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution2018-08-12  informationalinformationalDescription: Generally the same information content as "contactable", but with required (not mandatory) ids on entry point class. This flavor allows expression of the CMET even when mandatory information is not known.
http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution2018-08-12  minimalminimalDescription: Provides more than identified, but not as much as universal. There are not expected to be many of these.
http://terminology.hl7.org/CodeSystem/v3-hl7CMETAttribution2018-08-12  universaluniversalDescription: This variant includes all attributes and associations present in the R-MIM. Any of non-mandatory and non-required attributes and/or associations may be present or absent, as permitted in the cardinality constraints.

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