Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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: R5 R4B R4 R3

4.3.14.19 Code System http://hl7.org/fhir/relationship

Financial Management Work Group Maturity Level: 0Informative Use Context: Not Intended for Production use

This is a code system defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/relationship
Version:4.3.0
Name:Beneficiary Relationship Codes
Title:
Definition:

This value set includes the Patient to subscriber relationship codes.

Committee:Financial Management Work Group
OID:2.16.840.1.113883.4.642.1.36 (for OID based terminology systems)
Copyright:

This is an example set.

Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: Relationship (This value set includes the Patient to subscriber relationship codes.)

This code system http://hl7.org/fhir/relationship defines the following codes:

CodeDisplayDefinition
1 SelfThe patient is the subscriber (policy holder)
2 SpouseThe patient is the spouse or equivalent of the subscriber (policy holder)
3 ChildThe patient is the child of the subscriber (policy holder)
4 Common Law SpouseThe patient is the common law spouse of the subscriber (policy holder)
5 OtherThe patient has some other relationship, such as parent, to the subscriber (policy holder)

 

See the full registry of code systems defined as part of FHIR.


Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code