- Sem Ver: 29.2.0
- MD5-CAM-1.0.1: 5e83cd44adbd23f36b93ad7b50698232
- PARENT:MD5-CAM-1.0.1: 005501C1FA493A4838F5F1121F2870EC
- Original Language: ISO_639-1::en
- Acute Flaccid Paralysis (AFP)/Polio
- Chikungunya virus
- Congenital Rubella virus
- Congenital Syphilis
- Congenital Zika virus
- Dengue fever
- Diphtheria
- Fever & rash
- Guillain-Barre syndrome
- HIV/AIDS
- Meningitis/Encephalitis
- Monkeypox
- Ophthalmia neonatorum
- Paediatric HIV
- Pertussis
- Rheumatic fever/Rheumatic heart disease
- Serious Acute Respiratory Infection (SARI)
- Tuberculosis
- Zika virus
The investigation ID and the notification ID may be identical if both the notification and investigation are carried out within the same system.
The investigation ID and the notification ID may be identical if both the notification and investigation are carried out within the same system.
Also known as 'epi week'.
Also known as 'epi week'.
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
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.
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.
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
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.
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
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.
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
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.
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'.
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'.
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
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
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
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
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.
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.
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
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.
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.
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.
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
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
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.
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.
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
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.
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.
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.
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
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.
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'.
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'.
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
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
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
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
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.
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.
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
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.
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.
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.
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
This data element may be redundant if the index disease has been identified elsewhere within a template.
- Acute Flaccid Paralysis (AFP)/Polio
- Chikungunya virus
- Congenital Rubella virus
- Congenital Zika virus
- Dengue fever
- Monkeypox
- Serious Acute Respiratory Infection (SARI)
- Zika virus
- Guillain-Barre syndrome
- Tuberculosis
- HIV/AIDS
- Paediatric HIV
- Fever & rash
Not to be used to record the 'Final classification' after completion of a case investigation.
- Suspected
- Probable
- Not suspected
For example: lost to follow-up, child of an infected mother.
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
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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'.
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'.
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
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
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
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 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 °
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 °
For example: a location on a Google or iOS map.
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
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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)
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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)
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Business use
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.
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
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
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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'.
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'.
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
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
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
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 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 °
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 °
For example: a location on a Google or iOS map.
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)
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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.
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
For example: 'Neighbour in the house with the red door'.
- Baby of
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
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.
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.
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.
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.
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.
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.
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.
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'.
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'.
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
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
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
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 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 °
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 °
For example: a location on a Google or iOS map.
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)
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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.
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
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.
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
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
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
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
- Live birth
- Still birth
The value for this data element will usually, but not always, be identical to the 'Pregnancy duration' data element within the EVALUATION.pregnancy_summary in the maternal record. It may also be derived using the 'Agreed date' data element within the EVALUATION.estimated_date_delivery archetype in the maternal record. Usually estimated by Naegele's rule or by ultrasound scan.
P0W..P52W Week
Usually estimated by physical examination and/or neuromuscular assessment of the newborn.
P0W..P52W Week
- Pre-term
- Term
- Post-term
Also known as 'Corrected age'. In most use cases the DV_DURATION data type is used to record the Adjusted age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days), and the DV_TEXT data type is used for recording a textual representation of the individual's age. For example: 'P3M2W', '0,2884615384615385 a_j' or '3 months 2 weeks'.
Duration>-P1Y
Quantity-1..10; -1..10
Units:- yr
- a_j
Text
0..1000; 0..2000; 0..1000000
Units:
- kg
- lbm
- g
0..1000; 0..2000; 0..1000000
Units:
- kg
- lbm
- g
0..1000; 0..2000; 0..1000000
Units:
- kg
- lbm
- g
- Naked
- Nappy/diaper
- Lightly clothed/underwear
- Fully clothed, without shoes
- Fully clothed, including shoes
- Naked
- Nappy/diaper
- Lightly clothed/underwear
- Fully clothed, without shoes
- Fully clothed, including shoes
- Weight-for-age
For example: a choice between <-3, <-2, or Normal.
For example, for a typical height assessment, 'WHO' might be used, whereas for children diagnosed with Turner Syndrome, the 'Turner' standard would be applicable (see the Royal College of Paediatrics and Child Health API (https://growth.rcpch.ac.uk/).
Height is measured with the individual in a standing position and body length in a recumbent position.
0..1000; 0..250
Units:
- cm
- in
0..1000; 0..250
Units:
- cm
- in
0..1000; 0..250
Units:
- cm
- in
- Standing
- Lying
For example: noting of amputation.
- Standing
- Lying
For example: noting of amputation.
- Length/height-for-age
For example: a choice between <-3, <-2, or Normal.
0..100; 0..40
Units:
- cm
- in
0..100; 0..40
Units:
- cm
- in
0..100; 0..40
Units:
- cm
- in
For example: 'uncooperative child','caput & moulding post birth' and 'haematoma'.
For example: 'uncooperative child','caput & moulding post birth' and 'haematoma'.
- Head circumference-for-age
For example: a choice between <-3, <-2, or Normal.
The answers may be self-reported.
For example: Bee sting; travel to an 'at risk' location; exposure to infected body fluids; or worked as a healthcare provider. Coding of 'Situation' with a terminology is preferred, where possible.
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
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 exposure situation occurred. 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 exposure situation; the interval of time during which the exposure situation occurred; the duration of the exposure situation; the age of the individual at the time of the exposure situation; 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
Interval of Date/Time- Duration
Interval of Duration- Text
- Urban
- Peri-urban
- Rural
- Planned
- Unplanned
- Piped
- Stored
- Frequent
- Infrequent
For example: the genus, subgenus or species, such as Aedes or, more specifically Aeded aegypti and Aedes albopictus.
For example: home, school, or workplace.
- Home
- Workplace/School
Calculated as (number of positive containers / number of houses inspected) * 100.
- Percent
Calculated as (number of positive containers / total number of containers inspected) * 100.
- Percent
Calculated as (number of positive containers / number of houses inspected) * 100.
- Ratio
The answers may be self-reported.
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 by choosing between the DV_TEXT or the DV_BOOLEAN datatypes to match each specific use case.
- Yes
- No
- Unknown
For example: 'Local', 'National', 'Overseas', 'Cruise ship'; or 'War zone'. Coding of the 'Investigation name' with a terminology is preferred, where possible.
- National travel
- International travel
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 choosing between the DV_TEXT or the DV_BOOLEAN datatypes to match each specific use case.
- Yes
- No
- Unknown
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 of travel; the departure and return time for the trip; the interval of time during which the individual was travelling; the duration of the trip; the age of the individual at the time of the trip; or the duration of time since the trip occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year.
Different regions within the same country maybe identified if they potentially pose different health risks.
Different cities within the same country or region maybe identified if they potentially pose different health risks.
For example: a description of accommodation, clothing worn, mosquito nets used and any potential exposure to other health risks.
For example: people or organisation visited; accommodation or a cruise ship; a building, such as a museum or conference centre, hotel; an event, such as a festival; or other location, such as a beach or sports arena. This data element has multiple occurrences to allow for more than one specific place/person to be recorded.
This may be useful if it is necessary to use contact tracing. For example: the carrier and ID of a flight or ship.
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
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.
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.
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.
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.
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
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.
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'.
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'.
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
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
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
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 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 °
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 °
For example: a location on a Google or iOS map.
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
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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)
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Personal use
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)
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Business use
For example: household, health facility,
- Yes
- No
- Unsure
- Yes
- No
- Unsure
- Up-to-date
- Up-to-date for age
- Not up-to-date
- Yes
- No
- Unsure
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
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
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
The answers may be self-reported.
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
Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations.
For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible.
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
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.
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.
For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings. In that situation, nest an appropriate CLUSTER archetype within the following 'Additional details' SLOT.
For example: Tissue or body fluid.
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}]
Optional[{fhir_mapping=Specimen.receivedTime}]
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.
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
Optional[{fhir_mapping=Specimen.note}]
For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details.
Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}]
- Positive
- Indeterminate
- Negative
- Unknown
Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details.
Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}]
- Quantity
Count- Duration
Proportion- Text
Coded Text
Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2 IgG antibody test.
Coding with an external terminology is recommended, if available. For example: infection-related IgG/IgM, IgG1 or IgG2, allergen-specific IgE; anti-dsDNA.
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2.
Coding with an external terminology is recommended, if available. For example: lateral flow immunoassay, ELISA, chemiluminescent immunoassay.
- Coded Text
- Detected
- Not detected
- Indeterminate
- Text
- QuantityUnits:
- k[iU]/L
- [iU]/mL
- Proportion
- Ratio
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2 rapid antigen test, HIV p24 Antigen ELISA, PSA chemiluminescent immunoassay, AFP ELISA, HER2/neu immunohistochemistry (IHC) test.
Coding with an external terminology is recommended, if available. For example: spike protein (SARS-CoV-2), nucleocapsid protein (SARS-CoV-2), capsid protein (HIV), lipopolysaccharides (LPS) in gram-negative bacteria, prostate-specific antigen (PSA), alpha-fetoprotein (AFP), carcinoembryonic antigen (CEA), HER2/neu, CA-125.
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2, HIV.
Coding with an external terminology is recommended, if available. For example: lateral flow immunoassay, ELISA, immunohistochemistry (IHC).
- Detected
- Not detected
- Indeterminate
Units:
- ng/mL
- k[iU]/L
For example: whole blood; urine; or CSF.
Units:
- 10*6/uL
- 10*12/L
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
- Percent
- Percent
- Percent
- Percent
- Percent
- Percent
- Growth
- No growth
For example: name of a bacteria, virus or fungus.
- Detected
- Not detected
- Indeterminate
- No growth
- Light growth
- Moderate growth
- Heavy growth
Coding with an external terminology is recommended, if available. For example: Giardia, Entamoeba, Hookworm, Toxoplasma, Plasmodium or Trypanosoma
Coding with an external terminology is recommended, if available. For example: egg, cyst, larva, trophozoite.
- Detected
- Not detected
- Indeteminate
- Coded Text
- Absent
- Scant
- Low
- Moderate
- High
- Text
For example: 2% parasitaemia detected in a blood smear.
Units: %
For example: Ziehl–Neelsen; Gram stain
- Gram stain
For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris.
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
- Detected
- Not detected
- Scant
- Low
- Moderate
- High
- Absent
For example: Ziehl–Neelsen; Gram stain
For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris.
For example: gram-positive cocci, fungi, acid-fast bacilli, cell nuclei or pathological inclusions. Coding with an external terminology is preferred, if available.
- Encapsulated microorganism
- Detected
- Not detected
- Indeterminate
- Scant
- Low
- Moderate
- High
- Absent
For example: gram-positive cocci in clusters; gram-negative bacilli, short rods; elongated fibroblasts; multinucleated giant cells; branching hyphae; oval yeast forms with budding.
For example: Ziehl–Neelsen; Gram stain
- Ziehl-Neelsen stain
For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris.
For example: gram-positive cocci, fungi, acid-fast bacilli, cell nuclei or pathological inclusions. Coding with an external terminology is preferred, if available.
- Acid-fast bacilli
- Detected
- Not detected
- Indeterminate
- Scant
- Low
- Moderate
- High
- Absent
Coding with an external terminology is recommended, if available. For example: PCR for Mycobacterium tuberculosis or SARS-CoV-2.
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2, Mycobacterium tuberculosis, or Candida albicans.
Coding with an external terminology is recommended, if available. For example: 16S rRNA gene (for bacteria), RdRp gene (for SARS-CoV-2), or ITS region (for fungi).
For example: PCR, RT-PCR, NGS, isothermal amplification.
- Detected
- Not detected
- Indeterminate
Units: copies/mL
The answers may be self-reported.
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
Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations.
For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible.
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
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.
For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings. In that situation, nest an appropriate CLUSTER archetype within the following 'Additional details' SLOT.
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'.
For example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible.
- Intramuscular
For example: 1 stat dose of prophylactic antibiotics; or 10 doses in an antibiotic course over 5 days.
Different regions within the same country maybe identified if they potentially pose different health risks.
Different cities within the same country or region maybe identified if they potentially pose different health risks.
For example: a description of accommodation, clothing worn, mosquito nets used and any potential exposure to other health risks.
For example: people or organisation visited; accommodation or a cruise ship; a building, such as a museum or conference centre, hotel; an event, such as a festival; or other location, such as a beach or sports arena. This data element has multiple occurrences to allow for more than one specific place/person to be recorded.
This may be useful if it is necessary to use contact tracing. For example: the carrier and ID of a flight or ship.
Coding of the partnership status with a terminology is preferred, where possible. There is a huge variation in the value sets used across jurisdictions. Many have local, government-mandated value sets rather than using SNOMED CT or similar. For example: a 'marital status' value set including 'never married' or 'single'; 'married'; 'divorced'; or 'widowed'. Also known as 'civil status', 'union status', or 'relationship status'.
- Married
- Visiting union
- Common law
- Single
- Widowed
- Separated
- Divorced
- Other
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
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.
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.
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.
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.
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
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
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
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'.
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'.
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
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
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
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'.
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'.
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..
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.
Also known as a postcode or ZIP code.
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
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)
For example: area code + landline phone/pager number; country code + mobile phone number; or email address.
- Business use
- Personal use
- Both business and personal use
Coding with a terminology is desirable, where possible. For example: the ISCED classification, such as upper secondary vocational education; post-secondary non-tertiary vocational education; Bachelor’s or equivalent level, professional; Doctoral or equivalent level, academic; post-secondary non-tertiary vocational education; or never attended an educational program.
- No formal schooling
- Basic
- Primary/All Age/Preparatory
- Secondary/High School
- Tertiary/Post-secondary
- Vocational skills training
- Other
For example: employed; unemployed; or not in labour force. Coding with a terminology is desirable, where possible. Detail about each occupation can be recorded within the CLUSTER.occupation_record archetype.
- Employed
- Unemployed
- Unknown
For example: Chief Executive Officer; Carer; or Student. Each of these job titles or roles may be comprised of multiple duties.
- Armed Forces Occupations (All Ranks)
- Soldier
- Custos
- Governor General
- Leader, Opposition (Governmental)
- Opposition Leader
- Prime Minister
- Cabinet Minister
- Constituency Representative
- Government Minister
- Member of Parliament
- Minister, Cabinet
- Minister, Government
- Minister, Opposition
- MP
- Opposition Minister
- Senator
- Attorney General
- Solicitor General
- Public Defender
- Ombudsman, Political
- Political Ombudsman
- Chief Parliamentary Counsel
- Legislators n.e.c.
- Civil Service Commissioner
- Commissioner, Civil Service
- Financial Secretary
- Head, Civil Service Commission
- Permanent Secretary
- Secretary, Financial
- Secretary, Permanent
- Chief Executive Officer (Governmental Department/Agency)
- and MORE
- [...]
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
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'.
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'.
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
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
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
This information will provide a sense of the level of support, both physically and emotionally, to which an individual may have access.
Coding of the living arrangement with a terminology is preferred, where possible. The value sets for this data element are likely to vary between jurisdictions - it is anticipated that they will usually be set within a use-case specific template. For example: 'lives alone'; 'lives with family'; or 'lives with others'.
- Lives alone
- Lives with partner
- Lives with family
- Lives with friends
The intended scope of dwelling includes, but is not limited to: a building; part of a building; house; apartment; prison; houseboat; mobile home; or vehicle. It can also include the spaces associated with a structure or property, including the basement or yard.
Coding of the dwelling type with a terminology is preferred, where possible. The value sets for this data element are likely to vary between jurisdictions - it is anticipated that they will usually be set within a use-case specific template. For example: 'separate house'; 'flat, unit or apartment'; 'caravan or tent'; or 'house or flat attached to a shop or office'.
- Separate house (detached)
- Apartment building
- Townhouse
- Other attached
- Part of commercial building
- Improvised housing unit
- Other
- [...]
The number of people in the household will be a subset of the people living in a shared dwelling.
>=0
While this data element will usually record the number of people sleeping in the room where the index patient sleeps, this data element has multiple occurrences to allow for more than one bedroom to be recorded, if necessary.
>=0
Multiple occurrences will allow details for each water supply to be recorded. For example: piped water (in house); stand pipe; or yard pipe.
For example: Adequate or Inadequate.
The definition of an available, or habitable, 'room' varies enormously. In some jurisdictions it refers to the number of available bedrooms, but often needs a broader definition. In most situations definitions exclude the kitchen, bathrooms, balconies, porches, foyers, hall-ways and half-rooms. In a shared dwelling containing more than one household, the number of rooms available to a household will be a subset of the total number of rooms within the dwelling.
>=0
In most situations, this will be assessed as the number of household members per room that can be used for sleeping.
>=0
The answers may be self-reported.
For example: Admitted to hospital; Admitted to ICU; Use of compression stockings; Daily dressings; ECMO. Coding of the 'Management name' with a terminology is preferred, where possible.
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
The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the management activity may have occurred. The specific and intended semantics can be further clarified in a template. For example: the actual point in time when, or interval during which, an activity took place; the start and stop time of an activity; the duration of the activity; the age of the individual at the time of the activity; or the duration of time since the activity occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year.
The answers may be self-reported.
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
Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations.
For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible.
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
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.
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.
For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings. In that situation, nest an appropriate CLUSTER archetype within the following 'Additional details' SLOT.
For example: Tissue or body fluid.
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}]
Optional[{fhir_mapping=Specimen.receivedTime}]
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.
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
Optional[{fhir_mapping=Specimen.note}]
For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details.
Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}]
- Positive
- Indeterminate
- Negative
- Unknown
Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details.
Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}]
- Quantity
- Count
- Duration
- Proportion
- Text
- Coded Text
Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2 IgG antibody test.
Coding with an external terminology is recommended, if available. For example: infection-related IgG/IgM, IgG1 or IgG2, allergen-specific IgE; anti-dsDNA.
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2.
Coding with an external terminology is recommended, if available. For example: lateral flow immunoassay, ELISA, chemiluminescent immunoassay.
- Coded Text
- Detected
- Not detected
- Indeterminate
- Text
- QuantityUnits:
- k[iU]/L
- [iU]/mL
- Proportion
- Ratio
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2 rapid antigen test, HIV p24 Antigen ELISA, PSA chemiluminescent immunoassay, AFP ELISA, HER2/neu immunohistochemistry (IHC) test.
Coding with an external terminology is recommended, if available. For example: spike protein (SARS-CoV-2), nucleocapsid protein (SARS-CoV-2), capsid protein (HIV), lipopolysaccharides (LPS) in gram-negative bacteria, prostate-specific antigen (PSA), alpha-fetoprotein (AFP), carcinoembryonic antigen (CEA), HER2/neu, CA-125.
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2, HIV.
Coding with an external terminology is recommended, if available. For example: lateral flow immunoassay, ELISA, immunohistochemistry (IHC).
- Detected
- Not detected
- Indeterminate
Units:
- ng/mL
- k[iU]/L
For example: whole blood; urine; or CSF.
Units:
- 10*6/uL
- 10*12/L
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
Units:
- 10⁹/L
- 10*3/uL
- 1/[HPF]
- Percent
- Percent
- Percent
- Percent
- Percent
- Percent
- Growth
- No growth
For example: name of a bacteria, virus or fungus.
- Detected
- Not detected
- Indeterminate
- No growth
- Light growth
- Moderate growth
- Heavy growth
Coding with an external terminology is recommended, if available. For example: Giardia, Entamoeba, Hookworm, Toxoplasma, Plasmodium or Trypanosoma
Coding with an external terminology is recommended, if available. For example: egg, cyst, larva, trophozoite.
- Detected
- Not detected
- Indeteminate
- Coded Text
- Absent
- Scant
- Low
- Moderate
- High
- Text
For example: 2% parasitaemia detected in a blood smear.
Units: %
For example: Ziehl–Neelsen; Gram stain
- Gram stain
For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris.
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
- Detected
- Not detected
- Scant
- Low
- Moderate
- High
- Absent
For example: Ziehl–Neelsen; Gram stain
For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris.
For example: gram-positive cocci, fungi, acid-fast bacilli, cell nuclei or pathological inclusions. Coding with an external terminology is preferred, if available.
- Encapsulated microorganism
- Detected
- Not detected
- Indeterminate
- Scant
- Low
- Moderate
- High
- Absent
For example: gram-positive cocci in clusters; gram-negative bacilli, short rods; elongated fibroblasts; multinucleated giant cells; branching hyphae; oval yeast forms with budding.
For example: Ziehl–Neelsen; Gram stain
- Ziehl-Neelsen stain
For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris.
For example: gram-positive cocci, fungi, acid-fast bacilli, cell nuclei or pathological inclusions. Coding with an external terminology is preferred, if available.
- Acid-fast bacilli
- Detected
- Not detected
- Indeterminate
- Scant
- Low
- Moderate
- High
- Absent
Coding with an external terminology is recommended, if available. For example: PCR for Mycobacterium tuberculosis or SARS-CoV-2.
Coding with an external terminology is recommended, if available. For example: SARS-CoV-2, Mycobacterium tuberculosis, or Candida albicans.
Coding with an external terminology is recommended, if available. For example: 16S rRNA gene (for bacteria), RdRp gene (for SARS-CoV-2), or ITS region (for fungi).
For example: PCR, RT-PCR, NGS, isothermal amplification.
- Detected
- Not detected
- Indeterminate
Units: copies/mL
The answers may be self-reported.
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
Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations.
For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible.
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
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.
For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings. In that situation, nest an appropriate CLUSTER archetype within the following 'Additional details' SLOT.
The answers may be self-reported.
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
Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations.
For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible.
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.
- Coded Text
- Yes
- No
- Unknown
- Text
Boolean
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
- Text
- Interval of Date/Time
- Interval of Duration
- Duration
For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings. In that situation, nest an appropriate CLUSTER archetype within the following 'Additional details' SLOT.
A test result may be for a single analyte, or a group of items, including panel tests. It is strongly recommended that 'Test name' be coded with a terminology, for example LOINC or SNOMED CT. For example: 'Glucose', 'Urea and Electrolytes', 'Swab', 'Cortisol (am)', 'Potassium in perspiration' or 'Melanoma histopathology'. The name may sometimes include specimen type and patient state, for example 'Fasting blood glucose' or include other information, as 'Potassium (PNA blood gas)'.
For example: Tissue or body fluid.
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}]
Optional[{fhir_mapping=Specimen.receivedTime}]
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.
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
Optional[{fhir_mapping=Specimen.note}]
For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details.
Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}]
- Positive
- Indeterminate
- Negative
- Unknown
Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details.
Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}]
- Quantity
- Count
- Duration
- Proportion
- Text
- Coded Text
Optional[{fhir_mapping=Observation.note, hl7v2_mapping=NTE.3}]
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
- National Public Health Laboratory (NPHL)
- CARPHA
- National Influenza Centre (NIC)
- UHWI/UWI
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.
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.
For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'.
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.
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'.
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'.
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
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
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
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.
Equivalent to ImagingStudy.started in FHIR.
Also referred to as 'Opinion' or 'Conclusion'. Equivalent to DiagnosticReport.conclusion in FHIR.
For example: a note that the film was given to the patient. Equivalent to DiagnosticReport.note in FHIR.
For example: completed or not completed.
- Completed
- Not completed
- Cured
- Treatment failure
- Lost to followup
- Died
- Not evaluated
May be useful, for example, when the individual is lost to follow-up.
It is recommended that 'Finding' should be coded with a terminology, where possible.
For example: The date when the finding was made by or made available to the clinician.
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
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'.
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'.
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'.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
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').
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.
It is recommended that 'Cause' be coded with an external terminology.
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.
It is recommended that 'Cause' be coded with an external terminology.
It is recommended that 'Condition' be coded with an external terminology.
This data element may be redundant if the index disease has been identified elsewhere within a template.
Not to be used to record the 'Initial classification' at the initiation of a case investigation.
- Pending
- Probable
- Laboratory confirmed
- Clinically confirmed
- Discarded
- Inconclusive
For example: lost to follow-up, child of an infected mother.
- Text
- Coded Text
- Animal to human transmission
- Exposure to a common source
- Exposure to contaminated food/drinking water
- Environmental exposure
- Laboratory exposure
- Human to human transmission
For example: imported, import-related, endemic, vaccine-associated, congenital or unknown.
- Text
- Coded Text
- Imported case
- Import-related case
- Endemic case
- Vaccine-associated case
- Congenital case
- Unknown
For example: household contact, community, or unknown.
- Text
- Coded Text
- Related
- Unrelated
- Unknown
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'.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
This data element may be redundant if the index disease has been identified elsewhere within a template.
Not to be used to record the 'Initial classification' at the initiation of a case investigation.
- Pending
- Probable
- Laboratory confirmed
- Clinically confirmed
- Discarded
- Inconclusive
For example: lost to follow-up, child of an infected mother.
- Text
- Coded Text
- Animal to human transmission
- Exposure to a common source
- Exposure to contaminated food/drinking water
- Environmental exposure
- Laboratory exposure
- Human to human transmission
For example: imported, import-related, endemic, vaccine-associated, congenital or unknown.
- Text
- Coded Text
- Imported case
- Import-related case
- Endemic case
- Vaccine-associated case
- Congenital case
- Unknown
For example: household contact, community, or unknown.
- Text
- Coded Text
- Related
- Unrelated
- Unknown