<status value="active"/> <experimental value="false"/> <date value="2026-03-17T21:02:03.8104715+00:00"/> <publisher value="FHIR Infrastructure"/> <contact> <name value="FHIR Infrastructure"/> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/fiwg"/> </telecom> </contact> <description value="This cross-version ValueSet represents content from `http://terminology.hl7.org/ValueSet/v3-RoleClassSame|2.0.0` for use in FHIR R4."/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> <display value="World"/> </coding> </jurisdiction> <purpose value="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 R4. 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 R4"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-RoleClass"/> <version value="3.1.0"/> <concept> <code value="SAME"/> <display value="same"/> </concept> </include> </compose> <expansion> <timestamp value="2026-03-17T21:02:03.8104715+00:00"/> <contains> <system value="http://terminology.hl7.org/CodeSystem/v3-RoleClass"/> <version value="3.1.0"/> <code value="SAME"/> <display value="same"/> </contains> </expansion> </ValueSet>

Generated Narrative: ValueSet R5-v3-RoleClassSame-for-R4

This value set expansion contains 1 concepts.

System	Version	Code	Display	Definition
`http://terminology.hl7.org/CodeSystem/v3-RoleClass`	3.1.0	SAME	same	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.