ZorgDomein Integrator FHIR Edition | ZD Patient

ZD Patient (Patient)	S I		Patient	Element id Patient Short description Information about an individual receiving health care services Alternate names SubjectOfCare Client Resident Definition Demographics and other administrative information about an individual or animal receiving care or other health-related services. Data type Patient Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative `contained.text.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()` 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()` Mappings rim: Entity. Role, or Act rim: Patient[classCode=PAT] cda: ClinicalDocument.recordTarget.patientRole w5: administrative.individual
id	Σ	0..1	id	There are no (further) constraints on this element Element id Patient.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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. Data type id
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id Patient.meta Short description Metadata about the resource 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. Data type Meta
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Patient.implicitRules Short description A set of rules under which this content was created 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. 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. Data type uri
language		0..1	codeBinding	There are no (further) constraints on this element Element id Patient.language Short description Language of the resource content Definition The base language in which the resource is written. 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). Data type code Binding A human language. Common Languages (extensible)
text	I	0..1	Narrative	There are no (further) constraints on this element Element id Patient.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display 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. 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. Data type Narrative Mappings rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id Patient.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources 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. 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. Data type Resource Mappings rim: N/A
extension		0..*	Extension	Element id Patient.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Mappings rim: N/A
pharmacy	I	0..1	Extension(Reference(nl-core-organization))	Element id Patient.extension:pharmacy Short description Reference to patient's primary pharmacy Alternate names extensions, user content Definition Reference to patient's primary pharmacy 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. Data type Extension(Reference(nl-core-organization)) Extension URL http://fhir.nl/fhir/StructureDefinition/nl-core-preferred-pharmacy Constraints 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()` Mappings rim: N/A rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Patient.extension:pharmacy.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.extension:pharmacy.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.extension:pharmacy.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://fhir.nl/fhir/StructureDefinition/nl-core-preferred-pharmacy Mappings rim: N/A
valueReference		1..1	Reference(nl-core-organization)	There are no (further) constraints on this element Element id Patient.extension:pharmacy.valueReference:valueReference Short description Value of extension 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). Data type Reference(nl-core-organization) Mappings rim: N/A
modifierExtension	?!	0..*	Extension	There are no (further) constraints on this element Element id Patient.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: N/A
identifier	Σ	0..*	Identifier	Element id Patient.identifier Short description An identifier for this patient Definition An identifier for this patient. Requirements Patients are almost always assigned specific numerical identifiers. Data type Identifier Sliced: Unordered, Open, by system(Value) Mappings v2: PID-3 rim: id cda: .id w5: id
BSN	S Σ	0..1	Identifier	Element id Patient.identifier:BSN Short description BSN Definition An identifier for this patient. Requirements Patients are almost always assigned specific numerical identifiers. Data type Identifier Mappings v2: PID-3 rim: id cda: .id w5: id
id		0..1	string	There are no (further) constraints on this element Element id Patient.identifier:BSN.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.identifier:BSN.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
use	Σ ?!	1..1	codeBindingFixed Value	Element id Patient.identifier:BSN.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. 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. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Fixed value official Mappings v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Patient.identifier:BSN.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. 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. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Mappings v2: CX.5 rim: Role.code or implied by context
system	Σ	1..1	uriFixed Value	Element id Patient.identifier:BSN.system Short description The namespace for the identifier value Definition Establishes the namespace for the value - that is, a URL that describes a set values that are unique. 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. Data type uri Fixed value http://fhir.nl/fhir/NamingSystem/bsn Mappings v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	Σ	1..1	string	Element id Patient.identifier:BSN.value Short description The value that is unique Definition The portion of the identifier typically relevant to the user and which is unique within the context of the system. Comments 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. Data type string Examples General 123456 General 447363669 Mappings v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Patient.identifier:BSN.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Data type Period Mappings v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Patient.identifier:BSN.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. 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. Data type Reference(Organization) Mappings v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
active	Σ ?!	0..1	boolean	There are no (further) constraints on this element Element id Patient.active Short description Whether this patient's record is in active use Definition Whether this patient record is in active use. 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. Data type boolean Default value true Mappings rim: statusCode cda: n/a w5: status
name	S Σ I	0..*	nl-core-humanname	Element id Patient.name Short description Name of a human - parts and usage Alternate names Naamgegevens Definition A human's name with the ability to identify parts and usage. Requirements Need to be able to track the patient by multiple names. Examples are your official name and a partner name. Comments Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely. A Dutch HumanName is a proper FHIR HumanName. Systems that do not understand any of the extensions, will be able to render and work with a Dutch name. Dutch names make certain name parts seaprately communicable. These parts are required for use in true Dutch systems when dealing with Dutch names, but may not have value for international systems when information gets sent abroad. To have true compatibility an implementer SHOULD use the core HumanName parts as intended. To have names work for Dutch context, the implementer SHOULD in addition use the extension elements. 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. For this reason, there are extensions for marking each part for what it is. Example: miss Irma Jongeneel marries mister de Haas and assumes the name Irma Jongeneel-de Haas family = "Jongeneel-de Haas" given = "Irma" humanname-own-name = "Jongeneel" humanname-partner-prefix = "de " humanname-partner-name = "Haas" Data type nl-core-humanname Constraints 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()` Examples Structured HumanName (preferred above unstructured) { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/humanname-assembly-order", "valueCode": "NL4" } ], "use": "official", "family": "Jongeneel-de Haas", "_family": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/humanname-own-name", "valueString": "Jongeneel" }, { "url": "http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix", "valueString": "de" }, { "url": "http://hl7.org/fhir/StructureDefinition/humanname-partner-name", "valueString": "Haas" } ] }, "given": [ "Irma", "I." ], "_given": [ { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier", "valueCode": "CL" } ] }, { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier", "valueCode": "IN" } ] } ] } Unstructured HumanName { "use": "official", "text": "Irma Jongeneel-de Haas" } Mappings v2: PID-5, PID-9 rim: name cda: .patient.name rim: n/a v2: XPN rim: EN (actually, PN) servd: ProviderName hcim-nameinformation-v2.0.1-2015EN: NL-CM:0.1.6 hcim-nameinformation-v3.0-2016EN: NL-CM:0.1.6 hcim-nameinformation-v1.0.1-2017EN: NL-CM:20.4.1 BRP: 02 zib-patient: NL-CM:0.1.6
telecom	S Σ	0..*	ContactPoint	There are no (further) constraints on this element Element id Patient.telecom Short description A contact detail for the individual Definition A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. Requirements People have (primary) ways to contact them in some way such as phone, email. 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). Data type ContactPoint Mappings v2: PID-13, PID-14, PID-40 rim: telecom cda: .telecom
id		0..1	string	There are no (further) constraints on this element Element id Patient.telecom.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.telecom.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
system	Σ I	1..1	codeBinding	There are no (further) constraints on this element Element id Patient.telecom.system Short description phone \| fax \| email \| pager \| url \| sms \| other Definition Telecommunications form for contact point - what communications system is required to make use of the contact. Data type code Binding Telecommunications form for contact point ContactPointSystem (required) Mappings v2: XTN.3 rim: ./scheme servd: ./ContactPointType
value	Σ	1..1	string	There are no (further) constraints on this element Element id Patient.telecom.value Short description The actual contact point details Definition The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data type string Mappings v2: XTN.1 (or XTN.12) rim: ./url servd: ./Value
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Patient.telecom.use Short description home \| work \| temp \| old \| mobile - purpose of this contact point Definition Identifies the purpose for the contact point. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one. Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data type code Binding Use of contact point ContactPointUse (required) Mappings v2: XTN.2 - but often indicated by field rim: unique(./use) servd: ./ContactPointPurpose
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element id Patient.telecom.rank Short description Specify preferred order of use (1 = highest) Definition Specifies a preferred order in which to use a set of contacts. Contacts are ranked with lower values coming before higher values. Comments Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Data type positiveInt Mappings v2: n/a rim: n/a
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Patient.telecom.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Data type Period Mappings v2: N/A rim: ./usablePeriod[type="IVL<TS>"] servd: ./StartDate and ./EndDate
gender	S Σ	0..1	codeBinding	There are no (further) constraints on this element Element id Patient.gender Short description male \| female \| other \| unknown Definition Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes. Requirements Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes. 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. Data type code Binding The gender of a person used for administrative purposes. AdministrativeGender (required) Mappings v2: PID-8 rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/administrativeGender cda: .patient.administrativeGenderCode
birthDate	S Σ I	0..1	date	Element id Patient.birthDate Short description The date of birth for the individual Definition The date of birth for the individual. Requirements Age of the individual drives many clinical processes. 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). Data type date Constraints zd-date-1: BirthDate must be at least today. `($this as dateTime).toString().length() >= 8` Mappings v2: PID-7 rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/birthTime cda: .patient.birthTime loinc: 21112-8
deceased[x]	Σ ?!	0..1		There are no (further) constraints on this element Element id Patient.deceased[x] Short description Indicates if the individual is deceased or not Definition Indicates if the individual is deceased or not. 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. 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. Mappings v2: PID-30 (bool) and PID-29 (datetime) rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/deceasedInd, player[classCode=PSN\|ANM and determinerCode=INSTANCE]/deceasedTime cda: n/a
deceasedBoolean			boolean	There are no (further) constraints on this element Data type boolean
deceasedDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
address	S Σ I	0..*	nl-core-address	Element id Patient.address Short description Addresses for the individual Alternate names AdresInformatie 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 \| .ext:AddressType \| .ext:official \| .use \| .type \| \|-----------------------------------\|------------------\|---------------\|------\|----------\| \| Postal Address/Postadres \| PST \| \| \| postal \| \| Primary Home/Officieel adres \| HP \| true \| home \| \| \| Visit Address/Woon-/verblijfadres \| PHYS \| \| home \| physical \| \| Temporary Address/Tijdelijk adres \| TMP \| \| temp \| \| \| Work Place/Werkadres \| WP \| \| work \| \| \| Vacation Home/Vakantie adres \| HV \| \| temp \| \|` 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. Requirements May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification. Comments Note: address is for postal addresses, not physical locations. Data type nl-core-address Constraints 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())) Examples Example of a Vacation Home address { "extension": [ { "url": "http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType", "valueCodeableConcept": { "coding": [ { "system": "http://hl7.org/fhir/v3/AddressUse", "code": "HV", "display": "Vakantie adres" } ] } } ], "use": "temp", "line": [ "Binnenkant 12A Hoog" ], "_line": [ { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName", "valueString": "Binnenkant" }, { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber", "valueString": "12" }, { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix", "valueString": "A" }, { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-unitID", "valueString": "Hoog" } ] } ], "city": "Amsterdam", "state": "NH", "postalCode": "1000AA", "country": "NLD" } Example of a Primary Home address { "extension": [ { "url": "http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType", "valueCodeableConcept": { "coding": [ { "system": "http://hl7.org/fhir/v3/AddressUse", "code": "HP", "display": "Officieel adres" } ] } }, { "url": "http://fhir.nl/fhir/StructureDefinition/nl-core-address-official", "valueBoolean": true } ], "use": "home", "line": [ "Binnenkant to 10" ], "_line": [ { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName", "valueString": "Binnenkant" }, { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator", "valueString": "to" }, { "url": "http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber", "valueString": "10" } ] } ], "city": "Amsterdam", "state": "NH", "postalCode": "1001AA", "country": "NLD" } Mappings v2: PID-11 rim: addr cda: .addr rim: n/a v2: XAD rim: AD servd: Address hcim-address-v2.0.1-2015EN: NL-CM:0.1.4 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.4 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.1
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
AddressType	I	0..1	Extension(CodeableConcept)	There are no (further) constraints on this element Element id Patient.address.extension:AddressType Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. 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. Data type Extension(CodeableConcept) Extension URL http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType Constraints 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()` Mappings rim: n/a rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.extension:AddressType.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.extension:AddressType.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.extension:AddressType.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType Mappings rim: N/A
valueCodeableConcept		0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Patient.address.extension:AddressType.value[x]:valueCodeableConcept Short description AddressType Alternate names AdresSoort Definition The type of address in question, such as a home address or mailing address. Comments This extension can be used to include the HCIM AddressType code. See the documentation on the root level for mapping these codes to the various elements of this datatype. 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. Data type CodeableConcept Binding AdresSoortCodelijst AdresSoortCodelijst (extensible) Mappings rim: N/A hcim-address-v2.0.1-2015EN: NL-CM:0.1.11 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.11 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.8
official	I	0..1	Extension(boolean)	There are no (further) constraints on this element Element id Patient.address.extension:official Short description Mark an address as an 'officially registered' address. Alternate names extensions, user content, Markeer een adres als een 'officieel geregistreerd adres. Definition Mark an address as an 'officially registered' address. In Dutch context that means it is registered in the Basisregistratie persoonsgegevens (BRP) 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. Data type Extension(boolean) Extension URL http://fhir.nl/fhir/StructureDefinition/nl-core-address-official Constraints 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()` Mappings rim: n/a rim: N/A hcim-address-v2.0.1-2015EN: NL-CM:0.1.11 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.11 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.8
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.extension:official.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.extension:official.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.extension:official.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://fhir.nl/fhir/StructureDefinition/nl-core-address-official Mappings rim: N/A
valueBoolean		1..1	boolean	There are no (further) constraints on this element Element id Patient.address.extension:official.valueBoolean:valueBoolean Short description true if part of an official registry. false if it is not Alternate names true als deze deel is van een officieel register. false indien dat niet het geval is Definition When the value is true, this address is marked to be part of an official registry (Dutch realm: BRP). When the value is false, this address is explicitly marked as not part of an official registry. Meaning when missing When an address is not marked explicitly as official=true\|false then no information can be inferred from that. Data type boolean Mappings rim: N/A rim: AD/@use[.='OR']
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Patient.address.use Short description home \| work \| temp \| old - purpose of this address Definition Purpose of this address Requirements Allows an appropriate address to be chosen from a list of many. Comments This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one. Applications can assume that an address is current unless it explicitly says that it is temporary or old. Data type code Binding The use of an address AddressUse (required) Permitted Values AdresSoortCodelijst-to-AddressUse Examples General home Mappings v2: XAD.7 rim: unique(./use) servd: ./AddressPurpose hcim-address-v2.0.1-2015EN: NL-CM:0.1.11 hcim-address-v3.0-2016EN: NL-CM:0.1.11 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.8
type	Σ	0..1	codeBinding	There are no (further) constraints on this element Element id Patient.address.type Short description postal \| physical \| both Definition Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. Data type code Binding The type of an address (physical / postal) AddressType (required) Permitted Values AdresSoortCodelijst-to-AddressType Examples General both Mappings v2: XAD.18 rim: unique(./use) vcard: address type parameter hcim-address-v2.0.1-2015EN: NL-CM:0.1.11 hcim-address-v3.0-2016EN: NL-CM:0.1.11 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.8
text	Σ	0..1	string	There are no (further) constraints on this element Element id Patient.address.text Short description Text representation of the address Definition A full text representation of the address. Requirements A renderable, unencoded form. Comments Can provide both a text representation and parts. Data type string Examples General 137 Nowhere Street, Erewhon 9132 Mappings v2: XAD.1 + XAD.2 + XAD.3 + XAD.4 + XAD.5 + XAD.6 rim: ./formatted vcard: address label parameter
line	Σ	0..*	string	There are no (further) constraints on this element Element id Patient.address.line Short description Street name, number, direction & P.O. Box etc. Definition This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information. Requirements home \| work \| temp \| old - purpose of this address. Data type string Examples General 137 Nowhere Street Mappings v2: XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address) rim: AD.part[parttype = AL] vcard: street servd: ./StreetAddress (newline delimitted)
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references) Data type string
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value)
streetName	I	0..1	Extension(string)	There are no (further) constraints on this element Element id Patient.address.line.extension:streetName Short description streetName Alternate names extensions, user content Definition Street name. If the address is a P.O. Box then the Dutch word "Postbus" shall be communicated. If the address is an answer number (mailing address where the receiver pays postage) then the Dutch word "Antwoordnummer" shall be communicated. Requirements Basisregistratie Persoonsgegevens 11.10 Straatnaam 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. Data type Extension(string) Extension URL http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName Constraints 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()` Mappings rim: ADXP[partType=STR] hcim-address-v2.0.1-2015EN: NL-CM:0.1.12 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.12 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.2 BRP: 11.10
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:streetName.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:streetName.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.line.extension:streetName.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:streetName.valueString:valueString Short description Value of extension 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). Data type string Mappings rim: N/A
houseNumber	I	0..1	Extension(string)	There are no (further) constraints on this element Element id Patient.address.line.extension:houseNumber Short description houseNumber Alternate names extensions, user content Definition The element houseNumber shall contain the house number. The house number may contains non-numeric parts that further determine the address, e.g. "23a", but only if the source system cannot discretely communicate those. House letter shall, if possible, be communicated through the element buildingNumberSuffix. Information such as "to" (house boats that do not have their own house number, but are across (tegenover) a house with a house number or "3 hoog achter" are not part of this attribute. This type of information is conveyed elsewhere in the Address datatype. Requirements Basisregistratie Persoonsgegevens 11.20 Huisnummer 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. Data type Extension(string) Extension URL http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber Constraints 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()` Mappings rim: ADXP[partType=BNR] hcim-address-v2.0.1-2015EN: NL-CM:0.1.13 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.13 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.12 BRP: 11.20
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:houseNumber.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:houseNumber.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.line.extension:houseNumber.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:houseNumber.valueString:valueString Short description Value of extension 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). Data type string Mappings rim: N/A
buildingNumbersuffix	I	0..*	Extension(string)	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumbersuffix Short description buildingNumberSuffix Alternate names extensions, user content Definition HouseNumberLetter A letter following the house number as assigned by the municipal authorities. HouseNumberAddition The letters or signs needed to locate the mailbox, in addition to the house number and letter. Requirements Basisregistratie Persoonsgegevens 11.30 Huisletter 11.40 Huisnummertoevoeging 12.10 Locatieomschrijving Comments Export If a house letter as well as a house number addition is known: house letter first, followed by a space and finally the house letter suffix. If only a house letter is known send just that. No trailing space is required. If only a house letter suffix is known, communicate that with a leading space. Import If the value of buildingNumberSuffix contains no space, then the whole value is considered to be the house letter If the value of buildingNumberSuffix contains a space, then everything before the first space is considered to be the house letter, and the everything trailing the first space is considered to be the house number suffix Data type Extension(string) Extension URL http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix Constraints 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()` Mappings rim: ADXP[partType=BNS] hcim-address-v2.0.1-2015EN: NL-CM:0.1.40 hcim-address-v2.0.1-2015EN: NL-CM:0.1.41 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.40 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.41 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.11 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.10 BRP: 11.30 BRP: 11.40
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumbersuffix.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumbersuffix.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumbersuffix.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumbersuffix.value[x]:valueString Short description Value of extension 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). Data type string Mappings rim: N/A
unitID	I	0..1	Extension(string)	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID Short description unitID Alternate names extensions, user content Definition Extra information such as the building name, building number, entrance, route number. 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. Data type Extension(string) Extension URL http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-unitID Constraints 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()` Mappings rim: ADXP[partType=UNID] hcim-address-v2.0.1-2015EN: NL-CM:0.1.28 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.28 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.7
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-unitID Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.value[x]:valueString Short description Value of extension 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). Data type string Mappings rim: N/A
additionalLocator	I	0..1	Extension(string)	There are no (further) constraints on this element Element id Patient.address.line.extension:additionalLocator Short description additionalLocator Alternate names extensions, user content Definition HouseNumberIndication - The indication used for addresses that do not consist of the usual street name and house number. Requirements Basisregistratie Persoonsgegevens 11.50 Aanduiding bij huisnummer 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. Data type Extension(string) Extension URL http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator Constraints 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()` Mappings rim: ADXP[partType=ADL] hcim-address-v2.0.1-2015EN: NL-CM:0.1.42 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.42 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.9 BRP: 11.50
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:additionalLocator.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:additionalLocator.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.line.extension:additionalLocator.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:additionalLocator.valueString:valueString Short description Value of extension 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). Data type string Mappings rim: N/A
buildingNumberSuffix		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumberSuffix Short description Additional Content defined by implementations Alternate names extensions, user content Definition 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. 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. Data type Extension
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumberSuffix.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumberSuffix.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumberSuffix.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value buildingNumberSuffix Mappings rim: N/A
valueString		0..1		There are no (further) constraints on this element Element id Patient.address.line.extension:buildingNumberSuffix.valueString:valueString Short description Value of extension 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). Mappings rim: N/A
valueBase64Binary			base64Binary	There are no (further) constraints on this element Data type base64Binary
valueBoolean			boolean	There are no (further) constraints on this element Data type boolean
valueCode			code	There are no (further) constraints on this element Data type code
valueDate			date	There are no (further) constraints on this element Data type date
valueDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
valueDecimal			decimal	There are no (further) constraints on this element Data type decimal
valueId			id	There are no (further) constraints on this element Data type id
valueInstant			instant	There are no (further) constraints on this element Data type instant
valueInteger			integer	There are no (further) constraints on this element Data type integer
valueMarkdown			markdown	There are no (further) constraints on this element Data type markdown
valueOid			oid	There are no (further) constraints on this element Data type oid
valuePositiveInt			positiveInt	There are no (further) constraints on this element Data type positiveInt
valueString			string	There are no (further) constraints on this element Data type string
valueTime			time	There are no (further) constraints on this element Data type time
valueUnsignedInt			unsignedInt	There are no (further) constraints on this element Data type unsignedInt
valueUri			uri	There are no (further) constraints on this element Data type uri
valueAddress			Address	There are no (further) constraints on this element Data type Address
valueAge			Age	There are no (further) constraints on this element Data type Age
valueAnnotation			Annotation	There are no (further) constraints on this element Data type Annotation
valueAttachment			Attachment	There are no (further) constraints on this element Data type Attachment
valueCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data type CodeableConcept
valueCoding			Coding	There are no (further) constraints on this element Data type Coding
valueContactPoint			ContactPoint	There are no (further) constraints on this element Data type ContactPoint
valueCount			Count	There are no (further) constraints on this element Data type Count
valueDistance			Distance	There are no (further) constraints on this element Data type Distance
valueDuration			Duration	There are no (further) constraints on this element Data type Duration
valueHumanName			HumanName	There are no (further) constraints on this element Data type HumanName
valueIdentifier			Identifier	There are no (further) constraints on this element Data type Identifier
valueMoney			Money	There are no (further) constraints on this element Data type Money
valuePeriod			Period	There are no (further) constraints on this element Data type Period
valueQuantity			Quantity	There are no (further) constraints on this element Data type Quantity
valueRange			Range	There are no (further) constraints on this element Data type Range
valueRatio			Ratio	There are no (further) constraints on this element Data type Ratio
valueSampledData			SampledData	There are no (further) constraints on this element Data type SampledData
valueSignature			Signature	There are no (further) constraints on this element Data type Signature
valueTiming			Timing	There are no (further) constraints on this element Data type Timing
valueMeta			Meta	There are no (further) constraints on this element Data type Meta
valueReference			Reference()	There are no (further) constraints on this element Data type Reference()
unitID		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID Short description Additional Content defined by implementations Alternate names extensions, user content Definition 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. 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. Data type Extension
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value unitID Mappings rim: N/A
valueString		0..1		There are no (further) constraints on this element Element id Patient.address.line.extension:unitID.valueString:valueString Short description Value of extension 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). Mappings rim: N/A
valueBase64Binary			base64Binary	There are no (further) constraints on this element Data type base64Binary
valueBoolean			boolean	There are no (further) constraints on this element Data type boolean
valueCode			code	There are no (further) constraints on this element Data type code
valueDate			date	There are no (further) constraints on this element Data type date
valueDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
valueDecimal			decimal	There are no (further) constraints on this element Data type decimal
valueId			id	There are no (further) constraints on this element Data type id
valueInstant			instant	There are no (further) constraints on this element Data type instant
valueInteger			integer	There are no (further) constraints on this element Data type integer
valueMarkdown			markdown	There are no (further) constraints on this element Data type markdown
valueOid			oid	There are no (further) constraints on this element Data type oid
valuePositiveInt			positiveInt	There are no (further) constraints on this element Data type positiveInt
valueString			string	There are no (further) constraints on this element Data type string
valueTime			time	There are no (further) constraints on this element Data type time
valueUnsignedInt			unsignedInt	There are no (further) constraints on this element Data type unsignedInt
valueUri			uri	There are no (further) constraints on this element Data type uri
valueAddress			Address	There are no (further) constraints on this element Data type Address
valueAge			Age	There are no (further) constraints on this element Data type Age
valueAnnotation			Annotation	There are no (further) constraints on this element Data type Annotation
valueAttachment			Attachment	There are no (further) constraints on this element Data type Attachment
valueCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data type CodeableConcept
valueCoding			Coding	There are no (further) constraints on this element Data type Coding
valueContactPoint			ContactPoint	There are no (further) constraints on this element Data type ContactPoint
valueCount			Count	There are no (further) constraints on this element Data type Count
valueDistance			Distance	There are no (further) constraints on this element Data type Distance
valueDuration			Duration	There are no (further) constraints on this element Data type Duration
valueHumanName			HumanName	There are no (further) constraints on this element Data type HumanName
valueIdentifier			Identifier	There are no (further) constraints on this element Data type Identifier
valueMoney			Money	There are no (further) constraints on this element Data type Money
valuePeriod			Period	There are no (further) constraints on this element Data type Period
valueQuantity			Quantity	There are no (further) constraints on this element Data type Quantity
valueRange			Range	There are no (further) constraints on this element Data type Range
valueRatio			Ratio	There are no (further) constraints on this element Data type Ratio
valueSampledData			SampledData	There are no (further) constraints on this element Data type SampledData
valueSignature			Signature	There are no (further) constraints on this element Data type Signature
valueTiming			Timing	There are no (further) constraints on this element Data type Timing
valueMeta			Meta	There are no (further) constraints on this element Data type Meta
valueReference			Reference()	There are no (further) constraints on this element Data type Reference()
value		0..1		There are no (further) constraints on this element Element id Patient.address.line.value Short description Primitive value for string Definition The actual value Maximum string length 1048576
city	Σ	0..1	string	There are no (further) constraints on this element Element id Patient.address.city Short description Name of city, town etc. Alternate names Municpality, Municipality, woonplaats Definition The name of the city, town, village or other community or delivery center. Requirements Basisregistratie Persoonsgegevens 11.70 Woonplaatsnaam Data type string Examples General Erewhon Example city Den Haag Mappings v2: XAD.3 rim: AD.part[parttype = CTY] vcard: locality servd: ./Jurisdiction hcim-address-v2.0.1-2015EN: NL-CM:0.1.14 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.14 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.3 BRP: 11.70
district	Σ	0..1	string	There are no (further) constraints on this element Element id Patient.address.district Short description District name (aka county) Alternate names County, Gemeente Definition The name of the administrative area (county). Requirements Basisregistratie Persoonsgegevens 09.10 Gemeente van inschrijving Comments District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead. In a Dutch address this element is used for the population of a "gemeente" Data type string Examples General Madison Example district Wateringen Mappings v2: XAD.9 rim: AD.part[parttype = CNT \| CPA] hcim-address-v2.0.1-2015EN: NL-CM:0.1.16 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.16 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.4 BRP: 09.10
state	Σ	0..1	string	There are no (further) constraints on this element Element id Patient.address.state Short description Sub-unit of country (abbreviations ok). Alternate names Province, Territory, Provincie Definition Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes). For Dutch addresses this element should contain the "provincie" code Requirements Some (Dutch) cities have the same name in multiple provinces. Dutch examples include Bergen (Noord-Holland / Limburg) and Geesteren (Gelderland / Overijssel). Data type string Examples Example province ZH Mappings v2: XAD.4 rim: AD.part[parttype = STA] vcard: region servd: ./Region
postalCode	Σ I	0..1	string	There are no (further) constraints on this element Element id Patient.address.postalCode Short description Postal code for area Alternate names Zip, Postcode Definition A postal code designating a region defined by the postal service. Comments Dutch postal codes have pattern '\d{4}[A-Z]{2}' so they do not have spaces. Systems can easily render postal codes with a space if necessary. Data type string Constraints nl-postal-code-pattern: Dutch postal code pattern 'nnnnAA' `(country in 'nl' \| 'nld' \| 'nederland').not() or matches('^\\d{4}[A-Z]{2}$')` Examples General 9132 Example postcode 9132AG Mappings v2: XAD.5 rim: AD.part[parttype = ZIP] vcard: code servd: ./PostalIdentificationCode hcim-address-v2.0.1-2015EN: NL-CM:0.1.15 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.15 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.6 BRP: 11.60
country	Σ	0..1	string	There are no (further) constraints on this element Element id Patient.address.country Short description Country (can be ISO 3166 3 letter code) Alternate names land Definition A country (code) for the address. Comments The FHIR datatype does not properly support coding the country using a CodeableConcept or Coding datatype. If the sender supports coded countries, it SHALL send the coded value using the code-specification extension under Address.country. Data type string Examples Example country NLD Mappings v2: XAD.6 rim: AD.part[parttype = CNT] vcard: country servd: ./Country hcim-address-v2.0.1-2015EN: NL-CM:0.1.17 hcim-addressinformation-v3.0-2016EN: NL-CM:0.1.17 hcim-addressinformation-v1.0-2017EN: NL-CM:20.5.5
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.country.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references) Data type string
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.country.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value)
countryCode	I	0..1	Extension(CodeableConcept)	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode Short description CountryGBACode \| CountryISOCode Alternate names extensions, user content, 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. Definition Defines a more specific coded value for a code or string. Especially useful for FHIR's required ValueSets. These extensions are primarily used on codes bound to a required value set, where you would like to use a more specific code than the codes in the bounded value set. 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. Data type Extension(CodeableConcept) Extension URL http://nictiz.nl/fhir/StructureDefinition/code-specification Constraints 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()` Mappings rim: n/a rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://nictiz.nl/fhir/StructureDefinition/code-specification Mappings rim: N/A
valueCodeableConcept		1..1	CodeableConcept	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.value[x]:valueCodeableConcept Short description CountryGBACode \| CountryISOCode Alternate names LandGBACodelijst, LandISOCodelijst 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). Data type CodeableConcept Mappings rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.value[x]:valueCodeableConcept.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.value[x]:valueCodeableConcept.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
coding	Σ	1..*	Coding	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.value[x]:valueCodeableConcept.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. 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. Data type Coding Sliced: Unordered, Open, by $this(Pattern) Mappings v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
countryGBACodelist	Σ	0..*	CodingBindingPattern	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.value[x]:valueCodeableConcept.coding:countryGBACodelist Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. 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. Data type Coding Binding LandGBACodelijst LandGBACodelijst (extensible) Pattern { "system": "urn:oid:2.16.840.1.113883.2.4.4.16.34" } Mappings v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
countryISOCodelist	Σ	0..*	CodingBindingPattern	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.value[x]:valueCodeableConcept.coding:countryISOCodelist Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. 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. Data type Coding Binding LandISOCodelijst LandISOCodelijst (extensible) Pattern { "system": "urn:iso:std:iso:3166" } Mappings v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
text	Σ	0..1	string	There are no (further) constraints on this element Element id Patient.address.country.extension:countryCode.value[x]:valueCodeableConcept.text Short description Plain text representation of the concept 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. 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. Data type string Mappings v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
value		0..1		There are no (further) constraints on this element Element id Patient.address.country.value Short description Primitive value for string Definition The actual value Maximum string length 1048576
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Patient.address.period Short description Time period when address was/is in use Definition Time period when address was/is in use. Requirements Allows addresses to be placed in historical context. Data type Period Examples General { "start": "2010-03-23", "end": "2010-07-01" } Mappings v2: XAD.12 / XAD.13 + XAD.14 rim: ./usablePeriod[type="IVL<TS>"] servd: ./StartDate and ./EndDate
maritalStatus		0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Patient.maritalStatus Short description Marital (civil) status of a patient Definition This field contains a patient's most recent marital (civil) status. Requirements Most, if not all systems capture it. Data type CodeableConcept Binding The domestic partnership status of a person. Marital Status Codes (extensible) Mappings v2: PID-16 rim: player[classCode=PSN]/maritalStatusCode cda: .patient.maritalStatusCode
multipleBirth[x]		0..1		There are no (further) constraints on this element Element id Patient.multipleBirth[x] Short description Whether patient is part of a multiple birth Definition Indicates whether the patient is part of a multiple (bool) or indicates the actual birth order (integer). Requirements For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs. 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). Mappings v2: PID-24 (bool), PID-25 (integer) rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/multipleBirthInd, player[classCode=PSN\|ANM and determinerCode=INSTANCE]/multipleBirthOrderNumber cda: n/a
multipleBirthBoolean			boolean	There are no (further) constraints on this element Data type boolean
multipleBirthInteger			integer	There are no (further) constraints on this element Data type integer
photo		0..*	Attachment	There are no (further) constraints on this element Element id Patient.photo Short description Image of the patient Definition Image of the patient. Requirements Many EHR systems have the capability to capture an image of the patient. Fits with newer social media usage too. Data type Attachment Mappings v2: OBX-5 - needs a profile rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/desc cda: n/a
contact	I	0..*	BackboneElement	There are no (further) constraints on this element Element id Patient.contact Short description A contact party (e.g. guardian, partner, friend) for the patient Definition A contact party (e.g. guardian, partner, friend) for the patient. Requirements Need to track people you can contact about the patient. 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. Data type BackboneElement Constraints 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()` Mappings rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/scopedRole[classCode=CON] cda: n/a
id		0..1	string	There are no (further) constraints on this element Element id Patient.contact.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.contact.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Patient.contact.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
relationship		0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Patient.contact.relationship Short description The kind of relationship Definition The nature of the relationship between the patient and the contact person. Requirements Used to determine which contact person is the most relevant to approach, depending on circumstances. Data type CodeableConcept Binding The nature of the relationship between a patient and a contact person for that patient. v2 Contact Role (extensible) Mappings v2: NK1-7, NK1-3 rim: code cda: n/a
name		0..1	HumanName	There are no (further) constraints on this element Element id Patient.contact.name Short description A name associated with the contact person Definition A name associated with the contact person. Requirements Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person. Data type HumanName Mappings v2: NK1-2 rim: name cda: n/a
telecom		0..*	ContactPoint	There are no (further) constraints on this element Element id Patient.contact.telecom Short description A contact detail for the person Definition A contact detail for the person, e.g. a telephone number or an email address. Requirements People have (primary) ways to contact them in some way such as phone, email. Comments Contact 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. Data type ContactPoint Mappings v2: NK1-5, NK1-6, NK1-40 rim: telecom cda: n/a
address		0..1	Address	There are no (further) constraints on this element Element id Patient.contact.address Short description Address for the contact person Definition Address for the contact person. Requirements Need to keep track where the contact person can be contacted per postal mail or visited. Data type Address Mappings v2: NK1-4 rim: addr cda: n/a
gender		0..1	codeBinding	There are no (further) constraints on this element Element id Patient.contact.gender Short description male \| female \| other \| unknown Definition Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes. Requirements Needed to address the person correctly. Data type code Binding The gender of a person used for administrative purposes. AdministrativeGender (required) Mappings v2: NK1-15 rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/administrativeGender cda: n/a
organization	I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Patient.contact.organization Short description Organization that is associated with the contact Definition Organization on behalf of which the contact is acting or for which the contact is working. Requirements For guardians or business related contacts, the organization is relevant. Data type Reference(Organization) Mappings v2: NK1-13, NK1-30, NK1-31, NK1-32, NK1-41 rim: scoper cda: n/a
period		0..1	Period	There are no (further) constraints on this element Element id Patient.contact.period Short description The period during which this contact person or organization is valid to be contacted relating to this patient Definition The period during which this contact person or organization is valid to be contacted relating to this patient. Data type Period Mappings rim: effectiveTime cda: n/a
animal	Σ ?!	0..0	BackboneElement	There are no (further) constraints on this element Element id Patient.animal Short description This patient is known to be an animal (non-human) Definition This patient is known to be an animal. 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). Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: player[classCode=ANM] cda: n/a
communication		0..*	BackboneElement	There are no (further) constraints on this element Element id Patient.communication Short description A list of Languages which may be used to communicate with the patient about his or her health Definition Languages which may be used to communicate with the patient about his or her health. 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. 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. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: LanguageCommunication cda: patient.languageCommunication
id		0..1	string	There are no (further) constraints on this element Element id Patient.communication.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.communication.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Patient.communication.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
language		1..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Patient.communication.language Short description The language which can be used to communicate with the patient about his or her health Definition 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. Requirements Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. Comments The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type. Data type CodeableConcept Binding A human language. Common Languages (extensible) Mappings v2: PID-15, LAN-2 rim: player[classCode=PSN\|ANM and determinerCode=INSTANCE]/languageCommunication/code cda: .languageCode
preferred		0..1	boolean	There are no (further) constraints on this element Element id Patient.communication.preferred Short description Language preference indicator Definition Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). 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. Data type boolean Mappings v2: PID-15 rim: preferenceInd cda: .preferenceInd
generalPractitioner		0..*	Reference(Organization \| Practitioner)	There are no (further) constraints on this element Element id Patient.generalPractitioner Short description Patient's nominated primary care provider Alternate names careProvider Definition Patient's nominated care provider. 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. Data type Reference(Organization \| Practitioner) Mappings v2: PD1-4 rim: subjectOf.CareEvent.performer.AssignedEntity cda: n/a
managingOrganization	Σ	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Patient.managingOrganization Short description Organization that is the custodian of the patient record Definition Organization that is the custodian of the patient record. 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). Data type Reference(Organization) Mappings rim: scoper cda: .providerOrganization
link	Σ ?!	0..*	BackboneElement	There are no (further) constraints on this element Element id Patient.link Short description Link to another patient resource that concerns the same actual person Definition Link to another patient resource that concerns the same actual patient. Requirements There are multiple usecases: Duplicate patient records due to the clerical errors associated with the difficulties of identifying humans consistently, and * Distribution of patient information across multiple servers. 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'. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: outboundLink cda: n/a
id		0..1	string	There are no (further) constraints on this element Element id Patient.link.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Patient.link.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Patient.link.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
other	Σ	1..1	Reference(Patient \| RelatedPerson)	There are no (further) constraints on this element Element id Patient.link.other Short description The other patient or related person resource that the link refers to Definition The other patient resource that the link refers to. Comments Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual. Data type Reference(Patient \| RelatedPerson) Mappings v2: PID-3, MRG-1 rim: id cda: n/a
type	Σ	1..1	codeBinding	There are no (further) constraints on this element Element id Patient.link.type Short description replaced-by \| replaces \| refer \| seealso - type of link Definition The type of link between this patient resource and another patient resource. Data type code Binding The type of link between this patient resource and another patient resource. LinkType (required) Mappings rim: typeCode cda: n/a

Documentation:

https://simplifier.net/zorgdomein/zd-patient

Last updated on 12/9/2020, 3:37:47 PM

Confirmation

ZD Patient

About

Information

Follow us

Links