HdBe-MaritalStatus
CBB | Description | Status |
---|---|---|
HdBe-MaritalStatus | Marital status is a person’s formal position as defined by the Belgium civil code. There is a distinction between marriage and civil union. PurposeThe marital status is recorded for administrative purposes. InstructionsMarital status at the time of entering the information as reported by the patient. | active |
MaritalStatusRC | MaritalStatusRC | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
MaritalStatus | 0..1 | CodeableConceptBinding |
MaritalStatusRC | |
Definition | Root concept of the MaritalStatus information model. This concept contains all data elements of the MaritalStatus information model. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
MaritalStatusRC.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
MaritalStatusRC.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MaritalStatusRC.MaritalStatus | |
Definition | A person’s marital status. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | MaritalStatus codes |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Example instances
MaritalStatus | |
---|---|
MaritalStatus | 87915002 - Married (code by SNOMED CT) |
zib MaritalStatus-v3.1 difference
Concept | Category | Description |
---|---|---|
description | textual | Removed Dutch Context |
MaritalStatus |
terminology | Changed ValueSet to use a subset of concepts using SNOMED codes. |
MaritalStatus |
textual | Removed '>' in the definition (zib-1606) |
MaritalStatus |
textual | Removed Dutch context in definition. |
Terminology Bindings
Path | Name | Strength | URL |
---|---|---|---|
MaritalStatus | MaritalStatus | required | https://fhir.healthdata.be/ValueSet/MaritalStatus |