EHDS openEHR data exchange
0.1.0 - ci-build

EHDS openEHR data exchange, published by Ian. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/freshehr/EHDS-openEHR-FHIR-IG/ and changes regularly. See the Directory of published versions

ValueSet: OL - Carer contingency plan: Relationship

Official URL: https://ianbennett.github.io/ExampleIG_Ian/ValueSet/OLCarerContingencyPlanRelationship Version: 0.1.0
Draft as of 2026-03-25 Computable Name: OLCarerContingencyPlanRelationship

References

Logical Definition (CLD)

  • Include these codes as defined in http://openehr.org/archetypes/openEHR-EHR-CLUSTER.contact_cc.v0/CS version Not Stated (use latest from terminology server)
    CodeDisplay
    NOKNext of Kin
    AUNTAunt
    BROBrother
    BILBrother-in-Law
    COHABITCohabitee
    COUSINCousin
    DAUDaughter
    DILDaughter-in-Law
    FILFather-in-Law
    FOSTERFoster Carer
    FRIENDFriend
    GCHILDGrandchild
    GPARENTGrandparent
    HALFBROHalf Brother
    HALFSISHalf Sister
    HUSBANDHusband
    MILMother-in-Law
    NEPHEWNephew
    NIECENiece
    PARENTParent
    PARTNERPartner
    SISSister
    SILSister-in-Law
    SONSon
    SOILSon-in-Law
    STEPBROStep Brother
    STEPCHILDStep Child
    STEPPARENTStep Parent
    STEPSISStep Sister
    UNCLEUncle
    WIFEWife
    OTHEROther
    PARENTALRESPHas Parental Responsibility

 

Expansion

No Expansion for this valueset (Unknown Code System)


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