Generated Narrative: StructureDefinition ACP-ContactPerson Name Flags Card. Type Description & Constraints RelatedPerson 0..* nl-core-relatedperson(2.0.5) An person that is related to a patient, but who is not a direct target of care #xD; Slices for extension Content/Rules for all slices #xD; extension:role 0..* nl core relatedperson role(2.0.1) Optional Extensions Element #xD; patient 1..1 Reference(Patient(1.0.0-alpha1)) The patient this person is related to #xD; relationship 0..1 CodeableConcept Relationship #xD; name 0..* nl-core-humanname(2.0.10) NameInformation #xD; use 0..1 code usual | official | temp | nickname | anonymous | old | maiden #xD; family #xD; Slices for extension Content/Rules for all slices #xD; extension:humannameOwnPrefix 0..1 own-prefix Voorvoegsel derived from person's own surname #xD; extension:humannameOwnName 0..1 own-name Portion derived from person's own surname #xD; extension:humannamePartnerPrefix 0..1 partner-prefix Voorvoegsel derived from person's partner's surname #xD; extension:humannamePartnerName 0..1 partner-name Portion derived from person's partner's surname #xD; given 0..* string Given #xD; telecom 0..* nl-core-contactpoint(2.0.8) A contact detail for the person #xD; Slices for extension Content/Rules for all slices #xD; extension:TelecomType 0..1 Zib ContactInformation TelecomType(1.0.1) Provides the specific HCIM code for TelecomType #xD; system 1..1 code TelecomType / EmailAddressType #xD; value 0..1 string TelephoneNumber / EmailAddress #xD; use 0..1 code TelecomType / NumberType / EmailAddressType #xD; address 0..* nl-core-address(3.0.6) AddressInformation #xD; Documentation for this format
A person not being a healthcare professional who is involved in the patient’s care, such as family members, caregivers, mental caretakers, guardians and legal representatives. Based on nl-core-ContactPerson and HCIM ContactPerson.
Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.
ContactInformation has become an independent information model as of release 2017 of the HCIMs.
ContactInformation has become an independent information model as of release 2017 of the HCIMs
An person that is related to a patient, but who is not a direct target of care
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
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()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
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()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
Wettelijk vertegenwoordiger (Contactpersoon)
Gesprek gevoerd in bijzijn van (Contactpersoon)
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 may not always be associated with version changes to the resource.
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
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.
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).
Text summary of the resource, for human interpretation
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.
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.
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.
Optional Extension Element - found in all resources.
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional Content defined by implementations
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.
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.
Source of the definition for the extension code - a logical name or a URL.
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.
Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).
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.
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's record is in active use
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.
We need to know which patient this RelatedPerson is related to.
scoper[classCode=PSN|ANM and determinerCode='INSTANCE']/playedRole[classCode='PAT']/id
When someone is or **will be** a legal representative, then a relationship code `24` from code system _urn:oid:2.16.840.1.113883.2.4.3.11.22.472_ is added.
We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.
Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.
Naam wettelijk vertegenwoordiger (Naamgegevens)
A code that represents the preferred display order of the components of this human name.
NameUsage. Use FHIR Core ConceptMap for HCIM mapping: http://nictiz.nl/fhir/ConceptMap/NaamgebruikCodelijst-to-HumanNameAssemblyOrder
A code that represents the preferred display order of the components of a human name
usual | official | temp | nickname | anonymous | old | maiden
This is labeled as "Is Modifier" because applications should not mistake a temporary or old name etc.for a current/permanent one. Applications can assume that a name is current unless it explicitly says that it is temporary or old.
Allows the appropriate name for a particular context of use to be selected from among a set of names.
XPN.7, but often indicated by which field contains the name
Can provide both a text representation and structured parts.
The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father.
Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).
unique id for the element within a resource (for internal references)
Voorvoegsel derived from person's own surname
The prefix portion (e.g. voorvoegsel) of the family name that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse.
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
Portion derived from person's own surname
The portion of the family name that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse.
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
Voorvoegsel derived from person's partner's surname
The prefix portion (e.g. voorvoegsel) of the family name that is derived from the person's partner's surname, as distinguished from any portion that is derived from the surname of the person's own.
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to identify it as a separate sub-component.
Portion derived from person's partner's surname
The portion of the family name that is derived from the person's partner's surname, as distinguished from any portion that is derived from the surname of the person's own name.
Note that in order to mark the type of a given name, the FHIR standard extension for ISO 21090 EN Qualifiers is to be used. Examples include call me name (Dutch: roepnaam) and initials. Each initial is expected to be delimited by a dot.
Note that in order to mark the type of a given name, the FHIR standard extension for ISO 21090 EN Qualifiers is to be used. Examples include call me name (Dutch: roepnaam) and initials. Each initial is expected to be delimited by a dot. To be conformant to the HCIM for NameInformation, at least the following qualifiers SHALL be supported: _BR_, _IN_ and _CL_. The qualifier _BR_ maps to the HCIM concept FirstNames, _IN_ maps to Initials and _CL_ to GivenName. Please see the compatibility note on the containing element as well!
Given Names appear in the correct order for presenting the name
LS | AC | NB | PR | HON | BR | AD | SP | MID | CL | IN | VV
A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type.
Used to indicate additional information about the name part and how it should be used.
A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.
Prefixes appear in the correct order for presenting the name
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.
Suffixes appear in the correct order for presenting the name
Indicates the period of time when this name was valid for the named person.
Allows names to be placed in historical context.
A contact detail for the person, e.g. a telephone number or an email address.
Person 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.
People have (primary) ways to contact them in some way such as phone, email.
Contactgegevens wettelijk vertegenwoordiger (Contactgegevens)
Provides the specific HCIM code for TelecomType
Defines a more specific coded value for the concept TelecomType used in HCIM ContactInformation, to be able to use the required HCIM value set.
Definieert een specifieke gecodeerde waarde voor het concept TelecomType gebruikt in de zib Contactgegevens, zodat de in de zib gedefinieerde waardelijst kan worden gebruikt.
TelecomType. A ConceptMap (http://nictiz.nl/fhir/ConceptMap/TelecomTypeCodelijst-to-ContactPointSystem) is available that maps TelecomTypeCodelijst to the ContactPointSystem value set.
Telecommunications form for contact point - what communications system is required to make use of the contact.
TelecomType. A ConceptMap (http://nictiz.nl/fhir/ConceptMap/TelecomTypeCodelijst-to-ContactPointSystem) is available that maps TelecomTypeCodelijst to the ContactPointUse value set.
EmailAddressType. A ConceptMap (http://nictiz.nl/fhir/ConceptMap/EmailSoortCodelijst-to-ContactPointSystem) is available that maps EmailSoortCodelijst to the ContactPointUse value set.
The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).
Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
Need to support legacy numbers that are not in a tightly controlled format.
TelecomType / NumberType / EmailAddressType
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.
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.
TelecomType. A ConceptMap (http://nictiz.nl/fhir/ConceptMap/TelecomTypeCodelijst-to-ContactPointUse) is available that maps TelecomTypeCodelijst to the ContactPointUse value set.
NumberType. A ConceptMap (http://nictiz.nl/fhir/ConceptMap/NummerSoortCodelijst-to-ContactPointUse) is available that maps NummerSoortCodelijst to the ContactPointUse value set.
EmailAddressType. A ConceptMap (http://nictiz.nl/fhir/ConceptMap/EmailSoortCodelijst-to-ContactPointUse) is available that maps EmailSoortCodelijst to the ContactPointUse value set.
EmailAddressType. A ConceptMap (http://nictiz.nl/fhir/ConceptMap/EmailSoortCodelijst-to-ContactPointUse) is available that maps EmailSoortCodelijst to the ContactPointUse value set
Specify preferred order of use (1 = highest)
Specifies a preferred order in which to use a set of contacts. Contacts are ranked with lower values coming before higher values.
Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
Time period when the contact point was/is in use
Time period when the contact point was/is in use.
Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.
Needed for identification of the person, in combination with (at least) name and birth date.
The gender of a person used for administrative purposes.
The date on which the related person was born
The date on which the related person was born.
Address where the related person can be contacted or visited.
Need to keep track where the related person can be contacted per postal mail or visited.
Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too.
player[classCode='PSN' and determinerCode='INSTANCE']/desc
Period of time that this relationship is considered valid
The period of time that this relationship is considered to be valid. If there are no dates defined, then the interval is unknown.