This page is part of the HL7 Italia FHIR Implementation Guide (base) (v0.1.0: Public Comment 1 Ballot 1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://hl7.it/fhir/ValueSet/statoCivile |
Version: | 0.1.0 |
Name: | VsStatoCivile |
Status: | Active |
Title: | Stato Civile |
Definition: | Questo value set definisce una serie di codici per rappresentare lo stato civile di una persona. Specializza ed estende il value set http://hl7.org/fhir/ValueSet/marital-status |
Publisher: | HL7 Italia |
Source Resource: | XML / JSON / Turtle |
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-MaritalStatus
Code | Display | |
D | Divorziato/a | Marriage contract has been declared dissolved and inactive |
M | Coniugato/a | A current marriage contract is active |
S | Celibe/nubile | No marriage contract has ever been entered |
W | Vedovo/a | The spouse has died |
L | Separato/a Legalmente | Legally Separated |
A | Annullato | Marriage contract has been declared null and to not have existed |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | |
UNK | Sconosciuto | 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: 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.) |
http://terminology.hl7.it/CodeSystem/istat-statoCivile
Code | Display | |
6 | Unito civilmente | |
7 | Stato libero a seguito di decesso della parte unita civilmente | |
8 | Stato libero a seguito di scioglimento dell'unione |
This value set contains 10 concepts
Expansion based on:
Code | System | Display | Definition |
D | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Divorziato/a | Marriage contract has been declared dissolved and inactive |
M | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Coniugato/a | A current marriage contract is active |
S | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Celibe/nubile | No marriage contract has ever been entered |
W | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Vedovo/a | The spouse has died |
L | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Separato/a Legalmente | Legally Separated |
A | http://terminology.hl7.org/CodeSystem/v3-MaritalStatus | Annullato | Marriage contract has been declared null and to not have existed |
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Sconosciuto | 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: 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.) |
6 | http://terminology.hl7.it/CodeSystem/istat-statoCivile | Unito civilmente | |
7 | http://terminology.hl7.it/CodeSystem/istat-statoCivile | Stato libero a seguito di decesso della parte unita civilmente | |
8 | http://terminology.hl7.it/CodeSystem/istat-statoCivile | Stato libero a seguito di scioglimento dell'unione |
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 |