eHealth Platform Federal Core Profiles
2.1.2 - STU1
This page is part of the HL7 Belgium FHIR Implementation Guide - Core profiles (v2.1.2: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Official URL: https://www.ehealth.fgov.be/standards/fhir/core/ValueSet/be-civilstate | Version: 2.1.2 | |||
Active as of 2024-08-30 | Computable Name: BeCivilstate |
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/core/CodeSystem/CD-CIVILSTATE for the Belgian specific code.
References
Generated Narrative: ValueSet be-civilstate
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-MaritalStatus
Code | Display | Definition | English (English, en) | Nederlands (België) (Dutch (Belgium), nl) | French (Belgium) (fr) |
A | Annulled | Marriage contract has been declared null and to not have existed | Annuled | Nietigverklaring van huwelijk | Annulation de marriage |
D | Divorced | Marriage contract has been declared dissolved and inactive | Divorced | Echtgescheiden | Divorced |
M | Married | A current marriage contract is active | Married | Gehuwd | Marié |
U | unmarried | Currently not in a marriage contract. | Unmarried | Ongehuwd | Célibataire |
W | Widowed | The spouse has died | Widowed | Weduwnaar/weduwe | Veuf/veuve |
https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate
Code | Display | English (English, en) | Nederlands (België) (Dutch (Belgium), nl) | French (Belgium) (fr) |
10 | Unmarried | Unmarried | Ongehuwd | Célibataire |
26 | Putative marriage | Putative marriage | Putatief huwelijk | Mariage putatif |
40 | Divorced | Divorced | Echtgescheiden | Divorced |
41 | Divorced since 1/10/1994 | Divorced since 1/10/1994 | Echtgescheiden vanaf 1/10/1994 | Divorcé à partir du 1/10/1994 |
50 | Legal separation | Legal separation | Gescheiden van tafel en bed | Séparé de corps et de biens |
51 | Legal separation since 1/10/1994 | Legal separation since 1/10/1994 | Gescheiden van tafel en bed sinds 1/10/1994 | Séparé de corps et de biens à partir du 1/10/1994 |
60 | Repudiation | Repudiation | Verstoting | Répudiation |
80 | Partnership | Partnership | Partnerschap | Partenariat |
81 | End of partnership | End of partnership | Partnerschap beeindigd | Fin de partenariat |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition | English (English, en) | Nederlands (België) (Dutch (Belgium), nl) | French (Belgium) (fr) |
UNK | unknown | **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.) |
Unknown | Onbepaald | Indéterminé |
Generated Narrative: ValueSet
Expansion based on:
This value set contains 15 concepts
Code | System | Display | Definition |
A | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Annulled | Marriage contract has been declared null and to not have existed |
D | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Divorced | Marriage contract has been declared dissolved and inactive |
M | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Married | A current marriage contract is active |
U | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | unmarried | Currently not in a marriage contract. |
W | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Widowed | The spouse has died |
10 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Unmarried | |
26 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Putative marriage | |
40 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Divorced | |
41 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Divorced since 1/10/1994 | |
50 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Legal separation | |
51 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Legal separation since 1/10/1994 | |
60 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Repudiation | |
80 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | Partnership | |
81 | https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/cd-civilstate | End of partnership | |
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | unknown | **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:
|
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 |