Release 4B Snapshot 3: Connectathon 32 Base

This page is part of the FHIR Specification (v4.3.0: R4B - STU (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32 ). 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

Using Codes Code Systems Value Sets Concept Maps Identifier Systems

4.4.1.320 4.4.1.192 Value Set ValueSet http://hl7.org/fhir/ValueSet/sibling-relationship-codes

Patient Care icon Work Group   Maturity Level : 0 Informative Use Context : Any Country: World, Country: World
This is a value set defined by the FHIR project. Committee:
Official URL : Title: http://hl7.org/fhir/ValueSet/sibling-relationship-codes Sibling Relationship Codes Definition: The value set includes the v3 RoleCode SIB (sibling) and all of its specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. Version : 5.0.0-snapshot3
draft as of 2022-12-14 Patient Care Computable Name : SiblingRelationshipCodes Work Group
OID: Flags : 2.16.840.1.113883.4.642.3.922 (for OID based terminology systems) Source Resource XML / JSON : 2.16.840.1.113883.4.642.3.922

This value set is used in the following places:

The value set includes the v3 RoleCode SIB (sibling) and all of its specializations. It covers the relationships needed to establish genetic pedigree relationships between family members.


 

This expansion generated 28 May 14 Dec 2022


This value set contains 21 concepts

Expansion based on RoleCode v2.2.0 (CodeSystem) All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-RoleCode icon

Code System Display Definition
   SIB icon http://terminology.hl7.org/CodeSystem/v3-RoleCode sibling

The player of the role shares one or both parents in common with the scoping entity.

   BRO icon http://terminology.hl7.org/CodeSystem/v3-RoleCode brother

The player of the role is a male sharing one or both parents in common with the scoping entity.

   HBRO icon http://terminology.hl7.org/CodeSystem/v3-RoleCode half-brother

The player of the role is a male related to the scoping entity by sharing only one biological parent.

   NBRO icon http://terminology.hl7.org/CodeSystem/v3-RoleCode natural brother

The player of the role is a male having the same biological parents as the scoping entity.

   TWINBRO icon http://terminology.hl7.org/CodeSystem/v3-RoleCode twin brother

The scoper was carried in the same womb as the male player and shares common biological parents.

   FTWINBRO icon http://terminology.hl7.org/CodeSystem/v3-RoleCode fraternal twin brother

The scoper was carried in the same womb as the male player and shares common biological parents but is the product of a distinct egg/sperm pair.

   ITWINBRO icon http://terminology.hl7.org/CodeSystem/v3-RoleCode identical twin brother

The male scoper is an offspring of the same egg-sperm pair as the male player.

   STPBRO icon http://terminology.hl7.org/CodeSystem/v3-RoleCode stepbrother

The player of the role is a son of the scoping person's stepparent.

   HSIB icon http://terminology.hl7.org/CodeSystem/v3-RoleCode half-sibling

The player of the role is related to the scoping entity by sharing only one biological parent.

   HSIS icon http://terminology.hl7.org/CodeSystem/v3-RoleCode half-sister

The player of the role is a female related to the scoping entity by sharing only one biological parent.

   NSIB icon http://terminology.hl7.org/CodeSystem/v3-RoleCode natural sibling

The player of the role has both biological parents in common with the scoping entity.

   NSIS icon http://terminology.hl7.org/CodeSystem/v3-RoleCode natural sister

The player of the role is a female having the same biological parents as the scoping entity.

   TWINSIS icon http://terminology.hl7.org/CodeSystem/v3-RoleCode twin sister

The scoper was carried in the same womb as the female player and shares common biological parents.

   FTWINSIS icon http://terminology.hl7.org/CodeSystem/v3-RoleCode fraternal twin sister

The scoper was carried in the same womb as the female player and shares common biological parents but is the product of a distinct egg/sperm pair.

   ITWINSIS icon http://terminology.hl7.org/CodeSystem/v3-RoleCode identical twin sister

The female scoper is an offspring of the same egg-sperm pair as the female player.

   TWIN icon http://terminology.hl7.org/CodeSystem/v3-RoleCode twin

The scoper and player were carried in the same womb and shared common biological parents.

   FTWIN icon http://terminology.hl7.org/CodeSystem/v3-RoleCode fraternal twin

The scoper and player were carried in the same womb and share common biological parents but are the product of distinct egg/sperm pairs.

   ITWIN icon http://terminology.hl7.org/CodeSystem/v3-RoleCode identical twin

The scoper and player are offspring of the same egg-sperm pair.

   SIS icon http://terminology.hl7.org/CodeSystem/v3-RoleCode sister

The player of the role is a female sharing one or both parents in common with the scoping entity.

   STPSIS icon http://terminology.hl7.org/CodeSystem/v3-RoleCode stepsister

The player of the role is a daughter of the scoping person's stepparent.

   STPSIB icon http://terminology.hl7.org/CodeSystem/v3-RoleCode step sibling

The player of the role is a child of the scoping person's stepparent.

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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