STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.3.1.marital-status Value Set http://hl7.org/fhir/ValueSet/marital-status

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/marital-status
Name:Marital Status Codes
Definition:This value set defines the set of codes that can be used to indicate the marital status of a person.
Committee:Patient Administration Work Group
OID:2.16.840.1.113883.4.642.2.marital-status (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:


This value set includes codes from the following code systems:

  • Include all codes defined in http://hl7.org/fhir/v3/MaritalStatus
  • Include these codes as defined in http://hl7.org/fhir/v3/NullFlavor
    CodeDisplay
    UNKunknownDescription: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:
    Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 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.)

 

This expansion generated 06 Dec 2016


This value set contains 11 concepts

Expansion based on http://hl7.org/fhir/v3/NullFlavor version 2016-11-11, http://hl7.org/fhir/v3/MaritalStatus version 2016-11-11

CodeSystemDisplayDefinition
Ahttp://hl7.org/fhir/v3/MaritalStatusAnnulledMarriage contract has been declared null and to not have existed
Dhttp://hl7.org/fhir/v3/MaritalStatusDivorcedMarriage contract has been declared dissolved and inactive
Ihttp://hl7.org/fhir/v3/MaritalStatusInterlocutorySubject to an Interlocutory Decree.
Lhttp://hl7.org/fhir/v3/MaritalStatusLegally SeparatedLegally Separated
Mhttp://hl7.org/fhir/v3/MaritalStatusMarriedA current marriage contract is active
Phttp://hl7.org/fhir/v3/MaritalStatusPolygamousMore than 1 current spouse
Shttp://hl7.org/fhir/v3/MaritalStatusNever MarriedNo marriage contract has ever been entered
Thttp://hl7.org/fhir/v3/MaritalStatusDomestic partnerPerson declares that a domestic partner relationship exists.
Uhttp://hl7.org/fhir/v3/MaritalStatusunmarriedCurrently not in a marriage contract.
Whttp://hl7.org/fhir/v3/MaritalStatusWidowedThe spouse has died
UNKhttp://hl7.org/fhir/v3/NullFlavorunknownDescription: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: Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 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.)

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LevelA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance)
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code