| TEMPLATE ID | UseCaseC_Person |
|---|---|
| Concept | UseCaseC_Person |
| Description | Zur Darstellung von einer Person und ihren demografischen Merkmalen. |
| Use | Zur Repräsentation von demografischen Daten und anderen administrativen Informationen zu einer Person, die im Kontext einer Gesundheitseinrichtung relevant sein können. Das Template PERSON ist explizit für PATIENTEN modelliert und zum Zwecke der Führung eines standortübergreifenden Master Patient Index auf der Basis von identifizierenden Daten (IDAT) vorgesehen. |
| Misuse | Nicht in anderen Kontexten außer Gesundheitseinrichtung verwenden. Nicht für die Repräsentation von pseudonymisierten / anonymisierten Patienten verwenden. |
| Purpose | Zur Darstellung von einer Person und ihren demografischen Merkmalen. |
| References | |
| Authors | date: 2020-09-17; name: Louisa Bode; organisation: Medizinische Hochschule Hannover; email: bode.louisa@mh-hannover.de |
| Other Details Language | date: 2020-09-17; name: Louisa Bode; organisation: Medizinische Hochschule Hannover; email: bode.louisa@mh-hannover.de |
| Other Details (Language Independent) |
|
| Keywords | Personendaten; Demografie; Patient; Identifikation; Personenname; Geburtsname; Kontaktdaten |
| Language used | en |
| Citeable Identifier | 1246.169.2751 |
| Root archetype id | openEHR-EHR-COMPOSITION.person.v0 |
| Person | Person: Dokument zur Übermittlung von Informationen über Personen |
| Other Context | |
| Patient ID | Patient ID: ID der Person |
| Gender | Gender: Details about the gender of an individual. |
| Data | |
| Administrative gender | Administrative gender: The gender of an individual used for administrative purposes. This element is what most systems today describes as 'Sex' or 'Gender'. For example 'Male', 'Female', 'Other'. This aligns with HL7 FHIR 'Person.gender'. Coding with a terminology is recommended, where possible. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/administrative-gender |
| Anderes Geschlecht amtlich | Anderes Geschlecht amtlich: Additional narrative about the individual's gender not captured in other data elements. Terminology: http://fhir.de/ValueSet/gender-other-de
|
| Personendaten | Personendaten: Demografische Daten zu einer Person wie Geburtsdatum und Telefonnummer. |
| Data | |
| Person | Person: An individual human being. |
| Name | Name: Discrete components of an individual's name. |
| Namensart | Namensart: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/name-use |
| Vollständiger Name | Vollständiger Name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Vorname | Vorname: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Familienname | Familienname: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Familienname-Namenszusatz | Familienname-Namenszusatz: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Familienname-Nachname | Familienname-Nachname: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Familienname-Vorsatzwort | Familienname-Vorsatzwort: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Prefix | Prefix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'. |
| Geburtsname | Geburtsname: Discrete components of an individual's name. |
| Namensart | Namensart: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/name-use |
| Vollständiger Name | Vollständiger Name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Familienname | Familienname: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Familienname-Namenszusatz | Familienname-Namenszusatz: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Familienname-Nachname | Familienname-Nachname: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Familienname-Vorsatzwort | Familienname-Vorsatzwort: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'. |
| Versicherten ID_GKV | Versicherten ID_GKV: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| PID | PID: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Versicherungsnummer PKV | Versicherungsnummer PKV: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Straßenanschrift | Straßenanschrift: Details about the location of a person, physical building or landmark. |
| Straße | Straße: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Hausnummer | Hausnummer: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Adresszusatz | Adresszusatz: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Stadtteil | Stadtteil: The name of the suburb, town, city, village, community or lowest level locality that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. |
| Stadt | Stadt: The name of the suburb, town, city, village, community or lowest level locality that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. |
| Gemeindeschlüssel | Gemeindeschlüssel: The name of the suburb, town, city, village, community or lowest level locality that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. |
| Bundesland | Bundesland: The name of a major government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'New South Wales' and 'Queensland' in Australia; 'British Columbia' and 'Nova Scotia' in Canada; and the Counties of 'Cornwall', 'Middlesex' & 'Surrey' in Jamaica. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://fhir.de/ValueSet/iso/bundeslaender |
| Postal code | Postal code: The code for a postal delivery area containing the address, as defined by the relevant postal delivery service. Also known as a postcode or ZIP code. |
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/iso3166-1-2 |
| Type | Type: The type of address. For example: physical or postal.
|
| Use | Use: The primary purpose or use for the address. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/address-use
|
| Comment | Comment: Additional narrative about the address not captured in other fields. |
| Postfach | Postfach: Details about the location of a person, physical building or landmark. |
| Postfach | Postfach: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Stadtteil | Stadtteil: The name of the suburb, town, city, village, community or lowest level locality that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. |
| Stadt | Stadt: The name of the suburb, town, city, village, community or lowest level locality that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. |
| Gemeindeschlüssel | Gemeindeschlüssel: The name of the suburb, town, city, village, community or lowest level locality that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. |
| Bundesland | Bundesland: The name of a major government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'New South Wales' and 'Queensland' in Australia; 'British Columbia' and 'Nova Scotia' in Canada; and the Counties of 'Cornwall', 'Middlesex' & 'Surrey' in Jamaica. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://fhir.de/ValueSet/iso/bundeslaender |
| Postal code | Postal code: The code for a postal delivery area containing the address, as defined by the relevant postal delivery service. Also known as a postcode or ZIP code. |
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/iso3166-1-2 |
| Type | Type: The type of address. For example: physical or postal.
|
| Use | Use: The primary purpose or use for the address. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/address-use
|
| Comment | Comment: Additional narrative about the address not captured in other fields. |
| Verwaltungsorganisation | Verwaltungsorganisation: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name | Name: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Identifier | Identifier: Identifier associated with the organisation. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the ID data type contains multiple subcomponents for recording the ID value, type, issuer and assigner.
|
| Birth data | Birth data: Birth demographic data |
| Birth date | Birth date: The date of birth of a person |
| Angaben zum Tod | Angaben zum Tod: * |
| Verstorben? | Verstorben?: * |
| Angaben zum Tod | Angaben zum Tod: Angaben über den Tod einer Person, die mit übergeordneten Datenelementen für die Registrierung übereinstimmen zB. Sterberegister. |
| Sterbedatum | Sterbedatum: Der Zeitpunkt, an dem die Person verstorben ist. |
| Todesdiagnose | Todesdiagnose: Die Ursache, welche zum Tode geführt hat. Die Todesursache sollte, wenn möglich, mit einer Terminologie kodiert werden. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://fhir.de/ValueSet/bfarm/icd-10-gm |
| Kontaktperson | Kontaktperson: An individual human being. |
| Name | Name: The unstructured name for the individual. The content of this data element may be derived from one or more components from CLUSTER.structured_name combined together as a text string. For example: 'John Markham', 'Professor Sir John Markham', 'John Markham Jnr MP'. |
| Rolle (Relationship) | Rolle (Relationship): The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. Value set: terminology://fhir.hl7.org//ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/patient-contactrelationship |
| Address | Address: Details about the location of a person, physical building or landmark. |
| Address line | Address line: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Electronic communication | Electronic communication: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template.
|
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
|
| Organisation | Organisation: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name | Name: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Identifier | Identifier: Identifier associated with the organisation. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the ID data type contains multiple subcomponents for recording the ID value, type, issuer and assigner.
|
| Role | Role: The relationship or role of the organisation to the individual or subject of care. For example: oncologist; palliative care home nursing service; or informal support network. |
| Comment | Comment: Additional narrative about the organisation not captured in other fields. |
| Comment | Comment: Additional narrative about the individual not captured in other fields. |
| Other contributors | Samer Alkarkoukly, University Hospital Cologne, mabbouda@uni-koeln.de |