HL7 FHIR Implementation Guide: DK Core
1.1.0 - release
This page is part of the HL7 FHIR Implementation Guide: DK Core (v1.1.0: Release) based on FHIR R4. The current version which supercedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://hl7.dk/fhir/core/ValueSet/dk-marital-status |
Version: | 1.1.0 |
Name: | DK Marital Status Codes |
Title: | DK MaritalStatus |
Status: | Active as of 11/1/19, 9:29 AM |
Definition: | This value set defines the set of codes that can be used to indicate the marital status of a person in Denmark. |
Publisher: | HL7 Denmark |
Copyright: | CC-BY-SA-4.0 |
Source Resource: | XML / JSON / Turtle |
References
This value set includes codes based on the following rules:
http://hl7.dk/fhir/core/CodeSystem/dk-marital-status
Code | Display | Dansk (Danish, da) |
P | Registered partnership | Registreret partnerskab |
O | Dissolved partnership | Ophævet partnerskab |
This value set contains 14 concepts
Expansion based on:
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 |
I | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Interlocutory | Subject to an Interlocutory Decree. |
L | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Legally Separated | |
M | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Married | A current marriage contract is active |
C | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Common Law | a marriage recognized in some jurisdictions and based on the parties' agreement to consider themselves married and can also be based on documentation of cohabitation. This definition was based on https://www.merriam-webster.com/dictionary/common-law%20marriage. |
P | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Polygamous | More than 1 current spouse |
T | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Domestic partner | Person declares that a domestic partner relationship exists. |
U | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | unmarried | Currently not in a marriage contract. |
S | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Never Married | No marriage contract has ever been entered |
W | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Widowed | The spouse has died |
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: 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.) |
P | http://hl7.dk/fhir/core/CodeSystem/dk-marital-status | Registered partnership | |
O | http://hl7.dk/fhir/core/CodeSystem/dk-marital-status | Dissolved partnership |
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 |