US Veterans Health Administration FHIR Map Set Implementation Guide
1.3.1 - 250401
Publication Build: This will be filled in by the publication tooling
Official URL: http://va.gov/fhir/ValueSet/PharmacyPersonType | Version: 1.3.1 | |||
Active as of 2025-03-31 | Computable Name: PharmacyPersonType |
FHIR Target ValueSet for Terminology Maps VF_PharmacyPersonType
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
This value set contains the valid values for FHIR. The source values from VistA are mapped to these values in the linked ConceptMap.
Generated Narrative: ValueSet PharmacyPersonType
http://terminology.hl7.org/CodeSystem/subscriber-relationship
Code | Display | Definition |
self | Self | The Beneficiary is the Subscriber |
spouse | Spouse | The Beneficiary is a spouse or equivalent of the Subscriber |
other | Other | The Beneficiary has some other relationship the Subscriber |
ValueSet
Expansion performed internally based on codesystem SubscriberPolicyholder Relationship Codes v1.0.1 (CodeSystem)
This value set contains 3 concepts
Code | System | Display (en-US) | Definition |
self | http://terminology.hl7.org/CodeSystem/subscriber-relationship | The Beneficiary is the Subscriber | |
spouse | http://terminology.hl7.org/CodeSystem/subscriber-relationship | The Beneficiary is a spouse or equivalent of the Subscriber | |
other | http://terminology.hl7.org/CodeSystem/subscriber-relationship | The Beneficiary has some other relationship the Subscriber |
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 |