Belgium eHealth FHIR Core specifications
1.2.2 - CI Build

This page is part of the Belgium eHealth FHIR Core specifications (v1.2.2: Trial Use) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

ValueSet:

Summary

Defining URL:https://www.ehealth.fgov.be/standards/fhir/ValueSet/be-civilstate
Version:1.2.2
Name:BeCivilstate
Status:Active as of 2021-07-10T14:45:27+02:00
Definition:

Codes supported by eHealth Platform differentiating types of civil state. This valueset supports the Belgian federal FHIR profiling effort. Whenever possible add a code from http://terminology.hl7.org/CodeSystem/v3-MaritalStatus for international interoperability but also use https://www.ehealth.fgov.be/standards/fhir/CodeSystem/CD-CIVILSTATE for the Belgian specific code.

Publisher:eHealth
Source Resource:XML / JSON / Turtle

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-MaritalStatus
    CodeDisplayDefinitionEnglish (English, en)Nederlands (België) (Dutch (Belgium), nl)French (Belgium) (fr)
    AAnnulledMarriage contract has been declared null and to not have existedAnnuledNietigverklaring van huwelijkAnnulation de marriage
    DDivorcedMarriage contract has been declared dissolved and inactiveDivorcedEchtgescheidenDivorced
    MMarriedA current marriage contract is activeMarriedGehuwdMarié
    UunmarriedCurrently not in a marriage contract.UnmarriedOngehuwdCélibataire
    WWidowedThe spouse has diedWidowedWeduwnaar/weduweVeuf/veuve
  • Include these codes as defined in https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstate
    CodeDisplayEnglish (English, en)Nederlands (België) (Dutch (Belgium), nl)French (Belgium) (fr)
    10UnmarriedUnmarriedOngehuwdCélibataire
    26Putative marriagePutative marriagePutatief huwelijkMariage putatif
    40DivorcedDivorcedEchtgescheidenDivorced
    41Divorced since 1/10/1994Divorced since 1/10/1994Echtgescheiden vanaf 1/10/1994Divorcé à partir du 1/10/1994
    50Legal separationLegal separationGescheiden van tafel en bedSéparé de corps et de biens
    51Legal separation since 1/10/1994Legal separation since 1/10/1994Gescheiden van tafel en bed sinds 1/10/1994Séparé de corps et de biens à partir du 1/10/1994
    60RepudiationRepudiationVerstotingRépudiation
    80PartnershipPartnershipPartnerschapPartenariat
    81End of partnershipEnd of partnershipPartnerschap beeindigdFin de partenariat
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
    CodeDisplayDefinitionEnglish (English, en)Nederlands (België) (Dutch (Belgium), nl)French (Belgium) (fr)
    UNKunknown**Description:**A proper value is applicable, but not known.

    **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:

    1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown')
    2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)
    UnknownOnbepaaldIndéterminé

 

Expansion

This value set contains 15 concepts

CodeSystemDisplayDefinition
Ahttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusAnnulledMarriage contract has been declared null and to not have existed
Dhttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusDivorcedMarriage contract has been declared dissolved and inactive
Mhttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusMarriedA current marriage contract is active
Uhttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusunmarriedCurrently not in a marriage contract.
Whttp://terminology.hl7.org/CodeSystem/v3-MaritalStatusWidowedThe spouse has died
10https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstateUnmarried
26https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstatePutative marriage
40https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstateDivorced
41https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstateDivorced since 1/10/1994
50https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstateLegal separation
51https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstateLegal separation since 1/10/1994
60https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstateRepudiation
80https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstatePartnership
81https://www.ehealth.fgov.be/standards/fhir/CodeSystem/cd-civilstateEnd of partnership
UNKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorunknown**Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)

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