| TEMPLATE ID | Ophthalmia neonatorum case investigation form |
|---|---|
| Concept | Ophthalmia neonatorum case investigation form |
| Description | Not Specified |
| Purpose | Not Specified |
| References | |
| Authors | name: Heather Leslie; organisation: Atomica Informatics; email: heather.leslie@atomicainformatics.com; date: 2023-09-04 |
| Other Details Language | name: Heather Leslie; organisation: Atomica Informatics; email: heather.leslie@atomicainformatics.com; date: 2023-09-04 |
| Other Details (Language Independent) |
|
| Language used | en |
| Citeable Identifier | 1013.26.1037 |
| Root archetype id | openEHR-EHR-COMPOSITION.report.v1 |
| 2024 12 29 Ophthalmia neonatorum case investigation form | 2024 12 29 Ophthalmia neonatorum case investigation form: Document to communicate information to others, commonly in response to a request from another party. |
| Infectious disease investigation metadata | Infectious disease investigation metadata: Infectious disease investigation metadata. |
| Data | Data: * |
| Notified disease | Notified disease: The name of the disease under investigation.
|
| Notification ID | Notification ID: The unique identifier for the notification that triggered this infectious disease investigation. The investigation ID and the notification ID may be identical if both the notification and investigation are carried out within the same system. |
| Investigation ID | Investigation ID: The unique identifier for this infectious disease investigation. The investigation ID and the notification ID may be identical if both the notification and investigation are carried out within the same system. |
| Date identified | Date identified: The date when the infection was first identified by a clinician or notifier. |
| Epidemiological week of onset | Epidemiological week of onset: Standardised way to identify the week of onset of symptoms. Also known as 'epi week'. |
| Epidemiological week of notification | Epidemiological week of notification: Standardised way to identify the week of notification to public health authorities. Also known as 'epi week'. |
| Date of notification | Date of notification: Details about the person who notified public health authorities about the infectious disease case. |
| Person - notifying individual | Person - notifying individual: An individual human being. |
| Structured name of a person - core | Structured name of a person - core: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'.
|
| Professional license number | Professional license number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Professional group | Professional group: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant.
|
| Position | Position: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Healthcare facility | Healthcare facility: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name | Name: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Identifier | Identifier: Identifier associated with the organisation. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the ID data type contains multiple subcomponents for recording the ID value, type, issuer and assigner. |
| Address - local | Address - local: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Detection method | Detection method: Method of detection of the index disease. |
| Person - investigating officer | Person - investigating officer: An individual human being. |
| Structured name of a person - core | Structured name of a person - core: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'.
|
| Professional license number | Professional license number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Professional group | Professional group: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Position | Position: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Organisation | Organisation: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name | Name: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Date investigation initiated | Date investigation initiated: The date when the investigator commenced the investigation. |
| Person - clinician | Person - clinician: An individual human being. |
| Structured name of a person - core | Structured name of a person - core: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'.
|
| Professional license number | Professional license number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Professional group | Professional group: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Position | Position: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Organisation | Organisation: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name | Name: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Healthcare facility | Healthcare facility: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name | Name: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Identifier | Identifier: Identifier associated with the organisation. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the ID data type contains multiple subcomponents for recording the ID value, type, issuer and assigner. |
| Address - local | Address - local: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Date investigation completed | Date investigation completed: The date when the investigator finished the investigation report. |
| Date submitted to MO(H) | Date submitted to MO(H): The date when the investigator submitted the investigation report for review. |
| MO(H) sign off | MO(H) sign off: Details about review, sign off or approval by local or regional clinical authorities. |
| Date received for review | Date received for review: The date when the reviewer received the investigation for review. |
| Person - public health official | Person - public health official: An individual human being. |
| Structured name of a person - core | Structured name of a person - core: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'.
|
| Professional license number | Professional license number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Professional group | Professional group: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Position | Position: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant. |
| Organisation | Organisation: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name | Name: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Parish | Parish: Name of the local health region. |
| Comment | Comment: Narrative description about the investigation report. |
| Date review completed | Date review completed: The date when the reviewer completed the review of the investigation. |
| Date submitted to NSU | Date submitted to NSU: The date on which the investigation was submitted to public health authorities. |
| Infant profile | Infant profile: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Case demographic information | Case demographic information: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Child demographics | Child demographics: A container archetype used to hold demographic-related EHR CLUSTER archetypes. |
| Data | |
| Person - child patient | Person - child patient: An individual human being. |
| Structured name of a person - full | Structured name of a person - full: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Middle name | Middle name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Nickname | Nickname: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'.
|
| Medical Record Number (MRN) | Medical Record Number (MRN): Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Jamaica Digital Health ID | Jamaica Digital Health ID: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| National Identification Number (NIN) | National Identification Number (NIN): Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Birth certificate number | Birth certificate number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Student Registration Number | Student Registration Number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Taxpayer Registration Number (TRN) | Taxpayer Registration Number (TRN): Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Drivers licence | Drivers licence: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Passport number | Passport number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| National Insurance Scheme Number | National Insurance Scheme Number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Address - Local + GIS | Address - Local + GIS: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Geolocation code | Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash. |
| Latitude | Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° |
| Longitude | Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° |
| Map URL | Map URL: Link to a location on an online map. For example: a location on a Google or iOS map. |
| Phone - home landline | Phone - home landline: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template.
|
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication.
|
| Phone - personal mobile | Phone - personal mobile: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template.
|
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication.
|
| Email: Details about a specified type of electronic communication. | |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Comment | Comment: Additional narrative about the electronic communication not captured in other fields. |
| Person - nameless infant patient | Person - nameless infant patient: An individual human being. |
| Label | Label: A label for the individual. For example: 'Neighbour in the house with the red door'.
|
| Structured name of woman - full + maiden | Structured name of woman - full + maiden: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Middle name | Middle name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Nickname | Nickname: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Maiden name | Maiden name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Medical Record Number (MRN) | Medical Record Number (MRN): Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Jamaica Digital Health ID | Jamaica Digital Health ID: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Address - Local + GIS | Address - Local + GIS: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Geolocation code | Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash. |
| Latitude | Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° |
| Longitude | Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° |
| Map URL | Map URL: Link to a location on an online map. For example: a location on a Google or iOS map. |
| Phone - home landline | Phone - home landline: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template.
|
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication.
|
| Phone - personal mobile | Phone - personal mobile: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template.
|
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication.
|
| Email: Details about a specified type of electronic communication. | |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Comment | Comment: Additional narrative about the electronic communication not captured in other fields. |
| Date of birth | Date of birth: Overview or summary record of the pregnancy and birth of an individual. |
| Data | |
| Date of birth | Date of birth: The date/time of birth of the individual. May also be used to record the assumed or agreed date/time of birth for operational purposes, if the actual date/time is not formally recorded. Possible alternatives for the date/time of birth of the individual can be recorded using the CLUSTER.DOB_alternative archetype 'Date of birth details' SLOT. Partial dates are allowed. |
| Place of birth | Place of birth: Simple representation about the place of birth. This data element provides the opportunity for simple detail about the place of birth, such as the city, region, town, or suburb within the identified 'Country of birth'. For example: Kingston (Jamaica); Manhattan (USA); or Box Hill (Australia). |
| Age assertion - infant | Age assertion - infant: A statement about the age of an individual at a point in time. |
| Data | |
| Point in time event | Point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time. |
| Data | |
| Chronological age | Chronological age: The age of an individual at the event time, calculated from date of birth. In most use cases the DV_DURATION data type is used to record the Chronological age. The DV_INTERVAL_DURATION is used for recording a structured age interval in cases where there's uncertainty about the individual's exact age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days). The DV_TEXT data type is used for recording a textual representation of the individual's age, or age category often found in questionnaires. For example: 'P3M2W', '0,2884615384615385 a_j', '3 months 2 weeks' or '31-40 years' or 'Teenager'. PT1H..P51W |
| Sex & gender - newborn | Sex & gender - newborn: Details about the gender of an individual. |
| Data | |
| Sex assigned at birth | Sex assigned at birth: The sex of an individual determined by anatomical characteristics observed and registered at birth. For example: 'Male', 'Female', 'Intersex'. Coding with a terminology is recommended, where possible. Use the element 'Comment' or the SLOT 'Details' if needed to register more specific details of the individuals gender.
|
| Clinical profile | Clinical profile: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Clinical screening | Clinical screening: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Symptom/sign screening | Symptom/sign screening: Series of questions and associated answers used to screen for symptoms or signs. The answers may be self-reported. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Onset of illness | Onset of illness: Timing of the inital recognition of any symptom or sign relevant for the screening purpose. The 'Onset' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture the onset of symptoms or signs. The specific and intended semantics can be further clarified in a template. For example: Date/time for the date the symptom started. Interval of date/time for a period of time eg. between 1940 and 1942. Text for descriptions like 'Immediately after the operation', or 'Up to one week ago', 'Up to two weeks ago', 'Three weeks ago'. Duration for the individual's age at the onset. Interval of Duration for the approximate age of the individual at the time of onset. |
| Specific symptom/sign | Specific symptom/sign: Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose. |
| Symptom/sign name | Symptom/sign name: Identification of a specific symptom or sign or grouping of symptoms or signs, by name. Coding of the 'Symptom/sign name' with a terminology is preferred, where possible.
|
| Presence? | Presence?: Is there a history of the specific symptom or sign being present? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Date of onset | Date of onset: Indication of timing related to the specific symptom or sign. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the specific symptom or sign occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. |
| Other symptom/sign | Other symptom/sign: Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose. |
| Symptom/sign name | Symptom/sign name: Identification of a specific symptom or sign or grouping of symptoms or signs, by name. Coding of the 'Symptom/sign name' with a terminology is preferred, where possible. |
| Presence? | Presence?: Is there a history of the specific symptom or sign being present? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Date of onset | Date of onset: Indication of timing related to the specific symptom or sign. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the specific symptom or sign occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. |
| Clinical management | Clinical management: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Antibiotic prophylaxis screening | Antibiotic prophylaxis screening: Series of questions and associated answers used to screen for the use of medications. The answers may be self-reported. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Any prophylaxis given? | Any prophylaxis given?: Is there a history of use of any medication related to the screening purpose? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Antibiotic prophylaxis | Antibiotic prophylaxis: An assertion about the current use of a single medication by an individual. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Antibiotic name | Antibiotic name: Name of the medication. It is strongly recommended that the 'Medication name' be coded with a terminology capable of triggering decision support, where possible. Free text entry should only be used if there is no appropriate terminology available or for customised extemporaneous preparations. The extent of coding may vary from the simple generic or product name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. For example: 'Plaquenil'; 'Ibrutinib 420 mg tablet'; 'Rectinol ointment, 50 g, tube'; or 'Hydrofibre dressing with silver'. |
| Dose and timing | Dose and timing: Complete narrative description about how the ordered item is to be used. |
| Route of administration | Route of administration: The route by which the medication is administrated into the body. For example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible. |
| Other medication | Other medication: An assertion about the current use of a single medication by an individual. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Medication name | Medication name: Name of the medication. It is strongly recommended that the 'Medication name' be coded with a terminology capable of triggering decision support, where possible. Free text entry should only be used if there is no appropriate terminology available or for customised extemporaneous preparations. The extent of coding may vary from the simple generic or product name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. For example: 'Plaquenil'; 'Ibrutinib 420 mg tablet'; 'Rectinol ointment, 50 g, tube'; or 'Hydrofibre dressing with silver'. |
| Dose and timing | Dose and timing: Complete narrative description about how the ordered item is to be used. |
| Route of administration | Route of administration: The route by which the medication is administrated into the body. For example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible.
|
| Comment | Comment: Additional narrative about the medication statement not captured in other fields. |
| First administered | First administered: The date and time when the medication was first taken by, or administered to, the individual. |
| Number of doses administered | Number of doses administered: The total number of doses administered. For example: 1 stat dose of prophylactic antibiotics; or 10 doses in an antibiotic course over 5 days. |
| Laboratory test screening | Laboratory test screening: Series of questions and associated answers used to screen whether diagnostic investigations have been carried out. The answers may be self-reported. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Specimen taken? | Specimen taken?: Is there a history of any diagnostic tests or investigations related to the screening purpose? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Eye swab specimen | Eye swab specimen: Details about a specified investigation or grouping of investigations relevant for the screening purpose. Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations. |
| Test name | Test name: Name of the diagnostic investigation or grouping of investigations. For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible. |
| Done? | Done?: Is there a history of the investigation being carried out? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Date/time sent to laboratory | Date/time sent to laboratory: Indication of timing related to the investigation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an investigation was carried out. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the investigation; the interval of time during which the investigation was carried out; the duration of the investigation; the age of the individual at the time of the investigation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. |
| Date/time result reported | Date/time result reported: Indication of timing related to the investigation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an investigation was carried out. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the investigation; the interval of time during which the investigation was carried out; the duration of the investigation; the age of the individual at the time of the investigation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. |
| Specimen collection details | Specimen collection details: A physical sample collected from, or related to, an individual for the purpose of investigation, examination or analysis. For example: Tissue or body fluid. |
| Specimen type | Specimen type: The type of specimen. For example: Venous blood, bacterial culture, cytology, or tissue sample. Coding of the specimen type with a terminology is preferred, where possible. Optional[{fhir_mapping=Specimen.type}]
|
| Date/time received by laboratory | Date/time received by laboratory: The date and time that the sample was received at the laboratory. Optional[{fhir_mapping=Specimen.receivedTime}] |
| Date/time collected | Date/time collected: The date and time that collection has been ordered to take place or has taken place. This datetime will be captured primarily in the INSTRUCTION timing, ACTION time or OBSERVATION times. However, as this is a critical piece of information, it can be useful to also associate it directly with the specimen itself. |
| Adequacy for testing | Adequacy for testing: Information about whether the specimen was adequate for testing. This element is intended to be used to record a judgement about whether or not the specimen quality was good enough for testing, and whether or not testing has been carried out. Coding of the specimen quality issues with a terminology is preferred, where possible.
|
| Gram stain findings | Gram stain findings: Findings observed during microscopic examination of tissue treated with specialised stains, intended to enhance the visualisation of specimen, including microorganisms, tissue structures and cellular details. |
| Staining method | Staining method: Name of the technique used to stain the specimen. For example: Ziehl–Neelsen; Gram stain
|
| Clinical findings | Clinical findings: Narrative description about the findings observed using the identified stain. For example: an overall description; the presence of non-targeted findings such as epithelial cells or debris. |
| Per target finding | Per target finding: Details about a specific microorganism, tissue structure, or cell structure observed during the microscopic examination of a stained specimen. |
| Staining target | Staining target: Identification of the target organism, cell or structure. For example: gram-positive cocci, fungi, acid-fast bacilli, cell nuclei or pathological inclusions. Coding with an external terminology is preferred, if available.
|
| Presence | Presence: Statement about detection of the staining target in the specimen.
|
| Qualitative result | Qualitative result: Qualitative assessment of the amount of the target organism, cell, or structure observed using the stain.
|
| Comment | Comment: Additional narrative about the target findings using the identified stain, not captured in other fields. |
| Microbiology culture findings | Microbiology culture findings: Findings observed from culturing a specimen to detect and identify the growth of microorganisms. |
| Overall growth | Overall growth: Statement about the presence or absence of any microbial growth on culture.
|
| Per microorganism | Per microorganism: Details about specific culture findings for each identified organism. |
| Microorganism name | Microorganism name: Name of the microorganism cultured. For example: name of a bacteria, virus or fungus. |
| Growth | Growth: Observation about the presence or absence of growth of the identified organism on culture.
|
| Qualitative result | Qualitative result: Qualitative assessment of the amount of the identified microorganism grown on culture.
|
| Comment | Comment: Additional narrative about the culture findings for the identified microorganism, not captured in other fields. |
| Blood specimen | Blood specimen: Details about a specified investigation or grouping of investigations relevant for the screening purpose. Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations. |
| Test name | Test name: Name of the diagnostic investigation or grouping of investigations. For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible. |
| Done? | Done?: Is there a history of the investigation being carried out? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Date/time sent to laboratory | Date/time sent to laboratory: Indication of timing related to the investigation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an investigation was carried out. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the investigation; the interval of time during which the investigation was carried out; the duration of the investigation; the age of the individual at the time of the investigation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. |
| Date/time result reported | Date/time result reported: Indication of timing related to the investigation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an investigation was carried out. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the investigation; the interval of time during which the investigation was carried out; the duration of the investigation; the age of the individual at the time of the investigation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. |
| Specimen collection details | Specimen collection details: A physical sample collected from, or related to, an individual for the purpose of investigation, examination or analysis. For example: Tissue or body fluid. |
| Specimen type | Specimen type: The type of specimen. For example: Venous blood, bacterial culture, cytology, or tissue sample. Coding of the specimen type with a terminology is preferred, where possible. Optional[{fhir_mapping=Specimen.type}]
|
| Date/time received by laboratory | Date/time received by laboratory: The date and time that the sample was received at the laboratory. Optional[{fhir_mapping=Specimen.receivedTime}] |
| Date/time collected | Date/time collected: The date and time that collection has been ordered to take place or has taken place. This datetime will be captured primarily in the INSTRUCTION timing, ACTION time or OBSERVATION times. However, as this is a critical piece of information, it can be useful to also associate it directly with the specimen itself. |
| Adequacy for testing | Adequacy for testing: Information about whether the specimen was adequate for testing. This element is intended to be used to record a judgement about whether or not the specimen quality was good enough for testing, and whether or not testing has been carried out. Coding of the specimen quality issues with a terminology is preferred, where possible.
|
| Molecular microbial test findings | Molecular microbial test findings: The result of a laboratory test for the detection and identification of specific micro-organism DNA or RNA in a specimen, using nucleic acid probes. |
| Test name | Test name: Name of the molecular test carried out. Coding with an external terminology is recommended, if available. For example: PCR for Mycobacterium tuberculosis or SARS-CoV-2. |
| Microbial target | Microbial target: The name of the microorganism being detected. Coding with an external terminology is recommended, if available. For example: SARS-CoV-2, Mycobacterium tuberculosis, or Candida albicans. |
| Presence | Presence: Statement about detection of the identified microorganism in the specimen.
|
| Quantitative result | Quantitative result: Quantitative assessment of the amount of the identified microorganism in the specimen. Units: copies/mL |
| Comment | Comment: Additional narrative about the test finding not captured in other fields. |
| Clinical notes | Clinical notes: Narrative summary or overview about a patient, specifically from the perspective of a healthcare provider, and with or without associated interpretations. |
| Data | |
| Clinical notes | Clinical notes: The summary, assessment, conclusions or evaluation of the clinical findings. |
| Maternal profile | Maternal profile: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Parent demographic information | Parent demographic information: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Name | Name: A container archetype used to hold demographic-related EHR CLUSTER archetypes. |
| Data | |
| Person - mother | Person - mother: An individual human being. |
| Structured name of woman - full + maiden | Structured name of woman - full + maiden: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Middle name | Middle name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Nickname | Nickname: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Maiden name | Maiden name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Medical record number | Medical record number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Relationship | Relationship: The relationship or role of the individual to the subject of the health record. For example - the copyholder of an advance care record; contact person in an organisation; relative in a family history entry; specimen collector; or witness to a fall or accident. If the individual being described using this archetype is the subject of the health record, then this data element is redundant.
|
| Address - local | Address - local: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Address - international | Address - international: Details about the location of a person, physical building or landmark. |
| Address line | Address line: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| City/Town | City/Town: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'. |
| District/County | District/County: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica.. |
| State/Territory/Province | State/Territory/Province: The name of a major government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'New South Wales' and 'Queensland' in Australia; 'British Columbia' and 'Nova Scotia' in Canada; and the Counties of 'Cornwall', 'Middlesex' & 'Surrey' in Jamaica. |
| Postal code | Postal code: The code for a postal delivery area containing the address, as defined by the relevant postal delivery service. Also known as a postcode or ZIP code. |
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Phone - unspecified number/s | Phone - unspecified number/s: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template.
|
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication.
|
| Date of birth | Date of birth: Overview or summary record of the pregnancy and birth of an individual. |
| Data | |
| Date of birth | Date of birth: The date/time of birth of the individual. May also be used to record the assumed or agreed date/time of birth for operational purposes, if the actual date/time is not formally recorded. Possible alternatives for the date/time of birth of the individual can be recorded using the CLUSTER.DOB_alternative archetype 'Date of birth details' SLOT. Partial dates are allowed. |
| Age assertion | Age assertion: A statement about the age of an individual at a point in time. |
| Data | |
| Point in time event | Point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time. |
| Data | |
| Chronological age | Chronological age: The age of an individual at the event time, calculated from date of birth. In most use cases the DV_DURATION data type is used to record the Chronological age. The DV_INTERVAL_DURATION is used for recording a structured age interval in cases where there's uncertainty about the individual's exact age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days). The DV_TEXT data type is used for recording a textual representation of the individual's age, or age category often found in questionnaires. For example: 'P3M2W', '0,2884615384615385 a_j', '3 months 2 weeks' or '31-40 years' or 'Teenager'. P1M..P200Y Units:
|
| Occupation summary | Occupation summary: Summary or persistent information about an individual's current and past jobs and/or roles. |
| Data | |
| Employment status | Employment status: Statement about the individual's current employment. For example: employed; unemployed; or not in labour force. Coding with a terminology is desirable, where possible. Detail about each occupation can be recorded within the CLUSTER.occupation_record archetype.
|
| Occupation record | Occupation record: A single job or role carried out by an individual during a specified period of time. |
| Occupation | Occupation: The main job title or the role of the individual. For example: Chief Executive Officer; Carer; or Student. Each of these job titles or roles may be comprised of multiple duties.
|
| Employer/School | Employer/School: An entity comprising one or more people and having a particular purpose. For example: a company, institution, association, network, department, community group, healthcare practice group, payer/insurer, care team, or a group of neighbours who provide care or support. |
| Name of Employer/School | Name of Employer/School: The unstructured name or label for the organisation. For example: 'Royal Children's Hospital'; 'ABC District Nursing Service'; 'YNWA Oslo' or 'JB Smith Lawyers'. |
| Address - local | Address - local: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Clinical profile | Clinical profile: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Obstetric summary | Obstetric summary: Summary or persistent information about the numbers of key obstetric events. |
| Data | |
| Gravidity | Gravidity: Number of times a woman has been pregnant, current and past, regardless of the pregnancy outcome. Clinical systems might represent this data element by the term 'Gravida' on a clinical form. 0..100 |
| Parity | Parity: Number of times a woman has given birth to a viable baby, regardless of the pregnancy outcome. Parity includes all pregnancies that are carried after the fetus is considered viable, as defined in the 'Definition of viability data' element. Stillbirths, late abortions, and all live births are included in the assessment of Parity. In cases of multiple pregnancies, parity is only increased with birth of the last fetus. 0..100 |
| Preterm births | Preterm births: Number of births before term. The definition of a preterm birth is a viable birth before 37 weeks of gestation. 0..100 |
| Miscarriages | Miscarriages: Number of times a woman has had a miscarriage. The definition of viability can be recorded in the Protocol. 0..100 |
| Live births | Live births: Number of infants born alive. 0..100 |
| Stillbirths | Stillbirths: Number of stillbirths. The definition of viability can be recorded in the Protocol. 0..100 |
| Pregnancy care summary | Pregnancy care summary: Summary details about the antenatal and postnatal care received during a single pregnancy. |
| Data | |
| No antenatal care | No antenatal care: * |
| Overall funding type | Overall funding type: Source of funding for all pregnancy care.
|
| Total number of antenatal visits | Total number of antenatal visits: Total number of antenatal clinic visits of all types and locations for the pregnancy overall. |
| Total number of postnatal admissions | Total number of postnatal admissions: * |
| Symptom/sign screening | Symptom/sign screening: Series of questions and associated answers used to screen for symptoms or signs. The answers may be self-reported. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Specific symptom/sign | Specific symptom/sign: Details about a specific symptom or sign or grouping of symptoms or signs relatevant for the screening purpose. |
| Symptom/sign name | Symptom/sign name: Identification of a specific symptom or sign or grouping of symptoms or signs, by name. Coding of the 'Symptom/sign name' with a terminology is preferred, where possible.
|
| Presence? | Presence?: Is there a history of the specific symptom or sign being present? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Date of onset | Date of onset: Indication of timing related to the specific symptom or sign. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when the specific symptom or sign occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the specific symptom or sign; the interval of time during which the specific symptom or sign occured; the duration of the specific symptom or sign; the age of the individual at the time of the specific symptom or sign occured; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. |
| Medication screening questionnaire | Medication screening questionnaire: Series of questions and associated answers used to screen for the use of medications. The answers may be self-reported. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Any treatment given in pregnancy? | Any treatment given in pregnancy?: Is there a history of use of any medication related to the screening purpose? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Medication use statement - JM | Medication use statement - JM: An assertion about the current use of a single medication by an individual. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Medication name | Medication name: Name of the medication. It is strongly recommended that the 'Medication name' be coded with a terminology capable of triggering decision support, where possible. Free text entry should only be used if there is no appropriate terminology available or for customised extemporaneous preparations. The extent of coding may vary from the simple generic or product name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. For example: 'Plaquenil'; 'Ibrutinib 420 mg tablet'; 'Rectinol ointment, 50 g, tube'; or 'Hydrofibre dressing with silver'. |
| Dose and timing | Dose and timing: Complete narrative description about how the ordered item is to be used. |
| Route of administration | Route of administration: The route by which the medication is administrated into the body. For example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible.
|
| Comment | Comment: Additional narrative about the medication statement not captured in other fields. |
| First administered | First administered: The date and time when the medication was first taken by, or administered to, the individual. |
| Number of doses administered | Number of doses administered: The total number of doses administered. For example: 1 stat dose of prophylactic antibiotics; or 10 doses in an antibiotic course over 5 days. |
| Additional notes | Additional notes: Narrative summary or overview about a patient, specifically from the perspective of a healthcare provider, and with or without associated interpretations. |
| Data | |
| Additional notes | Additional notes: The summary, assessment, conclusions or evaluation of the clinical findings. |
| Field investigator classification | Field investigator classification: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Field diagnosis | Field diagnosis: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual. Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'. |
| Data | |
| Diagnosis name | Diagnosis name: Identification of the problem or diagnosis, by name. Coding of the name of the problem or diagnosis with a terminology is preferred, where possible. |
| Field classification | Field classification: Classification for an identified infectious disease as part of a disease surveillance investigation. |
| Data | |
| Index disease | Index disease: The name of the infectious disease under investigation. This data element may be redundant if the index disease has been identified elsewhere within a template.
|
| Final classification | Final classification: Classification of the likelihood of the 'Index disease' as causal after completion of a case investigation. Not to be used to record the 'Initial classification' at the initiation of a case investigation.
|
| Reason for classification | Reason for classification: The broad category of the reason for the classification. For example: lost to follow-up, child of an infected mother. |
| Epidemiological link | Epidemiological link: Identification of the cause or source of transmission.
|
| Aetiology category | Aetiology category: The category for the cause of infection. For example: imported, import-related, endemic, vaccine-associated, congenital or unknown.
|
| Endemic source category | Endemic source category: The category for the source of an endemic case. For example: household contact, community, or unknown.
|
| Comment | Comment: Additional narrative about the classification, not captured in other fields. |
| Final classification | Final classification: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Diagnosis | Diagnosis: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual. Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'. |
| Data | |
| Diagnosis name | Diagnosis name: Identification of the problem or diagnosis, by name. Coding of the name of the problem or diagnosis with a terminology is preferred, where possible. |
| Classification | Classification: Classification for an identified infectious disease as part of a disease surveillance investigation. |
| Data | |
| Index disease | Index disease: The name of the infectious disease under investigation. This data element may be redundant if the index disease has been identified elsewhere within a template.
|
| Final classification | Final classification: Classification of the likelihood of the 'Index disease' as causal after completion of a case investigation. Not to be used to record the 'Initial classification' at the initiation of a case investigation.
|
| Reason for classification | Reason for classification: The broad category of the reason for the classification. For example: lost to follow-up, child of an infected mother. |
| Epidemiological link | Epidemiological link: Identification of the cause or source of transmission.
|
| Aetiology category | Aetiology category: The category for the cause of infection. For example: imported, import-related, endemic, vaccine-associated, congenital or unknown.
|
| Endemic source category | Endemic source category: The category for the source of an endemic case. For example: household contact, community, or unknown.
|
| Comment | Comment: Additional narrative about the classification, not captured in other fields. |