RIVO Noord Zorgviewer MVP2 Implementation Guide
0.2.1 - CI build
RIVO Noord Zorgviewer MVP2 Implementation Guide - Local Development build (v0.2.1). See the Directory of published versions
Draft as of 2023-03-22 |
Definitions for the Patient resource profile.
Guidance on how to interpret the contents of this table can be found here.
1. Patient | |
2. Patient.identifier:BSN | |
SliceName | BSN |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 10..1 |
Must Support | true |
3. Patient.name | |
Control | 10..* |
Must Support | true |
Invariants | Defined on this element zv-pat-1: Either Patient.name.given and/or Patient.name.family and/or Patient.name.text SHALL be present. (: (family.exists() or given.exists() or text.exists())) zv-pat-2: To be usable for a wide range of internationally available applications, the Patient.name.text SHOULD be present. (: text.exists()) |
4. Patient.gender | |
Must Support | true |
5. Patient.birthDate | |
Must Support | true |
Guidance on how to interpret the contents of this table can be found here.
1. Patient | |
Definition | Demographics and other administrative information about an individual or animal receiving care or other health-related services. |
Control | 0..* |
Alternate Names | SubjectOfCare Client Resident, Patiënt |
Invariants | Defined on this element dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty()) dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty()) dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource (: contained.where(('#'+id in %resource.descendants().reference).not()).empty()) dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated (: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) |
2. Patient.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Control | 0..1 |
Type | uri |
Is Modifier | true |
Summary | true |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
3. Patient.extension:preferredPharmacy | |
SliceName | preferredPharmacy |
Definition | Optional Extension Element - found in all resources. |
Control | 0..1 This element is affected by the following invariants: ele-1 |
Type | Extension(nl core preferred pharmacy) (Extension Type: Reference) |
Alternate Names | Verwijst naar de voorkeursapotheek van de patiënt |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
4. Patient.extension:nationality | |
SliceName | nationality |
Definition | The nationality of the patient. May be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | This element is affected by the following invariants: ele-1 |
Type | Extension(nationality) (Complex Extension) |
Alternate Names | Nationaliteit, extensions, user content |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
5. Patient.extension:nationality.extension:code | |
SliceName | code |
Definition | An Extension May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..1* |
Type | Extension |
Alternate Names | 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. |
6. Patient.extension:nationality.extension:code.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | code |
7. Patient.extension:nationality.extension:code.valueCodeableConcept:valueCodeableConcept | |
SliceName | valueCodeableConcept |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..1 |
Binding | The codes SHALL be taken from NationaliteitCodelijst; other codes may be used where these codes are not suitableFor codes, see (unbound) Indicates the country of citizenship |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
8. Patient.extension:nationality.extension:period | |
SliceName | period |
Definition | An Extension May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..1* |
Type | Extension |
Alternate Names | 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. |
9. Patient.extension:nationality.extension:period.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | period |
10. Patient.extension:nationality.extension:period.valuePeriod:valuePeriod | |
SliceName | valuePeriod |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..1 |
Type | Choice of: Period, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal, CodeableConcept |
11. Patient.extension:nationality.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://hl7.org/fhir/StructureDefinition/patient-nationality |
12. Patient.extension:nationality.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..01 |
Type | Choice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta |
[x] Note | See Choice of Data Types for further information about how to use [x] |
13. Patient.extension:legalStatus | |
SliceName | legalStatus |
Definition | The legal situation that applies to the patient during the intervention. The code of the legal status is based on the Vektis/AZR code list COD232-VEKT Legal Status. |
Control | 0..2 This element is affected by the following invariants: ele-1 |
Type | Extension(zib patient legalstatus) (Extension Type: CodeableConcept) |
Comments | The concept LegalStatus of the HCIM FreedomRestrictingMeasures plays an important role in the context of mental healthcare (GGZ). This concept will become an independent HCIM with the next release of HCIM (2018 release). The LegalStatus concept and associated ValueSet will be split in two concepts: legal status and representative. These concepts are currently captured in one ValueSet. It is possible to have a legal status AND a representative. Therefore, we allow this extension to have a cardinality of 0..2. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
14. Patient.extension:legalStatus.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/zib-patient-legalstatus |
15. Patient.extension:legalStatus.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..1 |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Slicing | This element introduces a set of slices on Patient.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
16. Patient.extension:legalStatus.value[x]:valueCodeableConcept | |
SliceName | valueCodeableConcept |
Definition | The legal situation that applies to the patient during the intervention. The code of the legal status is based on the Vektis/AZR code list COD232-VEKT Legal Status. Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Binding | The codes SHALL be taken from JuridischeStatusCodelijst; other codes may be used where these codes are not suitableFor codes, see (unbound) |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Alternate Names | JuridischeStatus |
17. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding | |
Definition | A reference to a code defined by a terminology system. |
Control | 10..* |
Type | Coding |
Summary | true |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
18. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Control | 10..1 |
Type | uri |
Summary | true |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. |
19. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Control | 10..1 |
Type | code |
Summary | true |
Requirements | Need to refer to a particular code in the system. |
20. Patient.extension:lifeStance | |
SliceName | lifeStance |
Definition | Optional Extension Element - found in all resources. |
Control | 0..* This element is affected by the following invariants: ele-1 |
Type | Extension(Zib LifeStance) (Extension Type: CodeableConcept) |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
21. Patient.extension:lifeStance.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance |
22. Patient.extension:lifeStance.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Slicing | This element introduces a set of slices on Patient.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
23. Patient.extension:lifeStance.value[x]:valueCodeableConcept | |
SliceName | valueCodeableConcept |
Definition | Patient’s life stance and/or religion. Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Binding | The codes SHOULD be taken from LevensovertuigingCodelijstFor codes, see (unbound) LevensovertuigingCodelijs |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Alternate Names | Levensovertuiging |
24. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding | |
Definition | A reference to a code defined by a terminology system. |
Control | 10..1* |
Type | Coding |
Summary | true |
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
25. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Control | 10..1 |
Type | uri |
Summary | true |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. |
26. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Control | 10..1 |
Type | code |
Summary | true |
Requirements | Need to refer to a particular code in the system. |
27. Patient.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | 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. |
28. Patient.identifier | |
Definition | The Burgerservicenummer or BSN, as one of the possible patient identification numbers, should at least be sent unless there is a reason not to. Reasons for not sending the burgerservicenummer include but are not limited to, research and apps without a contract for processing data (Dutch: bewerkingsovereenkomst). An identifier for this patient. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Summary | true |
Requirements | Patients are almost always assigned specific numerical identifiers. |
Alternate Names | Identificatienummer |
Slicing | This element introduces a set of slices on Patient.identifier. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
29. Patient.identifier:BSN | |
SliceName | BSN |
Definition | An identifier for this patient. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 10..1* |
Type | Identifier |
Must Support | true |
Summary | true |
Requirements | Patients are almost always assigned specific numerical identifiers. |
Alternate Names | BSN |
30. Patient.identifier:BSN.use | |
Definition | The purpose of this identifier. |
Control | 0..1 |
Binding | The codes SHALL be taken from IdentifierUse Identifies the purpose for this identifier, if known . |
Type | code |
Is Modifier | true |
Summary | true |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
31. Patient.identifier:BSN.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Control | 10..1 |
Type | uri |
Summary | true |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Fixed Value | http://fhir.nl/fhir/NamingSystem/bsn |
Example | General:http://www.acme.com/identifiers/patient |
32. Patient.identifier:BSN.value | |
Definition | Burgerservicenummer is the Dutch person identification number which is also allowed for use in healthcare. The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Control | 10..1 |
Type | string |
Summary | true |
Alternate Names | BSN |
Comments | The official format according to the 'Logisch Ontwerp BSN 1.4.pdf' is N8..9 and SHALL conform to an 11-proof algorithm. In order to check if the number is 11-proof the number, if N8, SHALL be prefixed with a leading zero. The expected format in FHIR is N9 with leading zero applied to any N8 bsn. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. |
Example | General:123456 Example of a burgerservicenummer:123456782 |
33. Patient.active | |
Definition | This field determines the status of the 'patient' record in the context of the organization that owns the record. Note that the record is not the medical record, but rather the actual patient 'resource'. Obviously when the patient 'resource' is not active, then by extension his medical record might also be inactive. Patient.active='false' may be used discourage use of the record, but that it is kept beause there is (medical) data attached to it. Another use case is a patient moving to a different GP practice. Patient.active would be 'false' in the system of the previous GP. Whether this patient record is in active use. |
Control | 0..1 |
Type | boolean |
Is Modifier | true |
Summary | true |
Requirements | Need to be able to mark a patient record as not to be used because it was created in error. |
Comments | Default is true. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient This element is labeled as a modifier because when the patient record is marked as not active it is not expected to be used/referenced without being changed back to active. |
Default Value | true |
34. Patient.name | |
Definition | A human's name with the ability to identify parts and usage. A name associated with the individual. |
Control | 10..* This element is affected by the following invariants: ele-1 |
Type | HumanName(nl-core-humanname) |
Must Support | true |
Requirements | Need to be able to track the patient by multiple names. Examples are your official name and a partner name. |
Alternate Names | Naamgegevens |
Comments | Dutch names require that certain name parts are separately communicable. For this reason, extensions are added onto the base HumanName element to mark the meaning of each part. A Dutch HumanName is still a proper FHIR HumanName; however, there might be an incompatibilty with the default FHIR mechanism for communicating given names. See the compatibility note below for more information. The extension elements cover birth name (NL: eigennaam / geslachtsnaam) and partner/spouse name. Both may have a prefix (NL: voorvoegsel). When a person marries, he or she may keep their own name, assume the partner name, append the partner name to their own name, or the other way around. Incompatibility note: It has come to light that this specification deviates from the way that the HumanName datatype is normally used. This will be fixed in a future release. However, current implementations should be aware of the special considerations regarding the use of this specification. The issue at hand is the way alternative representations of a name, like initials or a nickname, are communicated. Normally this is done using multiple HumanName instances, which are differentiated using the Since multiple implementations are based on this specification, sending systems are advised (but not required) to keep the approach with one HumanName instance, while receiving systems should be able to handle this one-instance approach. More specifically:
Example: miss Irma Jongeneel marries mister de Haas and assumes the name Irma Jongeneel-de Haas:
A patient may have multiple names with different uses or applicable periods. For animals, the name is a "HumanName" in the sense that is assigned and used by humans and has the same patterns. |
Example | Structured HumanName (preferred above unstructured):<valueHumanName xmlns="http://hl7.org/fhir"> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-assembly-order"> <valueCode value="NL4"/> </extension> <text value="Irma Jongeneel-de Haas"/> <family value="Jongeneel-de Haas"> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-own-name"> <valueString value="Jongeneel"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix"> <valueString value="de"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-partner-name"> <valueString value="Haas"/> </extension> </family> <given value="Irma"/> </valueHumanName> Unstructured HumanName:<valueHumanName xmlns="http://hl7.org/fhir"> <text value="Irma Jongeneel-de Haas"/> </valueHumanName> |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) nl-core-humanname-1: if you specify a prefix for an own name then an own name is also expected (: name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty().not()) nl-core-humanname-2: if you specify a voorvoegsel for a partner name then a partner name is also expected (: name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-name').empty().not()) zv-pat-1: Either Patient.name.given and/or Patient.name.family and/or Patient.name.text SHALL be present. (: (family.exists() or given.exists() or text.exists())) zv-pat-2: To be usable for a wide range of internationally available applications, the Patient.name.text SHOULD be present. (: text.exists()) |
35. Patient.name.extension:humannameAssemblyOrder | |
SliceName | humannameAssemblyOrder |
Definition | A code that represents the preferred display order of the components of this human name. |
Control | 0..* |
Type | Extension(assembly-order) (Extension Type: code) |
36. Patient.name.extension:humannameAssemblyOrder.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-assembly-order |
37. Patient.name.extension:humannameAssemblyOrder.valueCode:valueCode | |
SliceName | valueCode |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..1 |
Binding | The codes SHALL be taken from HumanNameAssemblyOrderFor codes, see (unbound) A code that represents the preferred display order of the components of a human nam |
Type | Choice of: code, date, dateTime, Meta, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal, CodeableConcept |
38. Patient.name.use | |
Definition | Identifies the purpose for this name. |
Control | 0..1 |
Binding | The codes SHALL be taken from NameUse The use of a human name |
Type | code |
Is Modifier | true |
Summary | true |
Requirements | Allows the appropriate name for a particular context of use to be selected from among a set of names. |
Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary or old name etc.for a current/permanent one. Applications can assume that a name is current unless it explicitly says that it is temporary or old. |
39. Patient.gender | |
Definition | Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes. |
Control | 0..1 |
Binding | The codes SHALL be taken from AdministrativeGender |
Type | code |
Must Support | true |
Summary | true |
Requirements | Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes. |
Alternate Names | Geslacht |
Comments | The gender may not match the biological sex as determined by genetics, or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than M and F, though the vast majority of systems and contexts only support M and F. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific gender aspect of interest (anatomical, chromosonal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosonal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overrideable error, not a "hard" error. |
40. Patient.gender.extension:GeslachtCodelijst | |
SliceName | GeslachtCodelijst |
Definition | Patient’s administrative gender. |
Control | 0..1 This element is affected by the following invariants: ele-1 |
Type | Extension(Zib extension code specification) (Extension Type: CodeableConcept) |
Alternate Names | Bevat de specifieke code conform de zib, bij een FHIR-element die een verplichte koppeling heeft met een bepaalde FHIR waardelijst of een FHIR element die niet gecodeerd is gedefinieerd, terwijl de zib dit wel doet., Geslacht |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
41. Patient.gender.extension:GeslachtCodelijst.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/code-specification |
42. Patient.gender.extension:GeslachtCodelijst.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Slicing | This element introduces a set of slices on Patient.gender.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
43. Patient.gender.extension:GeslachtCodelijst.value[x]:valueCodeableConcept | |
SliceName | valueCodeableConcept |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Binding | The codes SHALL be taken from GeslachtCodelijst; other codes may be used where these codes are not suitableFor codes, see (unbound) GeslachtCodelijs |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
44. Patient.birthDate | |
Definition | The date of birth for the individual. |
Control | 0..1 |
Type | date |
Must Support | true |
Summary | true |
Requirements | Age of the individual drives many clinical processes. |
Alternate Names | Geboortedatum |
Comments | At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternaty/infant care systems). |
LOINC Code | 21112-8 |
45. Patient.deceased[x] | |
Definition | Indicates if the individual is deceased or not. |
Control | 0..1 |
Type | Choice of: boolean, dateTime |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Is Modifier | true |
Summary | true |
Requirements | The fact that a patient is deceased influences the clinical process. Also, in human communication and relation management it is necessary to know whether the person is alive. |
Alternate Names | Overlijdensindicator/DatumOverlijden |
Comments | If there's no value in the instance it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive. This element is labeled as a modifier because once a patient is marked as deceased, the actions that are appropriate to perform on the patient may be significantly different. |
46. Patient.address | |
Definition | This datatype defines a common basis for expressing all addresses around the world, but adds extensions to express Dutch addresses specifically, according to the HCIM AddressInformation (v1.0, 2017). A Dutch Address still is a proper FHIR Address, which means that systems that cannot interpret the extensions will still be able to render and work with this datatype. To have true compatibility an implementer SHOULD use the core Address parts as intended. To have addresses work for Dutch context, the implementer SHOULD in addition use the extension elements. Separate address parts The first addition is that Dutch addresses make certain address parts separately communicable. These parts are required for use in true Dutch systems when dealing with Dutch addresses, but may not have value for international systems when information gets sent abroad. Custom address types The second addition is that the HCIM defines its own ValueSet for address types, which can only be partially expressed using the FHIR Address datatype and requires a mapping to multiple elements. The table below explains how the HCIM concepts are mapped to the various FHIR elements (see the ConceptMaps http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressUse and http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressType as well). The HCIM code itself should also be included using the AddressType extension. | HCIM | If Address.type is both then this is to be understood as a dual purpose address (postal and physical). Systems that support importing it like this are encouraged to do so, otherwise they may need to import this as two separate addresses. NOTE: FHIR core defines the AD-use extension to further specify the postal address type. However, the ValueSet used in that extension doesn't completely match the HCIM ValueSet. Therefore, a custom extension has been made. This doesn't preclude the use of the AD-use extension. Addresses for the individual. |
Control | 0..* This element is affected by the following invariants: ele-1, nl-streetname-if-official-and-other-line-parts |
Type | Address(nl-core-address) |
Requirements | May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification. |
Alternate Names | AdresInformatie, Adresgegevens |
Comments | Note: address is for postal addresses, not physical locations. Patient may have multiple addresses with different uses or applicable periods. |
Example | Example of a Vacation Home address:<valueAddress xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="HV"/> <display value="Vakantie adres"/> </coding> </valueCodeableConcept> </extension> <use value="temp"/> <line value="Binnenkant 12A Hoog"/> <city value="Amsterdam"/> <state value="NH"/> <postalCode value="1000AA"/> <country value="NLD"/> </valueAddress> Example of a Primary Home address:<valueAddress xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="HP"/> <display value="Officieel adres"/> </coding> </valueCodeableConcept> </extension> <extension url="http://fhir.nl/fhir/StructureDefinition/nl-core-address-official"> <valueBoolean value="true"/> </extension> <use value="home"/> <line value="Binnenkant to 10"/> <city value="Amsterdam"/> <state value="NH"/> <postalCode value="1001AA"/> <country value="NLD"/> </valueAddress> |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) nl-streetname-if-official-and-other-line-parts: Address.streetName in an official address SHALL have a value if one of houseNumber|buildingNumberSuffix|additionalLocator has a value (: (extension.where(url = 'http://fhir.nl/fhir/StructureDefinition/nl-core-address-official').where(value = true)).empty() or (line.extension.where(url = 'http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty().not() and (line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty().not()))) |
47. Patient.animal | |
Definition | This patient is known to be an animal. |
Control | 0..1 |
Type | BackboneElement |
Is Modifier | true |
Summary | true |
Requirements | Many clinical systems are extended to care for animal patients as well as human. |
Comments | The animal element is labeled "Is Modifier" since patients may be non-human. Systems SHALL either handle patient details appropriately (e.g. inform users patient is not human) or reject declared animal records. The absense of the animal element does not imply that the patient is a human. If a system requires such a positive assertion that the patient is human, an extension will be required. (Do not use a species of homo-sapiens in animal species, as this would incorrectly infer that the patient is an animal). |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
48. Patient.animal.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Alternate Names | extensions, user content, modifiers |
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. |
49. Patient.animal.species | |
Definition | Identifies the high level taxonomic categorization of the kind of animal. |
Control | 1..1 |
Binding | For example codes, see AnimalSpecies The species of an animal. |
Type | CodeableConcept |
Summary | true |
Requirements | Need to know what kind of animal. |
Comments | If the patient is non-human, at least a species SHALL be specified. Species SHALL be a widely recognised taxonomic classification. It may or may not be Linnaean taxonomy and may or may not be at the level of species. If the level is finer than species--such as a breed code--the code system used SHALL allow inference of the species. (The common example is that the word "Hereford" does not allow inference of the species Bos taurus, because there is a Hereford pig breed, but the SNOMED CT code for "Hereford Cattle Breed" does.). |
50. Patient.generalPractitioner | |
Definition | Patient's nominated care provider. |
Control | 0..1* |
Type | Reference(nl-core-organization|nl-core-practitioner|Organization|Practitioner) |
Alternate Names | careProvider, Huisarts |
Comments | This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disablity setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources. |
51. Patient.generalPractitioner.extension:practitionerRole | |
SliceName | practitionerRole |
Definition | Optional Extension Element - found in all resources. |
Control | 0..1 |
Type | Extension(PractitionerRole Reference) (Extension Type: Reference) |
52. Patient.link | |
Definition | Link to another patient resource that concerns the same actual patient. |
Control | 0..* |
Type | BackboneElement |
Is Modifier | true |
Summary | true |
Requirements | There are multiple usecases:
|
Comments | There is no assumption that linked patient records have mutual links. This element is labelled as a modifier because it may not be the main Patient resource, and the referenced patient should be used instead of this Patient record. This is when the link.type value is 'replaced-by'. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
53. Patient.link.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Alternate Names | extensions, user content, modifiers |
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. |
54. Patient.link.other | |
Definition | The other patient resource that the link refers to. |
Control | 1..1 |
Type | Reference(Patient|RelatedPerson) |
Summary | true |
Comments | Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual. |
55. Patient.link.type | |
Definition | The type of link between this patient resource and another patient resource. |
Control | 1..1 |
Binding | The codes SHALL be taken from LinkType The type of link between this patient resource and another patient resource. |
Type | code |
Summary | true |
Guidance on how to interpret the contents of this table can be found here.
1. Patient | |||||
Definition | Demographics and other administrative information about an individual or animal receiving care or other health-related services. | ||||
Control | 0..* | ||||
Alternate Names | SubjectOfCare Client Resident, Patiënt | ||||
2. Patient.id | |||||
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||||
Control | 0..1 | ||||
Type | id | ||||
Summary | true | ||||
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||||
3. Patient.meta | |||||
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. | ||||
Control | 0..1 | ||||
Type | Meta | ||||
Summary | true | ||||
4. Patient.implicitRules | |||||
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. | ||||
Control | 0..1 | ||||
Type | uri | ||||
Is Modifier | true | ||||
Summary | true | ||||
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. | ||||
5. Patient.language | |||||
Definition | The base language in which the resource is written. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable
A human language
| ||||
Type | code | ||||
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | ||||
6. Patient.text | |||||
Definition | A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. | ||||
Control | 0..1 This element is affected by the following invariants: dom-1 | ||||
Type | Narrative | ||||
Alternate Names | narrative, html, xhtml, display | ||||
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. | ||||
7. Patient.contained | |||||
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. | ||||
Control | 0..* | ||||
Type | Resource | ||||
Alternate Names | inline resources, anonymous resources, contained resources | ||||
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. | ||||
8. Patient.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
9. Patient.extension:preferredPharmacy | |||||
SliceName | preferredPharmacy | ||||
Definition | Optional Extension Element - found in all resources. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(nl core preferred pharmacy) (Extension Type: Reference) | ||||
Alternate Names | Verwijst naar de voorkeursapotheek van de patiënt | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
10. Patient.extension:nationality | |||||
SliceName | nationality | ||||
Definition | The nationality of the patient. | ||||
Control | 0..* This element is affected by the following invariants: ele-1 | ||||
Type | Extension(nationality) (Complex Extension) | ||||
Alternate Names | Nationaliteit | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
11. Patient.extension:nationality.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
12. Patient.extension:nationality.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
13. Patient.extension:nationality.extension:code | |||||
SliceName | code | ||||
Definition | An Extension | ||||
Control | 0..1 | ||||
Type | Extension | ||||
14. Patient.extension:nationality.extension:code.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
15. Patient.extension:nationality.extension:code.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
16. Patient.extension:nationality.extension:code.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | code | ||||
17. Patient.extension:nationality.extension:code.valueCodeableConcept:valueCodeableConcept | |||||
SliceName | valueCodeableConcept | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from NationaliteitCodelijst; other codes may be used where these codes are not suitable Indicates the country of citizenship | ||||
Type | CodeableConcept | ||||
18. Patient.extension:nationality.extension:period | |||||
SliceName | period | ||||
Definition | An Extension | ||||
Control | 0..1 | ||||
Type | Extension | ||||
19. Patient.extension:nationality.extension:period.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
20. Patient.extension:nationality.extension:period.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
21. Patient.extension:nationality.extension:period.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | period | ||||
22. Patient.extension:nationality.extension:period.valuePeriod:valuePeriod | |||||
SliceName | valuePeriod | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | Period | ||||
23. Patient.extension:nationality.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/patient-nationality | ||||
24. Patient.extension:nationality.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..0 | ||||
Type | Choice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
25. Patient.extension:legalStatus | |||||
SliceName | legalStatus | ||||
Definition | The legal situation that applies to the patient during the intervention. The code of the legal status is based on the Vektis/AZR code list COD232-VEKT Legal Status. | ||||
Control | 0..2 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(zib patient legalstatus) (Extension Type: CodeableConcept) | ||||
Comments | The concept LegalStatus of the HCIM FreedomRestrictingMeasures plays an important role in the context of mental healthcare (GGZ). This concept will become an independent HCIM with the next release of HCIM (2018 release). The LegalStatus concept and associated ValueSet will be split in two concepts: legal status and representative. These concepts are currently captured in one ValueSet. It is possible to have a legal status AND a representative. Therefore, we allow this extension to have a cardinality of 0..2. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
26. Patient.extension:legalStatus.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
27. Patient.extension:legalStatus.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
28. Patient.extension:legalStatus.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/zib-patient-legalstatus | ||||
29. Patient.extension:legalStatus.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Patient.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
30. Patient.extension:legalStatus.value[x]:valueCodeableConcept | |||||
SliceName | valueCodeableConcept | ||||
Definition | The legal situation that applies to the patient during the intervention. The code of the legal status is based on the Vektis/AZR code list COD232-VEKT Legal Status. | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from JuridischeStatusCodelijst; other codes may be used where these codes are not suitable | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Alternate Names | JuridischeStatus | ||||
31. Patient.extension:legalStatus.value[x]:valueCodeableConcept.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
32. Patient.extension:legalStatus.value[x]:valueCodeableConcept.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.value[x].extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
33. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding | |||||
Definition | A reference to a code defined by a terminology system. | ||||
Control | 1..* | ||||
Type | Coding | ||||
Summary | true | ||||
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||||
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | ||||
34. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
35. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.value[x].coding.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
36. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.system | |||||
Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||||
Control | 1..1 | ||||
Type | uri | ||||
Summary | true | ||||
Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||||
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||||
37. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.version | |||||
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||||
Note | This is a business versionId, not a resource version id (see discussion) | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||||
38. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.code | |||||
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||||
Control | 1..1 | ||||
Type | code | ||||
Summary | true | ||||
Requirements | Need to refer to a particular code in the system. | ||||
39. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.display | |||||
Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||||
40. Patient.extension:legalStatus.value[x]:valueCodeableConcept.coding.userSelected | |||||
Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||||
Control | 0..1 | ||||
Type | boolean | ||||
Summary | true | ||||
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||||
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||||
41. Patient.extension:legalStatus.value[x]:valueCodeableConcept.text | |||||
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | ||||
Comments | Very often the text is the same as a displayName of one of the codings. | ||||
42. Patient.extension:lifeStance | |||||
SliceName | lifeStance | ||||
Definition | Optional Extension Element - found in all resources. | ||||
Control | 0..* This element is affected by the following invariants: ele-1 | ||||
Type | Extension(Zib LifeStance) (Extension Type: CodeableConcept) | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
43. Patient.extension:lifeStance.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
44. Patient.extension:lifeStance.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
45. Patient.extension:lifeStance.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance | ||||
46. Patient.extension:lifeStance.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Patient.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
47. Patient.extension:lifeStance.value[x]:valueCodeableConcept | |||||
SliceName | valueCodeableConcept | ||||
Definition | Patient’s life stance and/or religion. | ||||
Control | 1..1 | ||||
Binding | The codes SHOULD be taken from LevensovertuigingCodelijst LevensovertuigingCodelijs | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Alternate Names | Levensovertuiging | ||||
48. Patient.extension:lifeStance.value[x]:valueCodeableConcept.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
49. Patient.extension:lifeStance.value[x]:valueCodeableConcept.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.value[x].extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
50. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding | |||||
Definition | A reference to a code defined by a terminology system. | ||||
Control | 1..1 | ||||
Type | Coding | ||||
Summary | true | ||||
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||||
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | ||||
51. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
52. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.extension.value[x].coding.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
53. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.system | |||||
Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||||
Control | 1..1 | ||||
Type | uri | ||||
Summary | true | ||||
Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||||
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||||
54. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.version | |||||
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||||
Note | This is a business versionId, not a resource version id (see discussion) | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||||
55. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.code | |||||
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||||
Control | 1..1 | ||||
Type | code | ||||
Summary | true | ||||
Requirements | Need to refer to a particular code in the system. | ||||
56. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.display | |||||
Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||||
57. Patient.extension:lifeStance.value[x]:valueCodeableConcept.coding.userSelected | |||||
Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||||
Control | 0..1 | ||||
Type | boolean | ||||
Summary | true | ||||
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||||
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||||
58. Patient.extension:lifeStance.value[x]:valueCodeableConcept.text | |||||
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | ||||
Comments | Very often the text is the same as a displayName of one of the codings. | ||||
59. Patient.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Alternate Names | 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. | ||||
60. Patient.identifier | |||||
Definition | The Burgerservicenummer or BSN, as one of the possible patient identification numbers, should at least be sent unless there is a reason not to. Reasons for not sending the burgerservicenummer include but are not limited to, research and apps without a contract for processing data (Dutch: bewerkingsovereenkomst). | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 0..* | ||||
Type | Identifier | ||||
Summary | true | ||||
Requirements | Patients are almost always assigned specific numerical identifiers. | ||||
Alternate Names | Identificatienummer | ||||
Slicing | This element introduces a set of slices on Patient.identifier. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
61. Patient.identifier:BSN | |||||
SliceName | BSN | ||||
Definition | An identifier for this patient. | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 1..1 | ||||
Type | Identifier | ||||
Must Support | true | ||||
Summary | true | ||||
Requirements | Patients are almost always assigned specific numerical identifiers. | ||||
Alternate Names | BSN | ||||
62. Patient.identifier:BSN.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
63. Patient.identifier:BSN.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.identifier.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
64. Patient.identifier:BSN.use | |||||
Definition | The purpose of this identifier. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from IdentifierUse Identifies the purpose for this identifier, if known | ||||
Type | code | ||||
Is Modifier | true | ||||
Summary | true | ||||
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | ||||
Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | ||||
65. Patient.identifier:BSN.type | |||||
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from Identifier Type Codes; other codes may be used where these codes are not suitable A coded type for an identifier that can be used to determine which identifier to use for a specific purpose | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
Requirements | Allows users to make use of identifiers when the identifier system is not known. | ||||
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. | ||||
66. Patient.identifier:BSN.system | |||||
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. | ||||
Control | 1..1 | ||||
Type | uri | ||||
Summary | true | ||||
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. | ||||
Fixed Value | http://fhir.nl/fhir/NamingSystem/bsn | ||||
Example | General:http://www.acme.com/identifiers/patient | ||||
67. Patient.identifier:BSN.value | |||||
Definition | Burgerservicenummer is the Dutch person identification number which is also allowed for use in healthcare. | ||||
Control | 1..1 | ||||
Type | string | ||||
Summary | true | ||||
Alternate Names | BSN | ||||
Comments | The official format according to the 'Logisch Ontwerp BSN 1.4.pdf' is N8..9 and SHALL conform to an 11-proof algorithm. In order to check if the number is 11-proof the number, if N8, SHALL be prefixed with a leading zero. The expected format in FHIR is N9 with leading zero applied to any N8 bsn. | ||||
Example | General:123456 Example of a burgerservicenummer:123456782 | ||||
68. Patient.identifier:BSN.period | |||||
Definition | Time period during which identifier is/was valid for use. | ||||
Control | 0..1 | ||||
Type | Period | ||||
Summary | true | ||||
69. Patient.identifier:BSN.assigner | |||||
Definition | Organization that issued/manages the identifier. | ||||
Control | 0..1 | ||||
Type | Reference(Organization) | ||||
Summary | true | ||||
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. | ||||
70. Patient.active | |||||
Definition | This field determines the status of the 'patient' record in the context of the organization that owns the record. Note that the record is not the medical record, but rather the actual patient 'resource'. Obviously when the patient 'resource' is not active, then by extension his medical record might also be inactive. Patient.active='false' may be used discourage use of the record, but that it is kept beause there is (medical) data attached to it. Another use case is a patient moving to a different GP practice. Patient.active would be 'false' in the system of the previous GP. | ||||
Control | 0..1 | ||||
Type | boolean | ||||
Is Modifier | true | ||||
Summary | true | ||||
Requirements | Need to be able to mark a patient record as not to be used because it was created in error. | ||||
Comments | Default is true. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient This element is labeled as a modifier because when the patient record is marked as not active it is not expected to be used/referenced without being changed back to active. | ||||
Default Value | true | ||||
71. Patient.name | |||||
Definition | A human's name with the ability to identify parts and usage. | ||||
Control | 1..* This element is affected by the following invariants: ele-1 | ||||
Type | HumanName(nl-core-humanname) | ||||
Must Support | true | ||||
Requirements | Need to be able to track the patient by multiple names. Examples are your official name and a partner name. | ||||
Alternate Names | Naamgegevens | ||||
Comments | Dutch names require that certain name parts are separately communicable. For this reason, extensions are added onto the base HumanName element to mark the meaning of each part. A Dutch HumanName is still a proper FHIR HumanName; however, there might be an incompatibilty with the default FHIR mechanism for communicating given names. See the compatibility note below for more information. The extension elements cover birth name (NL: eigennaam / geslachtsnaam) and partner/spouse name. Both may have a prefix (NL: voorvoegsel). When a person marries, he or she may keep their own name, assume the partner name, append the partner name to their own name, or the other way around. Incompatibility note: It has come to light that this specification deviates from the way that the HumanName datatype is normally used. This will be fixed in a future release. However, current implementations should be aware of the special considerations regarding the use of this specification. The issue at hand is the way alternative representations of a name, like initials or a nickname, are communicated. Normally this is done using multiple HumanName instances, which are differentiated using the Since multiple implementations are based on this specification, sending systems are advised (but not required) to keep the approach with one HumanName instance, while receiving systems should be able to handle this one-instance approach. More specifically:
Example: miss Irma Jongeneel marries mister de Haas and assumes the name Irma Jongeneel-de Haas:
| ||||
Example | Structured HumanName (preferred above unstructured):<valueHumanName xmlns="http://hl7.org/fhir"> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-assembly-order"> <valueCode value="NL4"/> </extension> <text value="Irma Jongeneel-de Haas"/> <family value="Jongeneel-de Haas"> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-own-name"> <valueString value="Jongeneel"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix"> <valueString value="de"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-partner-name"> <valueString value="Haas"/> </extension> </family> <given value="Irma"/> </valueHumanName> Unstructured HumanName:<valueHumanName xmlns="http://hl7.org/fhir"> <text value="Irma Jongeneel-de Haas"/> </valueHumanName> | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) nl-core-humanname-1: if you specify a prefix for an own name then an own name is also expected (: name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty().not()) nl-core-humanname-2: if you specify a voorvoegsel for a partner name then a partner name is also expected (: name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-name').empty().not()) zv-pat-1: Either Patient.name.given and/or Patient.name.family and/or Patient.name.text SHALL be present. (: (family.exists() or given.exists() or text.exists())) zv-pat-2: To be usable for a wide range of internationally available applications, the Patient.name.text SHOULD be present. (: text.exists()) | ||||
72. Patient.name.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
73. Patient.name.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.name.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
74. Patient.name.extension:humannameAssemblyOrder | |||||
SliceName | humannameAssemblyOrder | ||||
Definition | A code that represents the preferred display order of the components of this human name. | ||||
Control | 0..* | ||||
Type | Extension(assembly-order) (Extension Type: code) | ||||
75. Patient.name.extension:humannameAssemblyOrder.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
76. Patient.name.extension:humannameAssemblyOrder.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.name.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
77. Patient.name.extension:humannameAssemblyOrder.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-assembly-order | ||||
78. Patient.name.extension:humannameAssemblyOrder.valueCode:valueCode | |||||
SliceName | valueCode | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from HumanNameAssemblyOrder A code that represents the preferred display order of the components of a human nam | ||||
Type | code | ||||
79. Patient.name.use | |||||
Definition | Identifies the purpose for this name. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from NameUse The use of a human nam | ||||
Type | code | ||||
Is Modifier | true | ||||
Summary | true | ||||
Requirements | Allows the appropriate name for a particular context of use to be selected from among a set of names. | ||||
Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary or old name etc.for a current/permanent one. Applications can assume that a name is current unless it explicitly says that it is temporary or old. | ||||
80. Patient.name.text | |||||
Definition | A full text representation of the name. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Requirements | A renderable, unencoded form. | ||||
Comments | Can provide both a text representation and structured parts. | ||||
81. Patient.name.family | |||||
Definition | The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Alternate Names | surname, Achternaam | ||||
Comments | Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures). | ||||
82. Patient.name.family.id | |||||
Definition | unique id for the element within a resource (for internal references) | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
83. Patient.name.family.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.name.family.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
84. Patient.name.family.extension:humannameOwnPrefix | |||||
SliceName | humannameOwnPrefix | ||||
Definition | The prefix portion (e.g. voorvoegsel) inclusive of the space between the prefix and the surname, if applicable, of the family name that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(own-prefix) (Extension Type: string) | ||||
Alternate Names | VoorvoegselGeslachtsnaam | ||||
Comments | An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
85. Patient.name.family.extension:humannameOwnPrefix.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
86. Patient.name.family.extension:humannameOwnPrefix.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
87. Patient.name.family.extension:humannameOwnPrefix.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-own-prefix | ||||
88. Patient.name.family.extension:humannameOwnPrefix.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
89. Patient.name.family.extension:humannameOwnName | |||||
SliceName | humannameOwnName | ||||
Definition | The person’s official last name. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(own-name) (Extension Type: string) | ||||
Alternate Names | Geslachtsnaam | ||||
Comments | The portion of the family name that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
90. Patient.name.family.extension:humannameOwnName.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
91. Patient.name.family.extension:humannameOwnName.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
92. Patient.name.family.extension:humannameOwnName.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-own-name | ||||
93. Patient.name.family.extension:humannameOwnName.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
94. Patient.name.family.extension:humannamePartnerPrefix | |||||
SliceName | humannamePartnerPrefix | ||||
Definition | Voorvoegsel derived from person's partner's surname inclusive of the space between the prefix and the surname, if applicable. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(partner-prefix) (Extension Type: string) | ||||
Alternate Names | VoorvoegselGeslachtsnaamPartner | ||||
Comments | An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to identify it as a separate sub-component. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
95. Patient.name.family.extension:humannamePartnerPrefix.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
96. Patient.name.family.extension:humannamePartnerPrefix.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
97. Patient.name.family.extension:humannamePartnerPrefix.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix | ||||
98. Patient.name.family.extension:humannamePartnerPrefix.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
99. Patient.name.family.extension:humannamePartnerName | |||||
SliceName | humannamePartnerName | ||||
Definition | Partner’s official last name. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(partner-name) (Extension Type: string) | ||||
Alternate Names | GeslachtsnaamPartner | ||||
Comments | The portion of the family name that is derived from the person's partner's surname, as distinguished from any portion that is derived from the surname of the person's own name. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
100. Patient.name.family.extension:humannamePartnerName.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
101. Patient.name.family.extension:humannamePartnerName.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
102. Patient.name.family.extension:humannamePartnerName.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-partner-name | ||||
103. Patient.name.family.extension:humannamePartnerName.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
104. Patient.name.family.value | |||||
Definition | The actual value | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Max Length | 1048576 | ||||
105. Patient.name.given | |||||
Definition | Note that in order to mark the type of a given name, the FHIR standard extension for ISO 21090 EN Qualifiers is to be used. Examples include call me name (Dutch: roepnaam) and initials. Each initial is expected to be delimited by a dot. | ||||
Control | 0..* | ||||
Type | string | ||||
Summary | true | ||||
Alternate Names | first name, middle name, Voornamen, Initialen, Roepnaam | ||||
Comments | Note that in order to mark the type of a given name, the FHIR standard extension for ISO 21090 EN Qualifiers is to be used. Examples include call me name (Dutch: roepnaam) and initials. Each initial is expected to be delimited by a dot. To be conformant to the HCIM for NameInformation, at least the following qualifiers SHALL be supported: BR, IN and CL. The qualifier BR maps to the HCIM concept FirstNames, IN maps to Initials and CL to GivenName. Please see the compatibility note on the containing element as well! | ||||
106. Patient.name.given.id | |||||
Definition | unique id for the element within a resource (for internal references) | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
107. Patient.name.given.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.name.given.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
108. Patient.name.given.extension:iso21090EnQualifier | |||||
SliceName | iso21090EnQualifier | ||||
Definition | A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(EN-qualifier) (Extension Type: code) | ||||
Comments | Used to indicate additional information about the name part and how it should be used. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
109. Patient.name.given.extension:iso21090EnQualifier.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
110. Patient.name.given.extension:iso21090EnQualifier.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.name.given.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
111. Patient.name.given.extension:iso21090EnQualifier.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier | ||||
112. Patient.name.given.extension:iso21090EnQualifier.valueCode:valueCode | |||||
SliceName | valueCode | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from EntityNamePartQualifier A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part typ | ||||
Type | code | ||||
113. Patient.name.given.value | |||||
Definition | The actual value | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Max Length | 1048576 | ||||
114. Patient.name.prefix | |||||
Definition | Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name. | ||||
Control | 0..* | ||||
Type | string | ||||
Summary | true | ||||
115. Patient.name.suffix | |||||
Definition | Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name. | ||||
Control | 0..* | ||||
Type | string | ||||
Summary | true | ||||
116. Patient.name.period | |||||
Definition | Indicates the period of time when this name was valid for the named person. | ||||
Control | 0..1 | ||||
Type | Period | ||||
Summary | true | ||||
Requirements | Allows names to be placed in historical context. | ||||
117. Patient.telecom | |||||
Definition | A contact detail for the individual. Note that there is no support for multiple use values like 'mobile business'. | ||||
Control | 0..* This element is affected by the following invariants: ele-1 | ||||
Type | ContactPoint(nl-core-contactpoint) | ||||
Requirements | People have (primary) ways to contact them in some way such as phone, email. | ||||
Alternate Names | Contactgegevens | ||||
Comments | A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address may not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone). | ||||
Example | Mobile business phone number. Note: the mobile nature stems from the number being an 06-* number.:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="phone"/> <value value="+31611234567"/> <use value="work"/> </valueContactPoint> Mobile phone number undetermined private/business. Note: the mobile nature stems from the number being an 06-* number.:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="phone"/> <value value="+31611234567"/> <use value="mobile"/> </valueContactPoint> Primary Home Land Line:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="LL"/> <display value="Land Line"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Land Line:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="LL"/> <display value="Land Line"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Land Line:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="LL"/> <display value="Land Line"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="work"/> </valueContactPoint> Primary Home Fax:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="FAX"/> <display value="Fax"/> </coding> </valueCodeableConcept> </extension> <system value="fax"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Fax:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="FAX"/> <display value="Fax"/> </coding> </valueCodeableConcept> </extension> <system value="fax"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Fax:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="FAX"/> <display value="Fax"/> </coding> </valueCodeableConcept> </extension> <system value="fax"/> <value value="..."/> <use value="work"/> </valueContactPoint> Primary Home Mobile Phone:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="MC"/> <display value="Mobile Phone"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Mobile Phone:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="MC"/> <display value="Mobile Phone"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Mobile Phone:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="MC"/> <display value="Mobile Phone"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="work"/> </valueContactPoint> Primary Home Pager:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="PG"/> <display value="Pager"/> </coding> </valueCodeableConcept> </extension> <system value="pager"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Pager:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="PG"/> <display value="Pager"/> </coding> </valueCodeableConcept> </extension> <system value="pager"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Pager:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="PG"/> <display value="Pager"/> </coding> </valueCodeableConcept> </extension> <system value="pager"/> <value value="..."/> <use value="work"/> </valueContactPoint> Private email address:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="email"/> <value value="giesput@myweb.nl"/> <use value="home"/> </valueContactPoint> Work email address:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="email"/> <value value="example@workplace.nl"/> <use value="work"/> </valueContactPoint> | ||||
Invariants | Defined on this element cpt-2: A system is required if a value is provided. (: value.empty() or system.exists()) ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) | ||||
118. Patient.gender | |||||
Definition | Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from AdministrativeGender | ||||
Type | code | ||||
Must Support | true | ||||
Summary | true | ||||
Requirements | Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes. | ||||
Alternate Names | Geslacht | ||||
Comments | The gender may not match the biological sex as determined by genetics, or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than M and F, though the vast majority of systems and contexts only support M and F. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific gender aspect of interest (anatomical, chromosonal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosonal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overrideable error, not a "hard" error. | ||||
119. Patient.gender.id | |||||
Definition | unique id for the element within a resource (for internal references) | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
120. Patient.gender.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.gender.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
121. Patient.gender.extension:GeslachtCodelijst | |||||
SliceName | GeslachtCodelijst | ||||
Definition | Patient’s administrative gender. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(Zib extension code specification) (Extension Type: CodeableConcept) | ||||
Alternate Names | Bevat de specifieke code conform de zib, bij een FHIR-element die een verplichte koppeling heeft met een bepaalde FHIR waardelijst of een FHIR element die niet gecodeerd is gedefinieerd, terwijl de zib dit wel doet., Geslacht | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
122. Patient.gender.extension:GeslachtCodelijst.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
123. Patient.gender.extension:GeslachtCodelijst.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.gender.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
124. Patient.gender.extension:GeslachtCodelijst.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/code-specification | ||||
125. Patient.gender.extension:GeslachtCodelijst.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Patient.gender.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
126. Patient.gender.extension:GeslachtCodelijst.value[x]:valueCodeableConcept | |||||
SliceName | valueCodeableConcept | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from GeslachtCodelijst; other codes may be used where these codes are not suitable GeslachtCodelijs | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
127. Patient.gender.value | |||||
Definition | Primitive value for code | ||||
Control | 0..1 | ||||
Type | code | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
128. Patient.birthDate | |||||
Definition | The date of birth for the individual. | ||||
Control | 0..1 | ||||
Type | date | ||||
Must Support | true | ||||
Summary | true | ||||
Requirements | Age of the individual drives many clinical processes. | ||||
Alternate Names | Geboortedatum | ||||
Comments | At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternaty/infant care systems). | ||||
LOINC Code | 21112-8 | ||||
129. Patient.deceased[x] | |||||
Definition | Indicates if the individual is deceased or not. | ||||
Control | 0..1 | ||||
Type | Choice of: boolean, dateTime | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Is Modifier | true | ||||
Summary | true | ||||
Requirements | The fact that a patient is deceased influences the clinical process. Also, in human communication and relation management it is necessary to know whether the person is alive. | ||||
Alternate Names | Overlijdensindicator/DatumOverlijden | ||||
Comments | If there's no value in the instance it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive. This element is labeled as a modifier because once a patient is marked as deceased, the actions that are appropriate to perform on the patient may be significantly different. | ||||
130. Patient.address | |||||
Definition | This datatype defines a common basis for expressing all addresses around the world, but adds extensions to express Dutch addresses specifically, according to the HCIM AddressInformation (v1.0, 2017). A Dutch Address still is a proper FHIR Address, which means that systems that cannot interpret the extensions will still be able to render and work with this datatype. To have true compatibility an implementer SHOULD use the core Address parts as intended. To have addresses work for Dutch context, the implementer SHOULD in addition use the extension elements. Separate address parts The first addition is that Dutch addresses make certain address parts separately communicable. These parts are required for use in true Dutch systems when dealing with Dutch addresses, but may not have value for international systems when information gets sent abroad. Custom address types The second addition is that the HCIM defines its own ValueSet for address types, which can only be partially expressed using the FHIR Address datatype and requires a mapping to multiple elements. The table below explains how the HCIM concepts are mapped to the various FHIR elements (see the ConceptMaps http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressUse and http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressType as well). The HCIM code itself should also be included using the AddressType extension. | HCIM | If Address.type is both then this is to be understood as a dual purpose address (postal and physical). Systems that support importing it like this are encouraged to do so, otherwise they may need to import this as two separate addresses. NOTE: FHIR core defines the AD-use extension to further specify the postal address type. However, the ValueSet used in that extension doesn't completely match the HCIM ValueSet. Therefore, a custom extension has been made. This doesn't preclude the use of the AD-use extension. | ||||
Control | 0..* This element is affected by the following invariants: ele-1, nl-streetname-if-official-and-other-line-parts | ||||
Type | Address(nl-core-address) | ||||
Requirements | May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification. | ||||
Alternate Names | AdresInformatie, Adresgegevens | ||||
Comments | Note: address is for postal addresses, not physical locations. | ||||
Example | Example of a Vacation Home address:<valueAddress xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="HV"/> <display value="Vakantie adres"/> </coding> </valueCodeableConcept> </extension> <use value="temp"/> <line value="Binnenkant 12A Hoog"/> <city value="Amsterdam"/> <state value="NH"/> <postalCode value="1000AA"/> <country value="NLD"/> </valueAddress> Example of a Primary Home address:<valueAddress xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="HP"/> <display value="Officieel adres"/> </coding> </valueCodeableConcept> </extension> <extension url="http://fhir.nl/fhir/StructureDefinition/nl-core-address-official"> <valueBoolean value="true"/> </extension> <use value="home"/> <line value="Binnenkant to 10"/> <city value="Amsterdam"/> <state value="NH"/> <postalCode value="1001AA"/> <country value="NLD"/> </valueAddress> | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) nl-streetname-if-official-and-other-line-parts: Address.streetName in an official address SHALL have a value if one of houseNumber|buildingNumberSuffix|additionalLocator has a value (: (extension.where(url = 'http://fhir.nl/fhir/StructureDefinition/nl-core-address-official').where(value = true)).empty() or (line.extension.where(url = 'http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty().not() and (line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty().not()))) | ||||
131. Patient.maritalStatus | |||||
Definition | This field contains a patient's most recent marital (civil) status. A person’s marital status according to the terms and definition in the Dutch civil code. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from BurgerlijkeStaatCodelijst; other codes may be used where these codes are not suitable | ||||
Type | CodeableConcept | ||||
Requirements | Most, if not all systems capture it. | ||||
Alternate Names | BurgerlijkeStaat | ||||
132. Patient.multipleBirth[x] | |||||
Definition | Indicates whether the patient is part of a multiple (bool) or indicates the actual birth order (integer). | ||||
Control | 0..1 | ||||
Type | Choice of: boolean, integer | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Requirements | For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs. | ||||
Alternate Names | Meerlingindicator | ||||
Comments | Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in tripplets would be valueInteger=2 and the third born would have valueInteger=3 If a bool value was provided for this tripplets examle, then all 3 patient records would have valueBool=true (the ordering is not indicated). | ||||
133. Patient.photo | |||||
Definition | Image of the patient. | ||||
Control | 0..* | ||||
Type | Attachment | ||||
Requirements | Many EHR systems have the capability to capture an image of the patient. Fits with newer social media usage too. | ||||
134. Patient.contact | |||||
Definition | Contacts are related persons in some way, but not all related persons are contacts. The HCIM ContactPerson is designed to deal with both related persons and contacts. An HCIM ContactPerson who is a contact, is expected to have an NL-CM:3.1.2 Role primary contact ('Eerste relatie/contactpersoon') or secondary contact ('Tweede relatie/contactpersoon'). See Patient.contact.relationship in slice 'role'. | ||||
Control | 0..* | ||||
Type | BackboneElement | ||||
Requirements | Need to track people you can contact about the patient. | ||||
Alternate Names | Contactpersoon | ||||
Comments | Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) pat-1: SHALL at least contain a contact's details or a reference to an organization (: name.exists() or telecom.exists() or address.exists() or organization.exists()) | ||||
135. Patient.contact.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
136. Patient.contact.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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. | ||||
137. Patient.contact.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Summary | true | ||||
Alternate Names | extensions, user content, modifiers | ||||
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. | ||||
138. Patient.contact.relationship | |||||
Definition | The nature of the relationship between the patient and the contact person. | ||||
Control | 0..* | ||||
Binding | The codes SHALL be taken from v2 Contact Role; other codes may be used where these codes are not suitable The nature of the relationship between a patient and a contact person for that patient | ||||
Type | CodeableConcept | ||||
Requirements | Used to determine which contact person is the most relevant to approach, depending on circumstances. | ||||
Slicing | This element introduces a set of slices on Patient.contact.relationship. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
139. Patient.contact.relationship:relationship | |||||
SliceName | relationship | ||||
Definition | The nature of the relationship between the patient and the contact person. | ||||
Control | 0..* | ||||
Binding | The codes SHALL be taken from RelatieCodelijst | ||||
Type | CodeableConcept | ||||
Requirements | Used to determine which contact person is the most relevant to approach, depending on circumstances. | ||||
Alternate Names | Relatie | ||||
140. Patient.contact.relationship:role | |||||
SliceName | role | ||||
Definition | Expectation is to have at least one of primary contact ('Eerste relatie/contactpersoon') or secondary contact ('Tweede relatie/contactpersoon') | ||||
Control | 0..* | ||||
Binding | The codes SHALL be taken from RolCodelijst | ||||
Type | CodeableConcept | ||||
Requirements | Used to determine which contact person is the most relevant to approach, depending on circumstances. | ||||
Alternate Names | Rol | ||||
141. Patient.contact.name | |||||
Definition | A human's name with the ability to identify parts and usage. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | HumanName(nl-core-humanname) | ||||
Requirements | Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person. | ||||
Alternate Names | Naamgegevens | ||||
Comments | Dutch names require that certain name parts are separately communicable. For this reason, extensions are added onto the base HumanName element to mark the meaning of each part. A Dutch HumanName is still a proper FHIR HumanName; however, there might be an incompatibilty with the default FHIR mechanism for communicating given names. See the compatibility note below for more information. The extension elements cover birth name (NL: eigennaam / geslachtsnaam) and partner/spouse name. Both may have a prefix (NL: voorvoegsel). When a person marries, he or she may keep their own name, assume the partner name, append the partner name to their own name, or the other way around. Incompatibility note: It has come to light that this specification deviates from the way that the HumanName datatype is normally used. This will be fixed in a future release. However, current implementations should be aware of the special considerations regarding the use of this specification. The issue at hand is the way alternative representations of a name, like initials or a nickname, are communicated. Normally this is done using multiple HumanName instances, which are differentiated using the Since multiple implementations are based on this specification, sending systems are advised (but not required) to keep the approach with one HumanName instance, while receiving systems should be able to handle this one-instance approach. More specifically:
Example: miss Irma Jongeneel marries mister de Haas and assumes the name Irma Jongeneel-de Haas:
| ||||
Example | Structured HumanName (preferred above unstructured):<valueHumanName xmlns="http://hl7.org/fhir"> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-assembly-order"> <valueCode value="NL4"/> </extension> <text value="Irma Jongeneel-de Haas"/> <family value="Jongeneel-de Haas"> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-own-name"> <valueString value="Jongeneel"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix"> <valueString value="de"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/humanname-partner-name"> <valueString value="Haas"/> </extension> </family> <given value="Irma"/> </valueHumanName> Unstructured HumanName:<valueHumanName xmlns="http://hl7.org/fhir"> <text value="Irma Jongeneel-de Haas"/> </valueHumanName> | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) nl-core-humanname-1: if you specify a prefix for an own name then an own name is also expected (: name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty().not()) nl-core-humanname-2: if you specify a voorvoegsel for a partner name then a partner name is also expected (: name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-name').empty().not()) | ||||
142. Patient.contact.name.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
143. Patient.contact.name.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.contact.name.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
144. Patient.contact.name.extension:humannameAssemblyOrder | |||||
SliceName | humannameAssemblyOrder | ||||
Definition | A code that represents the preferred display order of the components of this human name. | ||||
Control | 0..* | ||||
Type | Extension(assembly-order) (Extension Type: code) | ||||
145. Patient.contact.name.extension:humannameAssemblyOrder.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
146. Patient.contact.name.extension:humannameAssemblyOrder.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.contact.name.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
147. Patient.contact.name.extension:humannameAssemblyOrder.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-assembly-order | ||||
148. Patient.contact.name.extension:humannameAssemblyOrder.valueCode:valueCode | |||||
SliceName | valueCode | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from HumanNameAssemblyOrder A code that represents the preferred display order of the components of a human nam | ||||
Type | code | ||||
149. Patient.contact.name.use | |||||
Definition | Identifies the purpose for this name. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from NameUse The use of a human nam | ||||
Type | code | ||||
Is Modifier | true | ||||
Summary | true | ||||
Requirements | Allows the appropriate name for a particular context of use to be selected from among a set of names. | ||||
Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary or old name etc.for a current/permanent one. Applications can assume that a name is current unless it explicitly says that it is temporary or old. | ||||
150. Patient.contact.name.text | |||||
Definition | A full text representation of the name. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Requirements | A renderable, unencoded form. | ||||
Comments | Can provide both a text representation and structured parts. | ||||
151. Patient.contact.name.family | |||||
Definition | The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Alternate Names | surname, Achternaam | ||||
Comments | Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures). | ||||
152. Patient.contact.name.family.id | |||||
Definition | unique id for the element within a resource (for internal references) | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
153. Patient.contact.name.family.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.contact.name.family.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
154. Patient.contact.name.family.extension:humannameOwnPrefix | |||||
SliceName | humannameOwnPrefix | ||||
Definition | The prefix portion (e.g. voorvoegsel) inclusive of the space between the prefix and the surname, if applicable, of the family name that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(own-prefix) (Extension Type: string) | ||||
Alternate Names | VoorvoegselGeslachtsnaam | ||||
Comments | An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
155. Patient.contact.name.family.extension:humannameOwnPrefix.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
156. Patient.contact.name.family.extension:humannameOwnPrefix.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.contact.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
157. Patient.contact.name.family.extension:humannameOwnPrefix.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-own-prefix | ||||
158. Patient.contact.name.family.extension:humannameOwnPrefix.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
159. Patient.contact.name.family.extension:humannameOwnName | |||||
SliceName | humannameOwnName | ||||
Definition | The person’s official last name. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(own-name) (Extension Type: string) | ||||
Alternate Names | Geslachtsnaam | ||||
Comments | The portion of the family name that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
160. Patient.contact.name.family.extension:humannameOwnName.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
161. Patient.contact.name.family.extension:humannameOwnName.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.contact.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
162. Patient.contact.name.family.extension:humannameOwnName.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-own-name | ||||
163. Patient.contact.name.family.extension:humannameOwnName.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
164. Patient.contact.name.family.extension:humannamePartnerPrefix | |||||
SliceName | humannamePartnerPrefix | ||||
Definition | Voorvoegsel derived from person's partner's surname inclusive of the space between the prefix and the surname, if applicable. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(partner-prefix) (Extension Type: string) | ||||
Alternate Names | VoorvoegselGeslachtsnaamPartner | ||||
Comments | An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to identify it as a separate sub-component. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
165. Patient.contact.name.family.extension:humannamePartnerPrefix.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
166. Patient.contact.name.family.extension:humannamePartnerPrefix.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.contact.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
167. Patient.contact.name.family.extension:humannamePartnerPrefix.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix | ||||
168. Patient.contact.name.family.extension:humannamePartnerPrefix.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
169. Patient.contact.name.family.extension:humannamePartnerName | |||||
SliceName | humannamePartnerName | ||||
Definition | Partner’s official last name. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(partner-name) (Extension Type: string) | ||||
Alternate Names | GeslachtsnaamPartner | ||||
Comments | The portion of the family name that is derived from the person's partner's surname, as distinguished from any portion that is derived from the surname of the person's own name. If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
170. Patient.contact.name.family.extension:humannamePartnerName.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
171. Patient.contact.name.family.extension:humannamePartnerName.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.contact.name.family.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
172. Patient.contact.name.family.extension:humannamePartnerName.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/humanname-partner-name | ||||
173. Patient.contact.name.family.extension:humannamePartnerName.valueString:valueString | |||||
SliceName | valueString | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | string | ||||
174. Patient.contact.name.family.value | |||||
Definition | The actual value | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Max Length | 1048576 | ||||
175. Patient.contact.name.given | |||||
Definition | Note that in order to mark the type of a given name, the FHIR standard extension for ISO 21090 EN Qualifiers is to be used. Examples include call me name (Dutch: roepnaam) and initials. Each initial is expected to be delimited by a dot. | ||||
Control | 0..* | ||||
Type | string | ||||
Summary | true | ||||
Alternate Names | first name, middle name, Voornamen, Initialen, Roepnaam | ||||
Comments | Note that in order to mark the type of a given name, the FHIR standard extension for ISO 21090 EN Qualifiers is to be used. Examples include call me name (Dutch: roepnaam) and initials. Each initial is expected to be delimited by a dot. To be conformant to the HCIM for NameInformation, at least the following qualifiers SHALL be supported: BR, IN and CL. The qualifier BR maps to the HCIM concept FirstNames, IN maps to Initials and CL to GivenName. Please see the compatibility note on the containing element as well! | ||||
176. Patient.contact.name.given.id | |||||
Definition | unique id for the element within a resource (for internal references) | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
177. Patient.contact.name.given.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.contact.name.given.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
178. Patient.contact.name.given.extension:iso21090EnQualifier | |||||
SliceName | iso21090EnQualifier | ||||
Definition | A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(EN-qualifier) (Extension Type: code) | ||||
Comments | Used to indicate additional information about the name part and how it should be used. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
179. Patient.contact.name.given.extension:iso21090EnQualifier.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
180. Patient.contact.name.given.extension:iso21090EnQualifier.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.contact.name.given.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
181. Patient.contact.name.given.extension:iso21090EnQualifier.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier | ||||
182. Patient.contact.name.given.extension:iso21090EnQualifier.valueCode:valueCode | |||||
SliceName | valueCode | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from EntityNamePartQualifier A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part typ | ||||
Type | code | ||||
183. Patient.contact.name.given.value | |||||
Definition | The actual value | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Max Length | 1048576 | ||||
184. Patient.contact.name.prefix | |||||
Definition | Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name. | ||||
Control | 0..* | ||||
Type | string | ||||
Summary | true | ||||
185. Patient.contact.name.suffix | |||||
Definition | Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name. | ||||
Control | 0..* | ||||
Type | string | ||||
Summary | true | ||||
186. Patient.contact.name.period | |||||
Definition | Indicates the period of time when this name was valid for the named person. | ||||
Control | 0..1 | ||||
Type | Period | ||||
Summary | true | ||||
Requirements | Allows names to be placed in historical context. | ||||
187. Patient.contact.telecom | |||||
Definition | Contact information includes a person's telephone numbers and email addresses. This datatype defines a common basis for expressing all contact information around the world, but adds extensions to express Dutch contacts specifically, according to the HCIM ContactInformation (v1.0, 2017). A Dutch ContactPoint still is a proper FHIR ContactPoint, which means that systems that cannot interpret the extensions will still be able to render and work with this datatype. The table below explains how the HCIM concepts are mapped to the various FHIR elements. The HCIM code itself should also be included using the TelecomType extension. | HCIM | | ||||
Control | 0..* This element is affected by the following invariants: ele-1 | ||||
Type | ContactPoint(nl-core-contactpoint) | ||||
Requirements | People have (primary) ways to contact them in some way such as phone, email. | ||||
Alternate Names | Contactgegevens | ||||
Comments | Telecommunication data details (phone/email) is physically modeled in the HCIM Patient, which is why the telecommunication mappings appear to be coming from the HCIM Patient instead of the HCIM ContactPerson | ||||
Example | Mobile business phone number. Note: the mobile nature stems from the number being an 06-* number.:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="phone"/> <value value="+31611234567"/> <use value="work"/> </valueContactPoint> Mobile phone number undetermined private/business. Note: the mobile nature stems from the number being an 06-* number.:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="phone"/> <value value="+31611234567"/> <use value="mobile"/> </valueContactPoint> Primary Home Land Line:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="LL"/> <display value="Land Line"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Land Line:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="LL"/> <display value="Land Line"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Land Line:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="LL"/> <display value="Land Line"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="work"/> </valueContactPoint> Primary Home Fax:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="FAX"/> <display value="Fax"/> </coding> </valueCodeableConcept> </extension> <system value="fax"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Fax:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="FAX"/> <display value="Fax"/> </coding> </valueCodeableConcept> </extension> <system value="fax"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Fax:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.22.1"/> <code value="FAX"/> <display value="Fax"/> </coding> </valueCodeableConcept> </extension> <system value="fax"/> <value value="..."/> <use value="work"/> </valueContactPoint> Primary Home Mobile Phone:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="MC"/> <display value="Mobile Phone"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Mobile Phone:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="MC"/> <display value="Mobile Phone"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Mobile Phone:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="MC"/> <display value="Mobile Phone"/> </coding> </valueCodeableConcept> </extension> <system value="phone"/> <value value="..."/> <use value="work"/> </valueContactPoint> Primary Home Pager:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="PG"/> <display value="Pager"/> </coding> </valueCodeableConcept> </extension> <system value="pager"/> <value value="..."/> <use value="home"/> </valueContactPoint> Temporary Pager:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="PG"/> <display value="Pager"/> </coding> </valueCodeableConcept> </extension> <system value="pager"/> <value value="..."/> <use value="temp"/> </valueContactPoint> Primary Work Pager:<valueContactPoint xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-TelecomType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="PG"/> <display value="Pager"/> </coding> </valueCodeableConcept> </extension> <system value="pager"/> <value value="..."/> <use value="work"/> </valueContactPoint> Private email address:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="email"/> <value value="giesput@myweb.nl"/> <use value="home"/> </valueContactPoint> Work email address:<valueContactPoint xmlns="http://hl7.org/fhir"> <system value="email"/> <value value="example@workplace.nl"/> <use value="work"/> </valueContactPoint> | ||||
Invariants | Defined on this element cpt-2: A system is required if a value is provided. (: value.empty() or system.exists()) ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) | ||||
188. Patient.contact.address | |||||
Definition | This datatype defines a common basis for expressing all addresses around the world, but adds extensions to express Dutch addresses specifically, according to the HCIM AddressInformation (v1.0, 2017). A Dutch Address still is a proper FHIR Address, which means that systems that cannot interpret the extensions will still be able to render and work with this datatype. To have true compatibility an implementer SHOULD use the core Address parts as intended. To have addresses work for Dutch context, the implementer SHOULD in addition use the extension elements. Separate address parts The first addition is that Dutch addresses make certain address parts separately communicable. These parts are required for use in true Dutch systems when dealing with Dutch addresses, but may not have value for international systems when information gets sent abroad. Custom address types The second addition is that the HCIM defines its own ValueSet for address types, which can only be partially expressed using the FHIR Address datatype and requires a mapping to multiple elements. The table below explains how the HCIM concepts are mapped to the various FHIR elements (see the ConceptMaps http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressUse and http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressType as well). The HCIM code itself should also be included using the AddressType extension. | HCIM | If Address.type is both then this is to be understood as a dual purpose address (postal and physical). Systems that support importing it like this are encouraged to do so, otherwise they may need to import this as two separate addresses. NOTE: FHIR core defines the AD-use extension to further specify the postal address type. However, the ValueSet used in that extension doesn't completely match the HCIM ValueSet. Therefore, a custom extension has been made. This doesn't preclude the use of the AD-use extension. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1, nl-streetname-if-official-and-other-line-parts | ||||
Type | Address(nl-core-address) | ||||
Requirements | Need to keep track where the contact person can be contacted per postal mail or visited. | ||||
Alternate Names | AdresInformatie, Adresgegevens | ||||
Comments | Note: address is for postal addresses, not physical locations. | ||||
Example | Example of a Vacation Home address:<valueAddress xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="HV"/> <display value="Vakantie adres"/> </coding> </valueCodeableConcept> </extension> <use value="temp"/> <line value="Binnenkant 12A Hoog"/> <city value="Amsterdam"/> <state value="NH"/> <postalCode value="1000AA"/> <country value="NLD"/> </valueAddress> Example of a Primary Home address:<valueAddress xmlns="http://hl7.org/fhir"> <extension url="http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v3/AddressUse"/> <code value="HP"/> <display value="Officieel adres"/> </coding> </valueCodeableConcept> </extension> <extension url="http://fhir.nl/fhir/StructureDefinition/nl-core-address-official"> <valueBoolean value="true"/> </extension> <use value="home"/> <line value="Binnenkant to 10"/> <city value="Amsterdam"/> <state value="NH"/> <postalCode value="1001AA"/> <country value="NLD"/> </valueAddress> | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) nl-streetname-if-official-and-other-line-parts: Address.streetName in an official address SHALL have a value if one of houseNumber|buildingNumberSuffix|additionalLocator has a value (: (extension.where(url = 'http://fhir.nl/fhir/StructureDefinition/nl-core-address-official').where(value = true)).empty() or (line.extension.where(url = 'http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty().not() and (line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty().not()))) | ||||
189. Patient.contact.gender | |||||
Definition | Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from AdministrativeGender The gender of a person used for administrative purposes | ||||
Type | code | ||||
Requirements | Needed to address the person correctly. | ||||
190. Patient.contact.organization | |||||
Definition | Organization on behalf of which the contact is acting or for which the contact is working. | ||||
Control | 0..1 This element is affected by the following invariants: pat-1 | ||||
Type | Reference(Organization) | ||||
Requirements | For guardians or business related contacts, the organization is relevant. | ||||
191. Patient.contact.period | |||||
Definition | The period during which this contact person or organization is valid to be contacted relating to this patient. | ||||
Control | 0..1 | ||||
Type | Period | ||||
192. Patient.animal | |||||
Definition | This patient is known to be an animal. | ||||
Control | 0..1 | ||||
Type | BackboneElement | ||||
Is Modifier | true | ||||
Summary | true | ||||
Requirements | Many clinical systems are extended to care for animal patients as well as human. | ||||
Comments | The animal element is labeled "Is Modifier" since patients may be non-human. Systems SHALL either handle patient details appropriately (e.g. inform users patient is not human) or reject declared animal records. The absense of the animal element does not imply that the patient is a human. If a system requires such a positive assertion that the patient is human, an extension will be required. (Do not use a species of homo-sapiens in animal species, as this would incorrectly infer that the patient is an animal). | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) | ||||
193. Patient.animal.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
194. Patient.animal.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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. | ||||
195. Patient.animal.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Summary | true | ||||
Alternate Names | extensions, user content, modifiers | ||||
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. | ||||
196. Patient.animal.species | |||||
Definition | Identifies the high level taxonomic categorization of the kind of animal. | ||||
Control | 1..1 | ||||
Binding | For example codes, see AnimalSpecies The species of an animal | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
Requirements | Need to know what kind of animal. | ||||
Comments | If the patient is non-human, at least a species SHALL be specified. Species SHALL be a widely recognised taxonomic classification. It may or may not be Linnaean taxonomy and may or may not be at the level of species. If the level is finer than species--such as a breed code--the code system used SHALL allow inference of the species. (The common example is that the word "Hereford" does not allow inference of the species Bos taurus, because there is a Hereford pig breed, but the SNOMED CT code for "Hereford Cattle Breed" does.). | ||||
197. Patient.animal.breed | |||||
Definition | Identifies the detailed categorization of the kind of animal. | ||||
Control | 0..1 | ||||
Binding | For example codes, see AnimalBreeds The breed of an animal | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
Requirements | May need to know the specific kind within the species. | ||||
Comments | Breed MAY be used to provide further taxonomic or non-taxonomic classification. It may involve local or proprietary designation--such as commercial strain--and/or additional information such as production type. | ||||
198. Patient.animal.genderStatus | |||||
Definition | Indicates the current state of the animal's reproductive organs. | ||||
Control | 0..1 | ||||
Binding | For example codes, see GenderStatus The state of the animal's reproductive organs | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
Requirements | Gender status can affect housing and animal behavior. | ||||
199. Patient.communication | |||||
Definition | Languages which may be used to communicate with the patient about his or her health. | ||||
Control | 0..* | ||||
Type | BackboneElement | ||||
Requirements | If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest. | ||||
Alternate Names | Taalvaardigheid | ||||
Comments | If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) | ||||
200. Patient.communication.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
201. Patient.communication.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.communication.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
202. Patient.communication.extension:languageProficiency | |||||
SliceName | languageProficiency | ||||
Definition | Proficiency level of the communication. | ||||
Control | 0..* This element is affected by the following invariants: ele-1 | ||||
Type | Extension(proficiency) (Complex Extension) | ||||
Comments | The HCIM concepts LanguageControlListening, LanguageControlReading, LanguageControlSpeaking are captuperd using a mocked offical HL7 core extension from the R4 FHIR specification. Each of these three concepts is encoded as a copy of the extension, typed using the code in the type slice according to the following mapping: * LanguaneControlListening maps to code 'RSP' (Received spoken) * LanguageControlReading maps to code 'RWR' (Received written) * LanguageControlSpeaking maps to code 'ESP' (Expressed spoken) | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
203. Patient.communication.extension:languageProficiency.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
204. Patient.communication.extension:languageProficiency.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.communication.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
205. Patient.communication.extension:languageProficiency.extension:type | |||||
SliceName | type | ||||
Definition | An Extension | ||||
Control | 1..1 | ||||
Type | Extension | ||||
206. Patient.communication.extension:languageProficiency.extension:type.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
207. Patient.communication.extension:languageProficiency.extension:type.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.communication.extension.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
208. Patient.communication.extension:languageProficiency.extension:type.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | type | ||||
209. Patient.communication.extension:languageProficiency.extension:type.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Type | Coding | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Patient.communication.extension.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
210. Patient.communication.extension:languageProficiency.extension:type.value[x]:valueCoding | |||||
SliceName | valueCoding | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from LanguageAbilityMode; other codes may be used where these codes are not suitable | ||||
Type | Coding | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
211. Patient.communication.extension:languageProficiency.extension:level | |||||
SliceName | level | ||||
Definition | An Extension | ||||
Control | 1..1 | ||||
Type | Extension | ||||
212. Patient.communication.extension:languageProficiency.extension:level.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
213. Patient.communication.extension:languageProficiency.extension:level.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Patient.communication.extension.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
214. Patient.communication.extension:languageProficiency.extension:level.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | level | ||||
215. Patient.communication.extension:languageProficiency.extension:level.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Type | Coding | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Patient.communication.extension.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
216. Patient.communication.extension:languageProficiency.extension:level.value[x]:valueCoding | |||||
SliceName | valueCoding | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from LanguageAbilityProficiency; other codes may be used where these codes are not suitable | ||||
Type | Coding | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
217. Patient.communication.extension:languageProficiency.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/patient-proficiency | ||||
218. Patient.communication.extension:languageProficiency.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..0 | ||||
Type | Choice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
219. Patient.communication.extension:comment | |||||
SliceName | comment | ||||
Definition | An Extension | ||||
Control | 0..* This element is affected by the following invariants: ele-1 | ||||
Type | Extension(Comment) (Extension Type: string) | ||||
Alternate Names | Toelichting | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
220. Patient.communication.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Summary | true | ||||
Alternate Names | extensions, user content, modifiers | ||||
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. | ||||
221. Patient.communication.language | |||||
Definition | The language of communication. The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable
A human language
| ||||
Type | CodeableConcept | ||||
Requirements | Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. | ||||
Alternate Names | CommunicatieTaal | ||||
Comments | The FHIR value set http://hl7.org/fhir/valueset-languages.html is used instead of the HCIM value set CommunicationLanguageCodelist. The FHIR value set uses the code system urn:ietf:bcp:47 which includes the ISO-639-2 alpha code system used by the HCIM value set. | ||||
222. Patient.communication.preferred | |||||
Definition | Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). | ||||
Control | 0..1 | ||||
Type | boolean | ||||
Requirements | People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method. | ||||
Comments | This language is specifically identified for communicating healthcare information. | ||||
223. Patient.generalPractitioner | |||||
Definition | Patient's nominated care provider. | ||||
Control | 0..1 | ||||
Type | Reference(nl-core-organization|nl-core-practitioner) | ||||
Alternate Names | careProvider, Huisarts | ||||
Comments | This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disablity setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources. | ||||
224. Patient.generalPractitioner.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
225. Patient.generalPractitioner.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Patient.generalPractitioner.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
226. Patient.generalPractitioner.extension:practitionerRole | |||||
SliceName | practitionerRole | ||||
Definition | Optional Extension Element - found in all resources. | ||||
Control | 0..1 | ||||
Type | Extension(PractitionerRole Reference) (Extension Type: Reference) | ||||
227. Patient.generalPractitioner.reference | |||||
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | ||||
Control | 0..1 This element is affected by the following invariants: ref-1 | ||||
Type | string | ||||
Summary | true | ||||
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | ||||
228. Patient.generalPractitioner.identifier | |||||
Definition | An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 0..1 | ||||
Type | Identifier | ||||
Summary | true | ||||
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. | ||||
229. Patient.generalPractitioner.display | |||||
Definition | Plain text narrative that identifies the resource in addition to the resource reference. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | ||||
230. Patient.managingOrganization | |||||
Definition | Organization that is the custodian of the patient record. | ||||
Control | 0..1 | ||||
Type | Reference(Organization) | ||||
Summary | true | ||||
Requirements | Need to know who recognizes this patient record, manages and updates it. | ||||
Comments | There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association). | ||||
231. Patient.link | |||||
Definition | Link to another patient resource that concerns the same actual patient. | ||||
Control | 0..* | ||||
Type | BackboneElement | ||||
Is Modifier | true | ||||
Summary | true | ||||
Requirements | There are multiple usecases:
| ||||
Comments | There is no assumption that linked patient records have mutual links. This element is labelled as a modifier because it may not be the main Patient resource, and the referenced patient should be used instead of this Patient record. This is when the link.type value is 'replaced-by'. | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) | ||||
232. Patient.link.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
233. Patient.link.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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. | ||||
234. Patient.link.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Summary | true | ||||
Alternate Names | extensions, user content, modifiers | ||||
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. | ||||
235. Patient.link.other | |||||
Definition | The other patient resource that the link refers to. | ||||
Control | 1..1 | ||||
Type | Reference(Patient|RelatedPerson) | ||||
Summary | true | ||||
Comments | Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual. | ||||
236. Patient.link.type | |||||
Definition | The type of link between this patient resource and another patient resource. | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from LinkType The type of link between this patient resource and another patient resource | ||||
Type | code | ||||
Summary | true |