This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3 R2
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/parent-relationship-codes |
Name: | Parent Relationship Codes |
Definition: | The value set includes the v3 RoleCode PRN (parent), TWIN (twin) and all of their specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. |
OID: | 2.16.840.1.113883.4.642.2.382 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
This expansion generated 24 Oct 2015
This value set contains 21 concepts
All codes from system http://hl7.org/fhir/v3/RoleCode
Code | Display |
PRN | parent |
ADOPTP | adoptive parent |
ADOPTF | adoptive father |
ADOPTM | adoptive mother |
FTH | father |
FTHFOST | foster father |
NFTH | natural father |
NFTHF | natural father of fetus |
STPFTH | stepfather |
MTH | mother |
GESTM | gestational mother |
MTHFOST | foster mother |
NMTH | natural mother |
NMTHF | natural mother of fetus |
STPMTH | stepmother |
NPRN | natural parent |
PRNFOST | foster parent |
STPPRN | step parent |
TWIN | twin |
FTWIN | fraternal twin |
ITWIN | identical twin |
See the full registry of value sets defined as part of FHIR.
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 |
Source | 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 |