TEMPLATE Rheumatic fever_heart disease case investigation form (Rheumatic fever_heart disease case investigation form)

TEMPLATE ID	Rheumatic fever_heart disease case investigation form
Concept	Rheumatic fever_heart disease 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: 66.0.0 MD5-CAM-1.0.1: 89afc75012e39810611432d96f2da3dd PARENT:MD5-CAM-1.0.1: 005501C1FA493A4838F5F1121F2870EC Original Language: ISO_639-1::en
Language used	en
Citeable Identifier	1013.26.1036
Root archetype id	openEHR-EHR-COMPOSITION.report.v1
2024 12 29 Rheumatic fever/heart disease case investigation form	2024 12 29 Rheumatic fever/heart disease case investigation form: Document to communicate information to others, commonly in response to a request from another party.
Infectious disease investigation metadata	Infectious disease investigation metadata: Infectious disease investigation metadata.
Data	Data: *
Notified disease	Notified disease: The name of the disease under investigation. Rheumatic fever/Rheumatic heart disease
Notification ID	Notification ID: The unique identifier for the notification that triggered this infectious disease 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 infectious disease 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 identified	Date identified: The date when the infection was first identified by a clinician or notifier.
Epidemiological week of onset	Epidemiological week of onset: Standardised way to identify the week of onset of symptoms. Also known as 'epi week'.
Epidemiological week of notification	Epidemiological week of notification: Standardised way to identify the week of notification to public health authorities. Also known as 'epi week'.
Date of notification	Date of notification: Details about the person who notified public health authorities about the infectious disease case.
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
Detection method	Detection method: Method of detection of the index disease.
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 to MO(H)	Date submitted to MO(H): The date when the investigator submitted the investigation report for review.
MO(H) sign off	MO(H) sign off: 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'.
Parish	Parish: 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 submitted to NSU	Date submitted to NSU: 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
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
Onset of illness	Onset of illness: 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.
Major manifestation	Major manifestation: 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. Carditis Polyarthritis Chorea Erythema marginatum Subcutaneous nodules
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
Date of onset	Date of onset: Indication of timing related to the specific symptom or sign. 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 specific symptom or sign occured. 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 when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; 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.
Minor manifestation	Minor manifestation: 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. Joint pains High temperature (fever) Positive C-reactive protein test Increased erythrocyte sedimentation rate Increased PR interval on ECG
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
Date of onset	Date of onset: Indication of timing related to the specific symptom or sign. 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 specific symptom or sign occured. 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 when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; 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.
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
Date of onset	Date of onset: Indication of timing related to the specific symptom or sign. 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 specific symptom or sign occured. 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 when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; 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.
Cardiac involvement	Cardiac involvement: 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. Heart failure Bacterial endocarditis
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
Date of diagnosis	Date of diagnosis: Indication of timing related to the specific symptom or sign. 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 specific symptom or sign occured. 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 when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; 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.
Valve involvement	Valve involvement: Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose.
Valve lesion	Valve lesion: 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. No valve lesion Mitral stenosis (MS) Mitral regurgitation (MR) Aortic stenosis (AS) Aortic regurgitation (AR) Tricuspid stenosis (TS) Tricuspid regurgitation (TR) Pulmonary stenosis (PS) Pulmonary regurgitation (PR)
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
Date of diagnosis	Date of diagnosis: Indication of timing related to the specific symptom or sign. 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 specific symptom or sign occured. 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 when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; 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.
Overall assessment	Overall assessment: 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. Rheumatic heart disease
Severity of heart damage	Severity of heart damage: 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. None Borderline Mild Moderate Severe Indeterminate
ECG result	ECG result: Measurement of the electrical activity generated by the heart. Also known as an electrocardiograph or EKG.
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
PR interval	PR interval: PR interval measurement across the ECG as a whole (multiple leads). The PR interval is measured from onset of P wave to the onset of QRS complex. >=0 ms
Clinical context	Clinical context: A generic section header which should be renamed in a template to suit a specific clinical context.
Problem/Diagnosis screening	Problem/Diagnosis screening: Series of questions and associated answers used to screen for issues, problems or diagnoses. 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 problem or diagnosis	Specific problem or diagnosis: Details about a specific issue, problem or diagnosis or grouping of problems or diagnoses relevant for the screening purpose.
Problem/diagnosis name	Problem/diagnosis name: Identification of an issue, problem or diagnosis, or grouping of issues, problems or diagnoses, by name. Coding of the 'Problem/diagnosis name' with a terminology is preferred, where possible. History of Rheumatic fever Rheumatic heart disease
Presence?	Presence?: Is there a history of the specific issue, problem or diagnosis? 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
Adverse reaction screening questionnaire	Adverse reaction screening questionnaire: Series of questions and associated answers used to screen for adverse reactions. 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 adverse reactions?	Any adverse reactions?: Is there a history of any adverse reactions 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
Adverse reaction risk summary	Adverse reaction risk summary: Clinical assessment of the propensity for an individual to experience a harmful or undesirable physiological response if exposed, or re-exposed, to a substance. Substances include, but are not limited to: a therapeutic substance administered correctly at an appropriate dosage for the individual; food; material derived from plants or animals; or venom from insect stings. Optional[{source=openEHR,FHIR}]
Data
Substance	Substance: Identification of a substance, or substance class, that is considered to put the individual at risk of an adverse reaction event. Both an individual substance and a substance class are valid entries in 'Substance'. A substance may be a compound of simpler substances, for example a medicinal product. It is strongly recommended that the 'Substance' is coded with a terminology capable of triggering decision support, where possible. For example: Snomed CT, DM+D, RxNorm, NDFRT, ATC, New Zealand Universal List of Medicines and Australian Medicines Terminology. Free text entry should only be used if there is no appropriate terminology available.
Adverse reaction event	Adverse reaction event: Information about a specific adverse reaction event caused by exposure to a specific substance.
Specific substance	Specific substance: The substance considered to be responsible for the specific adverse reaction event. For example: 'Amoxycillin'. Only an individual substance is a valid entry in 'Specific substance'. A substance may be a compound of simpler substances, for example a medicinal product. If the 'Substance' recorded in the archetype in which this archetype is nested is an individual substance and not a substance class, then it may be duplicated in this data element, or this element may be redundant. It is strongly recommended that 'Specific substance' be coded with a terminology, for example: RxNorm, SNOMED CT, DM+D, NDFRT, ICD-9, ICD-10, UNI, ATC or CPT.
Reaction	Reaction: Clinical symptoms and/or signs that are observed or associated with the adverse reaction. Manifestation can be expressed as a single word, phrase or brief description. For example: nausea, rash. 'No reaction' may be appropriate where a previous reaction has been noted but the reaction did not re-occur after further exposure. It is preferable that 'Manifestation' should be coded with a terminology, where possible. The values entered here may be used to display on an application screen as part of a list of adverse reactions.
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.
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
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
Clinical management	Clinical management: A generic section header which should be renamed in a template to suit a specific clinical context.
Medication screening	Medication screening: Series of questions and associated answers used to screen for the use of medications. 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 prophylaxis?	Any prophylaxis?: Is there a history of use of any medication 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
BPG administration	BPG administration: An assertion about the current use of a single medication by an individual.
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
Medication name	Medication name: Name of the medication. It is strongly recommended that the 'Medication name' be coded with a terminology capable of triggering decision support, where possible. Free text entry should only be used if there is no appropriate terminology available or for customised extemporaneous preparations. The extent of coding may vary from the simple generic or product name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. For example: 'Plaquenil'; 'Ibrutinib 420 mg tablet'; 'Rectinol ointment, 50 g, tube'; or 'Hydrofibre dressing with silver'. Benzathine benzylpenicillin
Dose and timing	Dose and timing: Complete narrative description about how the ordered item is to be used.
Route of administration	Route of administration: The route by which the medication is administrated into the body. For example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible. Intramuscular
Last administered	Last administered: The date and time when the medication was last taken by, or administered to, the individual. For example: the time warfarin was last taken at home prior to admission to hospital; or when the last dose was administered before a transfer from hospital to aged care.
Comment	Comment: Additional narrative about the medication statement not captured in other fields.
First administered	First administered: The date and time when the medication was first taken by, or administered to, the individual.
Number of doses administered in the past 12 months	Number of doses administered in the past 12 months: The total number of doses administered. For example: 1 stat dose of prophylactic antibiotics; or 10 doses in an antibiotic course over 5 days.
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
Throat swab specimen	Throat swab specimen: 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. Throat swab microscopy and culture
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}] Throat swab
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
Gram stain findings	Gram stain findings: Findings observed during microscopic examination of tissue treated with specialised stains, intended to enhance the visualisation of specimen, including microorganisms, tissue structures and cellular details.
Staining method	Staining method: Name of the technique used to stain the specimen. For example: Ziehl–Neelsen; Gram stain Gram stain
Clinical findings	Clinical findings: Narrative description about the findings observed using the identified stain. For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris.
Per target finding	Per target finding: Details about a specific microorganism, tissue structure, or cell structure observed during the microscopic examination of a stained specimen.
Staining target	Staining target: Identification of the target organism, cell or structure. For example: gram-positive cocci, fungi, acid-fast bacilli, cell nuclei or pathological inclusions. Coding with an external terminology is preferred, if available. Gram-positive cocci Gram-negative cocci Gram-positive rods Gram-negative rods
Presence	Presence: Statement about detection of the staining target in the specimen. Detected Not detected
Qualitative result	Qualitative result: Qualitative assessment of the amount of the target organism, cell, or structure observed using the stain. Scant Low Moderate High Absent
Comment	Comment: Additional narrative about the target findings using the identified stain, not captured in other fields.
Microbiology culture findings	Microbiology culture findings: Findings observed from culturing a specimen to detect and identify the growth of microorganisms.
Overall growth	Overall growth: Statement about the presence or absence of any microbial growth on culture. Growth No growth
Streptococcus	Streptococcus: Details about specific culture findings for each identified organism.
Microorganism name	Microorganism name: Name of the microorganism cultured. For example: name of a bacteria, virus or fungus. Group A beta haemolytic Streptococcus
Growth	Growth: Observation about the presence or absence of growth of the identified organism on culture. Detected Not detected Indeterminate
Qualitative result	Qualitative result: Qualitative assessment of the amount of the identified microorganism grown on culture. No growth Light growth Moderate growth Heavy growth
Comment	Comment: Additional narrative about the culture findings for the identified microorganism, not captured in other fields.
Other microorganism	Other microorganism: Details about specific culture findings for each identified organism.
Microorganism name	Microorganism name: Name of the microorganism cultured. For example: name of a bacteria, virus or fungus.
Growth	Growth: Observation about the presence or absence of growth of the identified organism on culture. Detected Not detected Indeterminate
Qualitative result	Qualitative result: Qualitative assessment of the amount of the identified microorganism grown on culture. No growth Light growth Moderate growth Heavy growth
Comment	Comment: Additional narrative about the culture findings for the identified microorganism, not captured in other fields.
Serum specimen	Serum specimen: 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. ASOT
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}] Serum
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
Antibody test finding	Antibody test finding: The result of a laboratory test designed to detect and quantify the presence of specific antibodies produced by the immune system in response to a microorganism, tissue, allergen, or physiological process, within a clinical specimen.
Test name	Test name: Name of the antibody test. Coding with an external terminology is recommended, if available. For example: SARS-CoV-2 IgG antibody test. ASOT test
Antibody target	Antibody target: The specific antigenic structure or component that the test is designed to detect. Coding with an external terminology is recommended, if available. For example: infection-related IgG/IgM, IgG1 or IgG2, allergen-specific IgE; anti-dsDNA.
Microbial target	Microbial target: The name of the microorganism associated with the antibody target, if relevant. Coding with an external terminology is recommended, if available. For example: SARS-CoV-2. Group A Streptococcus
Test method	Test method: Method used for the antibody test. Coding with an external terminology is recommended, if available. For example: lateral flow immunoassay, ELISA, chemiluminescent immunoassay.
Presence	Presence: Statement about detection of the identified antibody in the specimen. Coded Text Detected Not detected Indeterminate Text
Quantitative result	Quantitative result: Quantitative assessment of the amount of the identified antibody in the specimen. QuantityUnits: k[iU]/L [iU]/mL Proportion Ratio
Comment	Comment: Additional narrative about the test finding not captured in other fields.
Imaging examination screening - JM	Imaging examination screening - JM: 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
Specific imaging	Specific imaging: 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.
Echocardiogram	Echocardiogram: 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
Echocardiogaphy result	Echocardiogaphy result: The result of an imaging examination performed on an individual, using radiological techniques.
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
Study name	Study name: The name of the imaging examination performed. For example: 'CT abdomen'; 'Doppler ultrasound of renal artery' or 'Plain chest xray'. Coding with a terminology is strongly recommended, preferably a term specifying both modality and anatomical location, where possible. Examples of candidate terminologies are the LOINC Imaging Document Codes, RadLex Playbook or SNOMED-CT. Equivalent to DiagnosticReport.code in FHIR. Echocardiography
Study date	Study date: Date/time when the imaging started. Equivalent to ImagingStudy.started in FHIR.
Echocardiography findings	Echocardiography findings: Findings on radiological examination of the heart.
Body structure	Body structure: Identification of the body structure or region examined. For example: 'Liver', 'Right ankle' or 'Lymph node group'. Coding of the body structure with an appropriate terminology, such as SNOMED CT, is recommended. If the body structure has been fully identified in this 'Body structure' element, then the 'Body site' data element and 'Structured body site' SLOT become redundant. Heart
Comment	Comment: Additional narrative about the imaging findings of the body structure, not captured in other fields.
Relative ventricular size	Relative ventricular size: Description of the comparative size of both cardiac ventricles relative to established normal ranges. Normal Enlarged
Valves normal?	Valves normal?: Overarching assessment about the condition and functionality of all heart valves, reflecting their structural integrity, movement, and any abnormalities observed. Normal Abnormal
Tricuspid stenosis (TS)	Tricuspid stenosis (TS): Statement about the presence or absence of tricuspid stenosis. Present Absent Indeterminate
Tricuspid regurgitation (TR)	Tricuspid regurgitation (TR): Statement about the presence or absence of tricuspid regurgitation. Present Absent Indeterminate
Pulmonary stenosis (PS)	Pulmonary stenosis (PS): Statement about the presence or absence of pulmonary stenosis. Present Absent Indeterminate
Pulmonary regurgitation (PR)	Pulmonary regurgitation (PR): Statement about the presence or absence of pulmonary regurgitation. Present Absent Indeterminate
Mitral stenosis (MS)	Mitral stenosis (MS): Statement about the presence or absence of mitral stenosis. Present Absent Indeterminate
Mitral regurgitation (MR)	Mitral regurgitation (MR): Statement about the presence or absence of mitral regurgitation. Present Absent Indeterminate
Aortic stenosis (AS)	Aortic stenosis (AS): Statement about the presence or absence of aortic stenosis. Present Absent Indeterminate
Aortic regurgitation (AR)	Aortic regurgitation (AR): Statement about the presence or absence of aortic regurgitation. Present Absent Indeterminate
Pericarditis	Pericarditis: Statement about the presence or absence of pericarditis. Present Absent Indeterminate
Myocarditis	Myocarditis: Statement about the presence or absence of myocarditis. Present Absent Indeterminate
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'.
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.
Date/time of onset	Date/time of onset: Estimated or actual date/time that signs or symptoms of the problem/diagnosis were first observed. Data captured/imported as "Age at onset" should be converted to a date using the subject's date of birth.
Date/time of diagnosis	Date/time of diagnosis: Estimated or actual date/time the diagnosis or problem was recognised by a healthcare professional. Partial dates are acceptable. If the subject of care is under the age of one year, then the complete date or a minimum of the month and year is necessary to enable accurate age calculations - for example, if used to drive decision support. Data captured/imported as "Age at time of clinical recognition" should be converted to a date using the subject's date of birth.
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.
Course description	Course description: Narrative description about the course of the problem or diagnosis since onset.
Problem/Diagnosis qualifier	Problem/Diagnosis qualifier: Contextual or temporal qualifier for a specified problem or diagnosis.
Occurrence	Occurrence: Category of the occurrence for this problem or diagnosis. This data element can be an additional qualifier to the 'New' value in the 'Episodicity' value set, that is a condition such as asthma can have recurring new episodes that have periods of resolution in between. However it can be important to identify the first ever episode of asthma from all of the other episodes. First occurrence Recurrence
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 infectious disease as part of a disease surveillance investigation.
Data
Index disease	Index disease: The name of the infectious disease under investigation. This data element may be redundant if the index disease has been identified elsewhere within a template. Rheumatic heart disease Rheumatic fever
Final classification	Final classification: Classification of the likelihood of the 'Index disease' 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, child of an infected mother.
Epidemiological link	Epidemiological link: Identification of the cause or source of transmission. Animal to human transmission Exposure to a common source Environmental exposure Human to human transmission
Aetiology category	Aetiology category: The category for the cause of infection. For example: imported, import-related, endemic, vaccine-associated, congenital or unknown. Imported case Import-related case Endemic case Unknown
Source country	Source country: Country identified as the (likely or probable) source for an imported or import-related case.
Endemic source category	Endemic source category: The category for the source of an endemic case. For example: household contact, community, or unknown.
Contribution to death	Contribution to death: Assessment of the relationship between the index disease 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.
Problem/Diagnosis qualifier	Problem/Diagnosis qualifier: Contextual or temporal qualifier for a specified problem or diagnosis.
Occurrence	Occurrence: Category of the occurrence for this problem or diagnosis. This data element can be an additional qualifier to the 'New' value in the 'Episodicity' value set, that is a condition such as asthma can have recurring new episodes that have periods of resolution in between. However it can be important to identify the first ever episode of asthma from all of the other episodes. First occurrence Recurrence
Classification	Classification: Classification for an identified infectious disease as part of a disease surveillance investigation.
Data
Index disease	Index disease: The name of the infectious disease under investigation. This data element may be redundant if the index disease has been identified elsewhere within a template. Rheumatic heart disease Rheumatic fever
Final classification	Final classification: Classification of the likelihood of the 'Index disease' 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, child of an infected mother.
Epidemiological link	Epidemiological link: Identification of the cause or source of transmission. Animal to human transmission Exposure to a common source Environmental exposure Human to human transmission
Aetiology category	Aetiology category: The category for the cause of infection. For example: imported, import-related, endemic, vaccine-associated, congenital or unknown. Imported case Import-related case Endemic case Unknown
Source country	Source country: Country identified as the (likely or probable) source for an imported or import-related case.
Endemic source category	Endemic source category: The category for the source of an endemic case. For example: household contact, community, or unknown.
Contribution to death	Contribution to death: Assessment of the relationship between the index disease and the death of the individual. Related Unrelated Unknown
Comment	Comment: Additional narrative about the classification, not captured in other fields.