TEMPLATE Accidental poisoning case investigation form (Accidental poisoning case investigation form)

TEMPLATE ID	Accidental poisoning case investigation form
Concept	Accidental poisoning case investigation form
Description	Not Specified
Purpose	Not Specified
References
Authors	name: Heather Leslie; organisation: Atomica Informatics; email: heather.leslie@atomicainformatics.com; date: 2023-09-04
Other Details Language	name: Heather Leslie; organisation: Atomica Informatics; email: heather.leslie@atomicainformatics.com; date: 2023-09-04
Other Details (Language Independent)	Sem Ver: 89.0.0 MD5-CAM-1.0.1: b440af10f3f1f3a7e666eb3929b51cb5 PARENT:MD5-CAM-1.0.1: 005501C1FA493A4838F5F1121F2870EC Original Language: ISO_639-1::en
Language used	en
Citeable Identifier	1013.26.988
Root archetype id	openEHR-EHR-COMPOSITION.report.v1
2024 12 29 Accidental poisoning case investigation form	2024 12 29 Accidental poisoning case investigation form: Document to communicate information to others, commonly in response to a request from another party.
Health event investigation metadata	Health event investigation metadata: Health event investigation metadata
Data	Data: *
Notified event	Notified event: The name of the disease under investigation. Accidental poisoning
Notification ID	Notification ID: The unique identifier for the notification that triggered this health event investigation. The investigation ID and the notification ID may be identical if both the notification and investigation are carried out within the same system.
Investigation ID	Investigation ID: The unique identifier for this health event investigation. The investigation ID and the notification ID may be identical if both the notification and investigation are carried out within the same system.
Date of notification	Date of notification: Details about the person who notified public health authorities about the health event.
Person - notifying individual	Person - notifying individual: 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'. Codes from National Data Dictionary
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)'. Codes from National Data Dictionary
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. Contact Investigator Data Entry Clerk Epidemiologist Lab Technician Public Health Inspector Public Health Nurse Medical Doctor Medical Officer of Health Medical Technologist Nurse (not PHN) Surveillance Officer Social Worker
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.
Healthcare facility	Healthcare facility: 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.
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Person - investigating officer	Person - investigating officer: 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'. Codes from National Data Dictionary
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)'. Codes from National Data Dictionary
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'.
Date investigation initiated	Date investigation initiated: The date when the investigator commenced the investigation.
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'. Codes from National Data Dictionary
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)'. Codes from National Data Dictionary
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'.
Healthcare facility	Healthcare facility: 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.
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Date investigation completed	Date investigation completed: The date when the investigator finished the investigation report.
Date submitted for local review/sign-off	Date submitted for local review/sign-off: The date when the investigator submitted the investigation report for review.
Local review details	Local review details: Details about review, sign off or approval by local or regional clinical authorities.
Date received for review	Date received for review: The date when the reviewer received the investigation for review.
Person - public health official	Person - public health official: 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'. Codes from National Data Dictionary
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)'. Codes from National Data Dictionary
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'.
Review type	Review type: Type of review requested. For example: sign-off, ready for submission to national public health authorities
Health region	Health region: Name of the local health region.
Comment	Comment: Narrative description about the investigation report.
Date review completed	Date review completed: The date when the reviewer completed the review of the investigation.
Date review submitted	Date review submitted: The date when the reviewer submitted the investigation report to the next level of review. This data element is redundant if there are no further levels of review required.
Date submitted to national authorities	Date submitted to national authorities: The date on which the investigation was submitted to public health authorities.
Case demographic information	Case demographic information: A generic section header which should be renamed in a template to suit a specific clinical context.
Adult demographics	Adult demographics: A container archetype used to hold demographic-related EHR CLUSTER archetypes.
Data
Person - adult patient	Person - adult patient: An individual human being.
Structured name of a person - full	Structured name of a person - full: 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'. Codes from National Data Dictionary
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.
Middle name	Middle 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.
Nickname	Nickname: 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)'. Codes from National Data Dictionary
Medical Record Number (MRN)	Medical Record Number (MRN): 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.
Jamaica Digital Health ID	Jamaica Digital Health ID: 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.
National Identification Number (NIN)	National Identification Number (NIN): 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.
Taxpayer Registration Number (TRN)	Taxpayer Registration Number (TRN): 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.
Drivers licence	Drivers licence: 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.
Passport number	Passport 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.
Electoral Office of Jamaica ID	Electoral Office of Jamaica ID: 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.
National Insurance Scheme Number	National Insurance Scheme 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.
Address - Local + GIS	Address - Local + GIS: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Geolocation code	Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash.
Latitude	Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° (UCUM: deg)
Longitude	Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° (UCUM: deg)
Map URL	Map URL: Link to a location on an online map. For example: a location on a Google or iOS map.
Phone - personal mobile	Phone - personal mobile: 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. Mobile (cellular) telephone
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Personal use
Phone - home landline	Phone - home landline: 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. Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Personal use
Phone - work number	Phone - work number: 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. Mobile (cellular) telephone Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Business use
Email	Email: 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.
Comment	Comment: Additional narrative about the electronic communication not captured in other fields.
Child demographics	Child demographics: A container archetype used to hold demographic-related EHR CLUSTER archetypes.
Data
Person - child patient	Person - child patient: An individual human being.
Structured name of a person - full	Structured name of a person - full: 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'. Codes from National Data Dictionary
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.
Middle name	Middle 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.
Nickname	Nickname: 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)'. Codes from National Data Dictionary
Medical Record Number (MRN)	Medical Record Number (MRN): 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.
Jamaica Digital Health ID	Jamaica Digital Health ID: 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.
National Identification Number (NIN)	National Identification Number (NIN): 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.
Birth certificate number	Birth certificate 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.
Student Registration Number	Student Registration 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.
Taxpayer Registration Number (TRN)	Taxpayer Registration Number (TRN): 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.
Drivers licence	Drivers licence: 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.
Passport number	Passport 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.
National Insurance Scheme Number	National Insurance Scheme 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.
Address - Local + GIS	Address - Local + GIS: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Geolocation code	Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash.
Latitude	Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° (UCUM: deg)
Longitude	Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° (UCUM: deg)
Map URL	Map URL: Link to a location on an online map. For example: a location on a Google or iOS map.
Phone - home landline	Phone - home landline: 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. Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Personal use
Phone - personal mobile	Phone - personal mobile: 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. Mobile (cellular) telephone
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Personal use
Email	Email: 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.
Comment	Comment: Additional narrative about the electronic communication not captured in other fields.
Person - nameless infant patient	Person - nameless infant patient: An individual human being.
Label	Label: A label for the individual. For example: 'Neighbour in the house with the red door'. Baby of
Structured name of woman - full + maiden	Structured name of woman - full + maiden: 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'. Codes from National Data Dictionary
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.
Middle name	Middle 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.
Nickname	Nickname: 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.
Maiden name	Maiden 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.
Medical Record Number (MRN)	Medical Record Number (MRN): 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.
Jamaica Digital Health ID	Jamaica Digital Health ID: 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.
Address - Local + GIS	Address - Local + GIS: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Geolocation code	Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash.
Latitude	Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° (UCUM: deg)
Longitude	Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° (UCUM: deg)
Map URL	Map URL: Link to a location on an online map. For example: a location on a Google or iOS map.
Phone - home landline	Phone - home landline: 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. Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Personal use
Phone - personal mobile	Phone - personal mobile: 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. Mobile (cellular) telephone
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Personal use
Email	Email: 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.
Comment	Comment: Additional narrative about the electronic communication not captured in other fields.
Date of birth	Date of birth: Overview or summary record of the pregnancy and birth of an individual.
Data
Date of birth	Date of birth: The date/time of birth of the individual. May also be used to record the assumed or agreed date/time of birth for operational purposes, if the actual date/time is not formally recorded. Possible alternatives for the date/time of birth of the individual can be recorded using the CLUSTER.DOB_alternative archetype 'Date of birth details' SLOT. Partial dates are allowed.
Age assertion	Age assertion: A statement about the age of an individual at a point in time.
Data
Point in time event	Point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time.
Data
Chronological age	Chronological age: The age of an individual at the event time, calculated from date of birth. In most use cases the DV_DURATION data type is used to record the Chronological age. The DV_INTERVAL_DURATION is used for recording a structured age interval in cases where there's uncertainty about the individual's exact age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days). The DV_TEXT data type is used for recording a textual representation of the individual's age, or age category often found in questionnaires. For example: 'P3M2W', '0,2884615384615385 a_j', '3 months 2 weeks' or '31-40 years' or 'Teenager'. P1M..P200Y Units: Year Month
Age assertion - infant	Age assertion - infant: A statement about the age of an individual at a point in time.
Data
Point in time event	Point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time.
Data
Chronological age	Chronological age: The age of an individual at the event time, calculated from date of birth. In most use cases the DV_DURATION data type is used to record the Chronological age. The DV_INTERVAL_DURATION is used for recording a structured age interval in cases where there's uncertainty about the individual's exact age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days). The DV_TEXT data type is used for recording a textual representation of the individual's age, or age category often found in questionnaires. For example: 'P3M2W', '0,2884615384615385 a_j', '3 months 2 weeks' or '31-40 years' or 'Teenager'. PT1H..P51W
Sex & gender	Sex & gender: Details about the gender of an individual.
Data
Sex assigned at birth	Sex assigned at birth: The sex of an individual determined by anatomical characteristics observed and registered at birth. For example: 'Male', 'Female', 'Intersex'. Coding with a terminology is recommended, where possible. Use the element 'Comment' or the SLOT 'Details' if needed to register more specific details of the individuals gender. Male Female
Sex & gender - newborn	Sex & gender - newborn: Details about the gender of an individual.
Data
Sex assigned at birth	Sex assigned at birth: The sex of an individual determined by anatomical characteristics observed and registered at birth. For example: 'Male', 'Female', 'Intersex'. Coding with a terminology is recommended, where possible. Use the element 'Comment' or the SLOT 'Details' if needed to register more specific details of the individuals gender. Male Female Indeterminate
Poisoning event summary	Poisoning event summary: Summary details about a single poisoning event, including accidental exposure to a substance at home, in the workplace, or within the broader community or environment, as well as deliberate self-poisoning.
Data
Substance name	Substance name: Name of the substance or agent causally linked with the poisoning.
Date/time of poisoning	Date/time of poisoning: The date and optional time of exposure to the substance or, for exposures extending over a period, the start of the exposure.
Poisoning circumstances	Poisoning circumstances: Narrative description about the poisoning event.
Substance colour	Substance colour: The colour of the substance at the time of exposure.
Substance state	Substance state: The physical form or presentation of the substance at the time of exposure. The state of the substance or agent may be different in its' stored form, for example a liquid that is inhaled as a gas. Gas Aerosol Liquid Solid
Solid state type	Solid state type: Specific type of solid form or presentation of the substance at the time of exposure. Tablet Capsule Pellet Block Powder Granule Crystal Shard Flake Fibre Chunk Bead Dust
Liquid state type	Liquid state type: Specific type of liquid form or presentation of the substance at the time of exposure. Solution Suspension Emulsion/Cream Gel Foam
Amount	Amount: The amount, or estimate of the amount, of substance ingested, inhaled or absorbed by the individual. QuantityUnits: g oz (avoirdupois) (UCUM: [oz_av]) l ml Coded Text Unknown
Route of exposure	Route of exposure: The route of exposure for the affected individual. Ingested Injected Inhaled Direct contact
Packaging context	Packaging context: Category of packaging for the substance. Original packaging/container Other packaging/container
Packaging description	Packaging description: Narrative description about the packaging of the substance. For example: if the substance was labelled or packaged inappropriately.
Occupational context	Occupational context: Narrative or category describing the occupational context of the poisoning event. For example: occupational or non-occupational. Occupational Non-occupational
Physical context	Physical context: Narrative or category describing of the physical or environmental context where the poisoning event occurred. For example: well ventilated or enclosed space; indoors or outdoors. Indoors Outdoors
Location context	Location context: Narrative or category of the physical location where the poisoning event took place. Residential School Workplace Other
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'.
Comment	Comment: Additional narrative about the organisation not captured in other fields.
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
Safety context	Safety context: Narrative or category describing the safety context of the poisoning event. For example: supervised or unsupervised. Supervised Unsupervised
Risk factor	Risk factor: Identification of a risk factor that contributed to the occurrence of the poisoning event. This data element has multiple occurrences to allow more than one risk factor to be recorded. Coding with an external terminology is recommended, if available. Improper storage location Improper storage container Child unsupervised
Date/time of healthcare encounter	Date/time of healthcare encounter: Date and time when the individual first attended a medical service after exposure. More than one occurrence to record date/time for each level of medical service provided.
Event occurrence	Event occurrence: The type of occurrence of the poisoning event. For example: first event or subsequent episode of poisoning First occurrence Subsequent occurrence
Occurrence number	Occurrence number: The sequence number of this event within a series of related poisoning events.
Comment	Comment: Additional narrative about the poisoning event not captured in other fields.
Clinical profile	Clinical profile: A generic section header which should be renamed in a template to suit a specific clinical context.
Clinical screening	Clinical screening: A generic section header which should be renamed in a template to suit a specific clinical context.
Symptom/sign screening	Symptom/sign screening: Series of questions and associated answers used to screen for symptoms or signs. The answers may be self-reported.
Data
Any event	Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Any symptoms or signs?	Any symptoms or signs?: Is there a history of any symptoms or signs relevant for the screening purpose? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No Unknown
Onset of symptoms/signs	Onset of symptoms/signs: Timing of the inital recognition of any symptom or sign relevant for the screening purpose. The 'Onset' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture the onset of symptoms or signs. The specific and intended semantics can be further clarified in a template. For example: Date/time for the date the symptom started. Interval of date/time for a period of time eg. between 1940 and 1942. Text for descriptions like 'Immediately after the operation', or 'Up to one week ago', 'Up to two weeks ago', 'Three weeks ago'. Duration for the individual's age at the onset. Interval of Duration for the approximate age of the individual at the time of onset.
Specific symptom/sign	Specific symptom/sign: Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose.
Symptom/sign name	Symptom/sign name: Identification of a specific symptom or sign or grouping of symptoms or signs, by name. Coding of the 'Symptom/sign name' with a terminology is preferred, where possible. Headache Vomiting Diarrhoea Burning sensation in mouth Drowsiness Shortness of breath Convulsions Loss of consciousness Flushing of skin Dizziness Delirium Weakness
Presence?	Presence?: Is there a history of the specific symptom or sign being present? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No Unknown
Other symptom/sign	Other symptom/sign: Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose.
Symptom/sign name	Symptom/sign name: Identification of a specific symptom or sign or grouping of symptoms or signs, by name. Coding of the 'Symptom/sign name' with a terminology is preferred, where possible.
Presence?	Presence?: Is there a history of the specific symptom or sign being present? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No
Clinical notes	Clinical notes: Narrative summary or overview about a patient, specifically from the perspective of a healthcare provider, and with or without associated interpretations.
Data
Clinical notes	Clinical notes: The summary, assessment, conclusions or evaluation of the clinical findings.
Exposure profile	Exposure profile: A generic section header which should be renamed in a template to suit a specific clinical context.
Physical environment screening	Physical environment screening: Series of questions and associated answers used to screen for factors or characteristics in the physical environment which have caused or could potentially cause harm to an individual. The answers may be self-reported.
Data
Any event	Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Specific condition	Specific condition: Details about each possible specific environmental condition or factor.
Environmental condition	Environmental condition: The condition or factor in the physical environment being screened for. For example: safe storage of poisonous materials. Coding with a terminology is preferred, where possible. Appropriate storage location Appropriate storage container Appropriate accessibility restrictions, including doors and child-proof locks Appropriate container labelling Appropriate storage environment, including temperature, humidity and ventilation Hazardous substance inventory Documented emergency procedures
Presence?	Presence?: Has the specified 'Condition' been identified? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No Unknown
Environmental survey	Environmental survey: Details about environmental factors related to the local community and built environment that impact health.
Data	Data: *
Urban setting	Urban setting: The type of setting in which an individual lives or works. Urban Peri-urban Rural
Social profile	Social profile: A generic section header which should be renamed in a template to suit a specific clinical context.
Social network	Social network: Group of individuals connected by social interactions and personal relationships.
Data
Union status	Union status: Single word or phrase that describes an individual's current relationship with a life partner. Coding of the partnership status with a terminology is preferred, where possible. There is a huge variation in the value sets used across jurisdictions. Many have local, government-mandated value sets rather than using SNOMED CT or similar. For example: a 'marital status' value set including 'never married' or 'single'; 'married'; 'divorced'; or 'widowed'. Also known as 'civil status', 'union status', or 'relationship status'. Married Visiting union Common law Single Widowed Separated Divorced Other
Person - next of kin	Person - next of kin: An individual human being.
Structured name of a person - full	Structured name of a person - full: 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'. Codes from National Data Dictionary
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.
Middle name	Middle 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.
Nickname	Nickname: 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)'. Codes from National Data Dictionary
Role	Role: 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. Next of kin
Relationship	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. Mother Father Brother Sister Cousin Aunt Uncle Grandmother Grandfather Caregiver Guardian Legal Guardian Husband Wife Friend Son Daughter Spiritual advisor Worker in religion
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Address - international	Address - international: 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'.
City/Town	City/Town: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
District/County	District/County: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
State/Territory/Province	State/Territory/Province: 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.
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. Afghanistan Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas (the) Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia (Plurinational State of) Bonaire, Sint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil and MORE
Phone - unspecified number/s	Phone - unspecified number/s: 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. Mobile (cellular) telephone Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Business use Personal use Both business and personal use
Person - mother	Person - mother: An individual human being.
Structured name of woman - full + maiden	Structured name of woman - full + maiden: 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'. Codes from National Data Dictionary
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.
Middle name	Middle 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.
Nickname	Nickname: 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.
Maiden name	Maiden 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.
Relationship	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. Mother
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Address - international	Address - international: 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'.
City/Town	City/Town: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
District/County	District/County: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
State/Territory/Province	State/Territory/Province: 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.
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. Afghanistan Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas (the) Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia (Plurinational State of) Bonaire, Sint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil and MORE
Phone - unspecified number/s	Phone - unspecified number/s: 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. Mobile (cellular) telephone Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Business use Personal use Both business and personal use
Person - father	Person - father: An individual human being.
Structured name of a person - full	Structured name of a person - full: 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'. Codes from National Data Dictionary
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.
Middle name	Middle 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.
Nickname	Nickname: 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)'. Codes from National Data Dictionary
Relationship	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. Father
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Address - international	Address - international: 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'.
City/Town	City/Town: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
District/County	District/County: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
State/Territory/Province	State/Territory/Province: 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.
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. Afghanistan Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas (the) Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia (Plurinational State of) Bonaire, Sint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil and MORE
Phone - unspecified number/s	Phone - unspecified number/s: 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. Mobile (cellular) telephone Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Business use Personal use Both business and personal use
Person - guardian	Person - guardian: An individual human being.
Structured name of a person - full	Structured name of a person - full: 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'. Codes from National Data Dictionary
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.
Middle name	Middle 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.
Nickname	Nickname: 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)'. Codes from National Data Dictionary
Role	Role: 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. Guardian
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Address - international	Address - international: 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'.
City/Town	City/Town: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
District/County	District/County: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
State/Territory/Province	State/Territory/Province: 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.
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. Afghanistan Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas (the) Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia (Plurinational State of) Bonaire, Sint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil and MORE
Phone - unspecified number/s	Phone - unspecified number/s: 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. Mobile (cellular) telephone Telephone (excluding mobile telephone)
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.
Purpose	Purpose: The purpose or use for the identified type of electronic communication. Business use Personal use Both business and personal use
Occupation/school summary	Occupation/school summary: Summary or persistent information about an individual's current and past jobs and/or roles.
Data
Employment status	Employment status: Statement about the individual's current employment. For example: employed; unemployed; or not in labour force. Coding with a terminology is desirable, where possible. Detail about each occupation can be recorded within the CLUSTER.occupation_record archetype. Employed Unemployed Unknown
Occupation/school record	Occupation/school record: A single job or role carried out by an individual during a specified period of time.
Occupation	Occupation: The main job title or the role of the individual. For example: Chief Executive Officer; Carer; or Student. Each of these job titles or roles may be comprised of multiple duties. Armed Forces Occupations (All Ranks) Soldier Custos Governor General Leader, Opposition (Governmental) Opposition Leader Prime Minister Cabinet Minister Constituency Representative Government Minister Member of Parliament Minister, Cabinet Minister, Government Minister, Opposition MP Opposition Minister Senator Attorney General Solicitor General Public Defender Ombudsman, Political Political Ombudsman Chief Parliamentary Counsel Legislators n.e.c. Civil Service Commissioner Commissioner, Civil Service Financial Secretary Head, Civil Service Commission Permanent Secretary Secretary, Financial Secretary, Permanent Chief Executive Officer (Governmental Department/Agency) and MORE [...]
Employer/School	Employer/School: 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 of Employer/School	Name of Employer/School: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
Address - local	Address - local: Details about the location of a person, physical building or landmark.
Street address	Street address: 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'.
Landmark	Landmark: 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'.
Community	Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. Aenon Town Alley Alston Ashley Banks Beckford Kraal Brandon Hill Brixton Hill Bucknor Bucks Common Bushy Park Chapelton Chateau Cockpit Coffee Piece Colonels Ridge Coxswain Crofts Hill Crooked River Cumberland Curatoe Hill Dawkins Effortville Four Paths Frankfield Freetown Gimme-me-bit Glenmuir Grantham Gravel Hill Hayes and MORE
Parish	Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. Clarendon Hanover Kingston Manchester Portland Saint Andrew Saint Ann Saint Catherine Saint Elizabeth Saint James Saint Mary Saint Thomas Trelawny Westmoreland
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. Jamaica
Clinical management	Clinical management: A generic section header which should be renamed in a template to suit a specific clinical context.
Management screening	Management screening: Series of questions and associated answers used to screen for clinical management including, but not limited to treatments, therapies and hospitalisation. The answers may be self-reported.
Data
Any event	Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Hospital admission	Hospital admission: Details about a specific management or treatment activity or grouping of management or treatment activities relevant for the screening purpose.
Management name	Management name: Name of a specific management or treatment activity or grouping of management or treatment activities. For example: Admitted to hospital; Admitted to ICU; Use of compression stockings; Daily dressings; ECMO. Coding of the 'Management name' with a terminology is preferred, where possible. Admitted to hospital
Done?	Done?: Is there a history of the specific management or treatment activity? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No Unknown
Inpatient episode details	Inpatient episode details: Details about an admission episode to an inpatient facility.
Place of admission	Place of admission: The physical location where the patient has been admitted. This data element has multiple occurrences to support more than one level of location to be recorded. For example, both the hospital and the ward.
Reason for admission	Reason for admission: The reason for admission. For example: admission diagnosis.
Date of admission	Date of admission: The date of admission to the inpatient facility.
Date of discharge	Date of discharge: The date of when the individual left to the inpatient facility. For example: discharged home or to an aged care facility.
Laboratory test screening	Laboratory test screening: Series of questions and associated answers used to screen whether diagnostic investigations have been carried out. The answers may be self-reported.
Data
Any event	Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Specimen taken?	Specimen taken?: Is there a history of any diagnostic tests or investigations related to the screening purpose? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No Unknown
Specific test	Specific test: Details about a specified investigation or grouping of investigations relevant for the screening purpose. Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations.
Test name	Test name: Name of the diagnostic investigation or grouping of investigations. For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible.
Done?	Done?: Is there a history of the investigation being carried out? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No Unknown
Date/time sent to laboratory	Date/time sent to laboratory: Indication of timing related to the investigation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an investigation was carried out. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the investigation; the interval of time during which the investigation was carried out; the duration of the investigation; the age of the individual at the time of the investigation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year.
Date/time result reported	Date/time result reported: Indication of timing related to the investigation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an investigation was carried out. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the investigation; the interval of time during which the investigation was carried out; the duration of the investigation; the age of the individual at the time of the investigation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year.
Specimen collection details	Specimen collection details: A physical sample collected from, or related to, an individual for the purpose of investigation, examination or analysis. For example: Tissue or body fluid.
Specimen type	Specimen type: The type of specimen. For example: Venous blood, bacterial culture, cytology, or tissue sample. Coding of the specimen type with a terminology is preferred, where possible. Optional[{fhir_mapping=Specimen.type}]
Date/time received by laboratory	Date/time received by laboratory: The date and time that the sample was received at the laboratory. Optional[{fhir_mapping=Specimen.receivedTime}]
Date/time collected	Date/time collected: The date and time that collection has been ordered to take place or has taken place. This datetime will be captured primarily in the INSTRUCTION timing, ACTION time or OBSERVATION times. However, as this is a critical piece of information, it can be useful to also associate it directly with the specimen itself.
Adequacy for testing	Adequacy for testing: Information about whether the specimen was adequate for testing. This element is intended to be used to record a judgement about whether or not the specimen quality was good enough for testing, and whether or not testing has been carried out. Coding of the specimen quality issues with a terminology is preferred, where possible. Satisfactory Unsatisfactory - analysed Unsatisfactory - not analysed
Laboratory analyte result - interpretative	Laboratory analyte result - interpretative: The result of a laboratory test for a single analyte value.
Test result	Test result: The value of the analyte result. For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details. Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}] Positive Indeterminate Negative Unknown
Comment	Comment: Additional narrative about the analyte result, not captured in other fields. Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
Laboratory analyte result - quantitative	Laboratory analyte result - quantitative: The result of a laboratory test for a single analyte value.
Test result	Test result: The value of the analyte result. For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details. Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}] Quantity Count Duration Proportion Text Coded Text
Comment	Comment: Additional narrative about the analyte result, not captured in other fields. Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
Treatment at home	Treatment at home: Summary or persistent details about a treatment course or protocol for an identified condition.
Data
Treatment name	Treatment name: The name of the (main) treatment or course of treatment.
Description	Description: Narrative description about the treatment.
Date treatment started	Date treatment started: The date when the treatment or course of treatment was started.
Treatment at healthcare facility	Treatment at healthcare facility: Summary or persistent details about a treatment course or protocol for an identified condition.
Data
Treatment name	Treatment name: The name of the (main) treatment or course of treatment.
Description	Description: Narrative description about the treatment.
Clinical indication	Clinical indication: The clinical reason for the treatment. Coding of the clinical indication with a terminology is preferred, where possible. For example: 'Cancer treatment' 'Angina' or 'Type 1 Diabetes mellitus'. This data element allows multiple occurrences to enable the user to record multiple responses, if required.
Date treatment started	Date treatment started: The date when the treatment or course of treatment was started.
Date treatment stopped	Date treatment stopped: The date when the treatment or course of treatment was completed or stopped.
Treatment outcome	Treatment outcome: Category of the treatment outcome for the individual. Treatment successful Treatment failed Indeterminate
Comment	Comment: Narrative description about the overall treatment, not captured in other data elements.
Management notes	Management notes: Narrative summary or overview about a patient, specifically from the perspective of a healthcare provider, and with or without associated interpretations.
Data
Actions taken	Actions taken: The summary, assessment, conclusions or evaluation of the clinical findings.
Outcome	Outcome: A generic section header which should be renamed in a template to suit a specific clinical context.
Vital status	Vital status: Status of an individual as alive or dead.
Data
Any point in time event	Any point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time.
Data
Vital status	Vital status: Whether an individual is alive or dead. Usually only relevant at a specified point in time. For example: record as alive or dead at the time of recording information within a disease registry. Alive Dead Unknown
Death summary	Death summary: Summary information about the circumstances and context of the death of an individual, excluding the cause(s) of death.
Data
Date of death	Date of death: The known, or assumed, date and time of death. Partial dates and an absence of time of death are allowed, if necessary. For example: based on findings pertaining to examination of the body and the pathologist's reconstruction of time of death based on post-mortem changes, temperature, etc. May also be known as DOD (date of death). If more than one 'Date of death alternatives' have been proposed, this data element could be renamed in a template as the 'Confirmed/Agreed date of death'.
Place of death	Place of death: The simple name, address or landmark of the place where the individual died. For example: 'City Hospital'; 'Mother's house'; or 'Mt Vesuvius crater'; or 'Corner of Smith & Brown Streets'. This data element has multiple occurrences to allow more than one level of detail about the place of death, such as recording both 'City Hospital' and 'Ward 6 North'.
Management screening	Management screening: Series of questions and associated answers used to screen for clinical management including, but not limited to treatments, therapies and hospitalisation. The answers may be self-reported.
Data
Any event	Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Post mortem	Post mortem: Details about a specific management or treatment activity or grouping of management or treatment activities relevant for the screening purpose.
Management name	Management name: Name of a specific management or treatment activity or grouping of management or treatment activities. For example: Admitted to hospital; Admitted to ICU; Use of compression stockings; Daily dressings; ECMO. Coding of the 'Management name' with a terminology is preferred, where possible. Post mortem carried out
Done?	Done?: Is there a history of the specific management or treatment activity? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. Yes No Unknown
Date	Date: Indication of timing related to the management activity. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the management activity may have occurred. The specific and intended semantics can be further clarified in a template. For example: the actual point in time when, or interval during which, an activity took place; the start and stop time of an activity; the duration of the activity; the age of the individual at the time of the activity; or the duration of time since the activity occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year.
Recommendation	Recommendation: A suggestion, advice or proposal for clinical management.
Data
Topic	Topic: The topic or subject of the recommendation. Useful if multiple types of recommendations are made at the same time, and within the same data set.
Recommendation	Recommendation: Narrative description of the recommendation. May be coded, using a terminology, if required.
Rationale	Rationale: Justifications for the recommendation.
Additional notes	Additional notes: Narrative summary or overview about a patient, specifically from the perspective of a healthcare provider, and with or without associated interpretations.
Data
Additional notes	Additional notes: The summary, assessment, conclusions or evaluation of the clinical findings.
Field investigator classification	Field investigator classification: A generic section header which should be renamed in a template to suit a specific clinical context.
Field diagnosis	Field diagnosis: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual. Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Diagnosis name	Diagnosis name: Identification of the problem or diagnosis, by name. Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Cause of death	Cause of death: Details about specific diseases, conditions or injuries that caused or contributed to the death of an individual.
Data
Immediate cause	Immediate cause: The disease, condition or injury that directly led to, or occurred closest to, the time of death. It is recommended that 'Direct cause' be coded with an external terminology. This data element may also be considered as the Cause labelled as 'A' within a death certificate recording a sequence of events leading to death. For example: Cerebral haemorrhage (as 'Direct cause', A) - 'due to' Metastasis of the brain ('Antecedent cause B'); - 'due to' Breast cancer (as the earliest 'Antecedent cause C'; or 'Underlying cause').
Intermediate cause(s)	Intermediate cause(s): Details about one or more diseases, conditions or injuries in the sequence of events preceding death, recorded in order from most recent onset to the earliest onset. In the following example, there would only need to be two instances of this 'Antecedent cause(s)' CLUSTER represented in a template: - Cerebral haemorrhage (as 'Direct cause', A) - 'due to' Metastasis of the brain ('Antecedent cause B'); - 'due to' Breast cancer (as the earliest 'Antecedent cause C'; or 'Underlying cause'). If there is more than one 'Antecedent cause', each is represented as a separate instance of this CLUSTER.
Intermediate cause	Intermediate cause: Identification of an antecedent disease, condition or injury that directly contributed to the 'Direct cause'. It is recommended that 'Cause' be coded with an external terminology.
Underlying cause	Underlying cause: Details about one or more diseases, conditions or injuries in the sequence of events preceding death, recorded in order from most recent onset to the earliest onset. In the following example, there would only need to be two instances of this 'Antecedent cause(s)' CLUSTER represented in a template: - Cerebral haemorrhage (as 'Direct cause', A) - 'due to' Metastasis of the brain ('Antecedent cause B'); - 'due to' Breast cancer (as the earliest 'Antecedent cause C'; or 'Underlying cause'). If there is more than one 'Antecedent cause', each is represented as a separate instance of this CLUSTER.
Underlying cause	Underlying cause: Identification of an antecedent disease, condition or injury that directly contributed to the 'Direct cause'. It is recommended that 'Cause' be coded with an external terminology.
Other significant conditions	Other significant conditions: Details about other significant conditions that may have contributed to the death, but without a causal association.
Condition	Condition: Name of a significant condition that may have contributed to the death, but without a causal association. It is recommended that 'Condition' be coded with an external terminology.
Field classification	Field classification: Classification for an identified health event as part of a public health surveillance investigation.
Data
Index event	Index event: The name of the infectious event under investigation. This data element may be redundant if the index event has been identified elsewhere within a template. Accidental poisoning
Final classification	Final classification: Classification of the likelihood of the 'Index event' as causal after completion of a case investigation. Not to be used to record the 'Initial classification' at the initiation of a case investigation. Pending Probable Laboratory confirmed Clinically confirmed Discarded Inconclusive
Reason for classification	Reason for classification: The broad category of the reason for the classification. For example: lost to follow-up.
Contribution to death	Contribution to death: Assessment of the relationship between the index event and the death of the individual. Related Unrelated Unknown
Comment	Comment: Additional narrative about the classification, not captured in other fields.
Final classification	Final classification: A generic section header which should be renamed in a template to suit a specific clinical context.
Diagnosis	Diagnosis: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual. Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Diagnosis name	Diagnosis name: Identification of the problem or diagnosis, by name. Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Classification	Classification: Classification for an identified health event as part of a public health surveillance investigation.
Data
Index event	Index event: The name of the infectious event under investigation. This data element may be redundant if the index event has been identified elsewhere within a template. Accidental poisoning
Final classification	Final classification: Classification of the likelihood of the 'Index event' as causal after completion of a case investigation. Not to be used to record the 'Initial classification' at the initiation of a case investigation. Pending Probable Laboratory confirmed Clinically confirmed Discarded Inconclusive
Reason for classification	Reason for classification: The broad category of the reason for the classification. For example: lost to follow-up.
Contribution to death	Contribution to death: Assessment of the relationship between the index event and the death of the individual. Related Unrelated Unknown
Comment	Comment: Additional narrative about the classification, not captured in other fields.