Te Whatu Ora, Central Region Integration Hub
1.0.12-rc1 - ci-build
Te Whatu Ora, Central Region Integration Hub, published by Te Whatu Ora, Te Pae Hauora o Ruahine o Tararua, MidCentral. This guide is not an authorized publication; it is the continuous build for version 1.0.12-rc1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/tewhatuora/centralRegion-integrationHub-ig/ and changes regularly. See the Directory of published versions
Official URL: https://standards.digital.health.nz/fhir/central-region/ValueSet-marital-status | Version: 1.0.12-rc1 | |||
Active as of 2024-09-17 | Computable Name: NZCentralRegionMaritalStatusValueSet |
Combined Marital Status value set with HL7 defined valueset plus #OTH from NullFlavor, as used in the Central Region
References
Generated Narrative: ValueSet nzcr-marital-status-vs
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-MaritalStatus
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition |
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.) |
OTH | other | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). **Usage Notes**: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to \*any\* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. |
Generated Narrative: ValueSet
Expansion based on:
This value set contains 13 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 |
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:
|
OTH | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | other | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. |
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 |