| TEMPLATE ID | Person - JM Clinician |
|---|---|
| Concept | Person - JM Clinician |
| Description | Not Specified |
| Purpose | Not Specified |
| References | |
| Authors | date: 2022-11-28 |
| Other Details Language | date: 2022-11-28 |
| Other Details (Language Independent) |
|
| Language used | en |
| Citeable Identifier | 1013.26.921 |
| Root archetype id | openEHR-EHR-CLUSTER.person.v1 |
| Person - clinician | Person - clinician: An individual human being. |
| Structured name of a person - core | Structured name of a person - core: Discrete components of an individual's name. |
| Title | Title: 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'.
|
| First name | First 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. |
| Last name | Last name: 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)'.
|
| Professional license number | Professional license number: 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. |
| Professional group | Professional group: 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. |
| Position | Position: 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. |
| 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'. |