| TEMPLATE ID | Infectious disease investigation metadata - JM |
|---|---|
| Concept | Infectious disease investigation metadata - JM |
| Description | Not Specified |
| Purpose | Not Specified |
| References | |
| Authors | date: 2025-12-19 |
| Other Details Language | date: 2025-12-19 |
| Other Details (Language Independent) |
|
| Language used | en |
| Citeable Identifier | 1013.26.923 |
| Root archetype id | openEHR-EHR-ADMIN_ENTRY.infectious_disease_investigation_metadata.v0 |
| 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. |