Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.

Whereas the zib ContactPerson includes all (non-healthcare professional) persons that are involved in the care for a patient, FHIR distinguishes two use cases for these persons:

• The RelatedPerson resource, and therefore this profile, is used to capture information about any person that is related to the patient.
• Information about persons that should be contacted regarding the care for the patient is captured using the Patient.contact resource.

If a person is both a related person and a contact person, then some data duplication is inevitable.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

An Extension

Defines the author of the resource.

Part of the authorisation model. Upon creation of the resource this extension is set to the device that created it.

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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifier for a person within a particular scope.

People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.

Whether this related person record is in active use.

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

Need to be able to mark a related person record as not to be used, such as if it was created in error.

The patient this person is related to.

We need to know which patient this RelatedPerson is related to.

The nature of the relationship between a patient and the related person.

See Koppeltaal Implementation Guide for more information on the ValueSet

The nature of the relationship between a patient and the related person.

We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.

Defines the role of the contact in relation to the patient.

When using the display element for COD472 codes 23 (Contactpersoon) and 24 (Wettelijke vertegenwoordiger), you MUST use the exact content of the display element from the CodeSystem. Otherwise, validation will result in errors. These specific codes require strict display validation due to known inconsistencies between different code systems and ValueSets. Other COD472 codes do not enforce display validation. Note that the display of the code in the ValueSet can be different from the CodeSystem.

The nature of the relationship between a patient and the related person.

We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.

Defines the contact’s familial relationship to the patient.

The nature of the relationship between a patient and the related person.

We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.

Full name of the contact.

Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.

This slice represents the person's official name information, including given names, last name and possibly the partner's last name.

This .name element represents a Dutch name according to the zib NameInformation (v1.1, 2020) (except for the GivenName concept). A Dutch name is represented in FHIR as an ordinary international name, but is augmented using extensions to specify how the last name is built up according to the Dutch rules. See the guidance on .family and on .extension:nameUsage for more information. Systems that need to work in a Dutch context MUST support these extensions as specified here. In addition, systems MUST use the core elements according to the FHIR specifications to provide compatibility outside Dutch contexts. It is encouraged to provide a representation of the full name in the .text element.

Note 1: The zib cannot be represented straightforward in FHIR. Especially note the guidance on .given on how to map the FirstNames and Initials concepts, and on .prefix/.suffix on how to map the Titles concept.

Note 2: This element should only contain a person's official names. The GivenName concept is represented in another .name element with .name.use = usual.

Note 3: The examples illustrate how the zib is mapped to FHIR.

Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.

This slice represents the name information normally used to address the person.

This .name element represents the Dutch given name ("roepnaam") according to the zib NameInformation v1.1 (2020).

Note 1: This element should only contain a person's unofficial name. The official names are represented in one or more other .name elements with .name.use = official.

Note 2: The examples illustrate how the zib is mapped to FHIR.

Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.

The contact’s telephone number and/or e-mail address.

The cardinality mismatch between the zib (0..1) and FHIR (0..*) is explained by the containers TelephoneNumbers (0..*) and EmailAddresses (0..*) inside the ContactInformation model. The FHIR datatype ContactPoint does not have these containers.

People have (primary) ways to contact them in some way such as phone, email.

Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.

Implementation of the "TelephoneNumbers" concept of zib ContactInformation.

Please note that, although the zib concepts TelecomType and NumberType are functionally equivalent to the FHIR concepts ContactPoint.system and ContactPoint.use respectively, a mismatch occurs on the concept of mobile phone numbers; the zib uses the first concept and FHIR the second. For this reason, the ValueSet on ContactPoint.system is too narrow and the zib code will need to be communicated using the ext-CodeSpecification extension.

People have (primary) ways to contact them in some way such as phone, email.

Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.

Implementation of the "EmailAddresses" concept of zib ContactInformation.

People have (primary) ways to contact them in some way such as phone, email.

Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.

The gender of a person used for administrative purposes.

Needed for identification of the person, in combination with (at least) name and birth date.

The date on which the related person was born.

Image of the person.

Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too.

See Koppeltaal Implementation Guide for more information on the ValueSet

When using the display element for COD472 codes 23 (Contactpersoon) and 24 (Wettelijke vertegenwoordiger), you MUST use the exact content of the display element from the CodeSystem. Otherwise, validation will result in errors. These specific codes require strict display validation due to known inconsistencies between different code systems and ValueSets. Other COD472 codes do not enforce display validation. Note that the display of the code in the ValueSet can be different from the CodeSystem.

This .name element represents a Dutch name according to the zib NameInformation (v1.1, 2020) (except for the GivenName concept). A Dutch name is represented in FHIR as an ordinary international name, but is augmented using extensions to specify how the last name is built up according to the Dutch rules. See the guidance on .family and on .extension:nameUsage for more information. Systems that need to work in a Dutch context MUST support these extensions as specified here. In addition, systems MUST use the core elements according to the FHIR specifications to provide compatibility outside Dutch contexts. It is encouraged to provide a representation of the full name in the .text element.

Note 1: The zib cannot be represented straightforward in FHIR. Especially note the guidance on .given on how to map the FirstNames and Initials concepts, and on .prefix/.suffix on how to map the Titles concept.

Note 2: This element should only contain a person's official names. The GivenName concept is represented in another .name element with .name.use = usual.

Note 3: The examples illustrate how the zib is mapped to FHIR.

Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.

Whereas the zib ContactPerson includes all (non-healthcare professional) persons that are involved in the care for a patient, FHIR distinguishes two use cases for these persons:

• The RelatedPerson resource, and therefore this profile, is used to capture information about any person that is related to the patient.
• Information about persons that should be contacted regarding the care for the patient is captured using the Patient.contact resource.

If a person is both a related person and a contact person, then some data duplication is inevitable.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

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).

A human language.

A human-readable narrative that contains a summary of the resource and can 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.

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 information is added later.

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.

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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

An Extension

Defines the author of the resource.

Part of the authorisation model. Upon creation of the resource this extension is set to the device that created it.

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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifier for a person within a particular scope.

People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.

Whether this related person record is in active use.

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

Need to be able to mark a related person record as not to be used, such as if it was created in error.

The patient this person is related to.

We need to know which patient this RelatedPerson is related to.

The nature of the relationship between a patient and the related person.

See Koppeltaal Implementation Guide for more information on the ValueSet

The nature of the relationship between a patient and the related person.

We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.

Defines the role of the contact in relation to the patient.

When using the display element for COD472 codes 23 (Contactpersoon) and 24 (Wettelijke vertegenwoordiger), you MUST use the exact content of the display element from the CodeSystem. Otherwise, validation will result in errors. These specific codes require strict display validation due to known inconsistencies between different code systems and ValueSets. Other COD472 codes do not enforce display validation. Note that the display of the code in the ValueSet can be different from the CodeSystem.

The nature of the relationship between a patient and the related person.

We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.

Defines the contact’s familial relationship to the patient.

The nature of the relationship between a patient and the related person.

We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.

Full name of the contact.

Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.

This slice represents the person's official name information, including given names, last name and possibly the partner's last name.

This .name element represents a Dutch name according to the zib NameInformation (v1.1, 2020) (except for the GivenName concept). A Dutch name is represented in FHIR as an ordinary international name, but is augmented using extensions to specify how the last name is built up according to the Dutch rules. See the guidance on .family and on .extension:nameUsage for more information. Systems that need to work in a Dutch context MUST support these extensions as specified here. In addition, systems MUST use the core elements according to the FHIR specifications to provide compatibility outside Dutch contexts. It is encouraged to provide a representation of the full name in the .text element.

Note 1: The zib cannot be represented straightforward in FHIR. Especially note the guidance on .given on how to map the FirstNames and Initials concepts, and on .prefix/.suffix on how to map the Titles concept.

Note 2: This element should only contain a person's official names. The GivenName concept is represented in another .name element with .name.use = usual.

Note 3: The examples illustrate how the zib is mapped to FHIR.

Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.

This slice represents the name information normally used to address the person.

This .name element represents the Dutch given name ("roepnaam") according to the zib NameInformation v1.1 (2020).

Note 1: This element should only contain a person's unofficial name. The official names are represented in one or more other .name elements with .name.use = official.

Note 2: The examples illustrate how the zib is mapped to FHIR.

Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.

The contact’s telephone number and/or e-mail address.

The cardinality mismatch between the zib (0..1) and FHIR (0..*) is explained by the containers TelephoneNumbers (0..*) and EmailAddresses (0..*) inside the ContactInformation model. The FHIR datatype ContactPoint does not have these containers.

People have (primary) ways to contact them in some way such as phone, email.

Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.

Implementation of the "TelephoneNumbers" concept of zib ContactInformation.

Please note that, although the zib concepts TelecomType and NumberType are functionally equivalent to the FHIR concepts ContactPoint.system and ContactPoint.use respectively, a mismatch occurs on the concept of mobile phone numbers; the zib uses the first concept and FHIR the second. For this reason, the ValueSet on ContactPoint.system is too narrow and the zib code will need to be communicated using the ext-CodeSpecification extension.

People have (primary) ways to contact them in some way such as phone, email.

Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.

Implementation of the "EmailAddresses" concept of zib ContactInformation.

People have (primary) ways to contact them in some way such as phone, email.

Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.

The gender of a person used for administrative purposes.

Needed for identification of the person, in combination with (at least) name and birth date.

The date on which the related person was born.

An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world.

This datatype defines a common basis for expressing all addresses around the world, but adds extensions to express Dutch addresses specifically, according to the zib AddressInformation v1.1 (2020). 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 zib 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 zib 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 code from the zib should also be included using the extension on Address.extension:addressType.

If Address.type is both then this is to be understood as a dual purpose address (postal and physical), unless a specific postal type address is added. 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 zib ValueSet. Therefore, a custom extension has been made. This doesn't preclude the use of the AD-use extension.

Need to keep track where the related person can be contacted per postal mail or visited.

Image of the person.

Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too.

The period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown.

A language which may be used to communicate with about the patient's health.

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 RelatedPerson.Communication associations. If the RelatedPerson does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.

If a related person 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.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

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.

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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

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.

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.

A human language.

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.

Indicates whether or not the patient prefers this language (over other languages he masters up a certain level).

This language is specifically identified for communicating healthcare information.

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.