Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-SignificantOtherRoleType-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5V3SignificantOtherRoleTypeForR4 | ||
This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-SignificantOtherRoleType|2.0.0 for use in FHIR R4.
This value set is part of the cross-version definitions generated to enable use of the
value set http://terminology.hl7.org/ValueSet/v3-SignificantOtherRoleType|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-SignificantOtherRoleType|2.0.0, defined in FHIR R5 does not have any mapping to FHIR R4
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-RoleCode version 📍2.2.0| Code | Display | Definition |
| DOMPART | domestic partner | The player of the role cohabits with the scoping person but is not the scoping person's spouse. |
| FMRSPS | former spouse | Player of the role was previously joined to the scoping person in marriage and this marriage is now dissolved and inactive. *Usage Note:* This is significant to indicate as some jurisdictions have different legal requirements for former spouse to access the patient's record, from a general friend. |
| HUSB | husband | The player of the role is a man joined to a woman (scoping person) in marriage. |
| SIGOTHR | significant other | A person who is important to one's well being; especially a spouse or one in a similar relationship. (The player is the one who is important) |
| SPS | spouse | The player of the role is a marriage partner of the scoping person. |
| WIFE | wife | The player of the role is a woman joined to a man (scoping person) in marriage. |
This value set expansion contains 6 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-RoleCode | 2.2.0 | DOMPART | domestic partner | The player of the role cohabits with the scoping person but is not the scoping person's spouse. | ||
http://terminology.hl7.org/CodeSystem/v3-RoleCode | 2.2.0 | FMRSPS | former spouse | Player of the role was previously joined to the scoping person in marriage and this marriage is now dissolved and inactive. Usage Note: This is significant to indicate as some jurisdictions have different legal requirements for former spouse to access the patient's record, from a general friend. | ||
http://terminology.hl7.org/CodeSystem/v3-RoleCode | 2.2.0 | HUSB | husband | The player of the role is a man joined to a woman (scoping person) in marriage. | ||
http://terminology.hl7.org/CodeSystem/v3-RoleCode | 2.2.0 | SIGOTHR | significant other | A person who is important to one's well being; especially a spouse or one in a similar relationship. (The player is the one who is important) | ||
http://terminology.hl7.org/CodeSystem/v3-RoleCode | 2.2.0 | SPS | spouse | The player of the role is a marriage partner of the scoping person. | ||
http://terminology.hl7.org/CodeSystem/v3-RoleCode | 2.2.0 | WIFE | wife | The player of the role is a woman joined to a man (scoping person) in marriage. |
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 |