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

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

ValueSet: R5V3RoleClassSameForR3

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-RoleClassSame-for-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5V3RoleClassSameForR3

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-RoleClassSame|2.0.0 for use in FHIR STU3.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/v3-RoleClassSame|2.0.0 as defined in FHIR R5 in FHIR STU3.

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-RoleClassSame|2.0.0, defined in FHIR R5 does not have any mapping to FHIR STU3

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-RoleClass version 📍3.1.0
    CodeDisplayDefinition
    SAMEsameThe "same" role asserts an identity between playing and scoping entities, i.e., that they are in fact two records of the same entity instance, and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.

    *Usage:*

    playing and scoping entities must have same classCode, but need not have identical attributes or values.

    *Example:*

    a provider registry maintains sets of conflicting demographic data for what is reported to be the same individual.

 

Expansion

This value set expansion contains 1 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-RoleClass3.1.0  SAMEsame

The "same" role asserts an identity between playing and scoping entities, i.e., that they are in fact two records of the same entity instance, and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.

Usage:

playing and scoping entities must have same classCode, but need not have identical attributes or values.

Example:

a provider registry maintains sets of conflicting demographic data for what is reported to be the same individual.

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