| TEMPLATE ID | Contact for tracing - JM |
|---|---|
| Concept | Contact for tracing - JM |
| Description | Not Specified |
| Purpose | Not Specified |
| References | |
| Authors | name: Heather Leslie; organisation: Atomica Informatics; email: heather.leslie@atomicainformatics.com; date: 2023-10-16 |
| Other Details Language | name: Heather Leslie; organisation: Atomica Informatics; email: heather.leslie@atomicainformatics.com; date: 2023-10-16 |
| Other Details (Language Independent) |
|
| Language used | en |
| Citeable Identifier | 1013.26.952 |
| Root archetype id | openEHR-EHR-SECTION.adhoc.v1 |
| Contact for tracing | Contact for tracing: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Exposure contact for tracing | Exposure contact for tracing: An individual who may be the source of infectious disease and at risk of spreading it to others or an individual who may be at risk after exposure to an infected individual. |
| Data | |
| Label | Label: Administrative identifier or label to anonymise the contact. |
| Person - contact for tracing | Person - contact for tracing: 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 | 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. |
| 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 - 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. |
| 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 - work number | Phone - work number: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| 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. |
| Contact type | Contact type: The type of contact where potential transmission occurred. For example: household, health facility, |
| Contacted? | Contacted?: Has contact been made with the exposed individual?
|
| Symptomatic? | Symptomatic?: Is the exposed individual reporting any relevant symptoms or signs?
|
| Vaccination status | Vaccination status: Assertion about whether the contact has received all recommended and relevant vaccines for the infectious disease or agent.
|
| Treated? | Treated?: Has the exposed individual been treated?
|
| Comment | Comment: Additional narrative about the contact not captured in other fields. |
| 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:
|
| Age assertion - infant | Age assertion - infant: A statement about the age of an individual at a point in time. |
| Data | |
| Point in time event | Point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time. |
| Data | |
| Chronological age | Chronological age: The age of an individual at the event time, calculated from date of birth. In most use cases the DV_DURATION data type is used to record the Chronological age. The DV_INTERVAL_DURATION is used for recording a structured age interval in cases where there's uncertainty about the individual's exact age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days). The DV_TEXT data type is used for recording a textual representation of the individual's age, or age category often found in questionnaires. For example: 'P3M2W', '0,2884615384615385 a_j', '3 months 2 weeks' or '31-40 years' or 'Teenager'. PT1H..P51W |
| Sex & gender | Sex & gender: Details about the gender of an individual. |
| Data | |
| Sex assigned at birth | Sex assigned at birth: The sex of an individual determined by anatomical characteristics observed and registered at birth. For example: 'Male', 'Female', 'Intersex'. Coding with a terminology is recommended, where possible. Use the element 'Comment' or the SLOT 'Details' if needed to register more specific details of the individuals gender.
|
| 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.
|
| Specific test | Specific test: Details about a specified investigation or grouping of investigations relevant for the screening purpose. Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations. |
| Test name | Test name: Name of the diagnostic investigation or grouping of investigations. For example: 'Blood gas', Chest Xray', 'ECG'; or 'Hearing test'. Coding of the 'Investigation name' with a terminology is preferred, where possible. |
| Done? | Done?: Is there a history of the investigation being carried out? In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
|
| Type | Type: The method, technique, modality or other more specific identification of the diagnostic investigation. For example: contrast-enhanced mammography, magnification mammography, mammographic digital tomosynthesis, contrast imaging technique, fluorescence in situ hybridisation, Immunoassay method. |
| 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. |
| Conclusion | Conclusion: Brief description, summary or interpretation of the investigation outcome. For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings of laboratory tests. In that situation, nest a CLUSTER archetype carrying the structured result within the following 'Additional details' SLOT, for example the CLUSTER.laboratory_test_analyte archetype. |
| 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.
|
| Comment | Comment: Additional narrative about the specimen not captured in other fields. Optional[{fhir_mapping=Specimen.note}] |
| Comment | Comment: Additional narrative about the diagnostic investigation test not captured in other fields. |
| Imaging examination screening - JM | Imaging examination screening - JM: Series of questions and associated answers used to screen whether diagnostic investigations have been carried out. The answers may be self-reported. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Any imaging? | Any imaging?: 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.
|
| Specific imaging | Specific imaging: Details about a specified investigation or grouping of investigations relevant for the screening purpose. Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations. |
| Study name | Study 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.
|
| Type | Type: The method, technique, modality or other more specific identification of the diagnostic investigation. For example: contrast-enhanced mammography, magnification mammography, mammographic digital tomosynthesis, contrast imaging technique, fluorescence in situ hybridisation, Immunoassay method. |
| Date of study | Date of study: 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. |
| Findings | Findings: Brief description, summary or interpretation of the investigation outcome. For example: 'All results within normal range', 'Normal', 'Further investigations needed'. This data element is not to contain a representation of the actual results or findings of laboratory tests. In that situation, nest a CLUSTER archetype carrying the structured result within the following 'Additional details' SLOT, for example the CLUSTER.laboratory_test_analyte archetype. |
| Comment | Comment: Additional narrative about the diagnostic investigation test not captured in other fields. |
| Medication administered | Medication administered: 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. |
| Contact travel history | Contact travel history: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Travel event | Travel event: Details about a specific trip or travel event. |
| Data | |
| Origin | Origin: The name of the country, or the region of a country, that the individual regards as 'home' for the purpose of this episode of travel. |
| Date of departure | Date of departure: The date when the individual departed their location of origin. |
| Description | Description: Narrative description about the whole trip, especially about potential exposure to health risks. |
| Specific destination | Specific destination: Details about a single location visited during travel - in country or abroad. |
| Country | Country: The country visited. |
| State/region | State/region: The region visited. Different regions within the same country maybe identified if they potentially pose different health risks. |
| City | City: The city visited. Different cities within the same country or region maybe identified if they potentially pose different health risks. |
| Date of arrival | Date of arrival: Date of arrival to the identified destination. |
| Description | Description: Narrative description about the visit to the location. For example: a description of accommodation, clothing worn, mosquito nets used and any potential exposure to other health risks. |
| Specific place or person | Specific place or person: The name of a specific place, person or group of people that was visited. For example: people or organisation visited; accommodation or a cruise ship; a building, such as a museum or conference centre, hotel; an event, such as a festival; or other location, such as a beach or sports arena. This data element has multiple occurrences to allow for more than one specific place/person to be recorded. |
| Date of departure | Date of departure: Date of exit from the identified destination. |
| Comment | Comment: Additional narrative about the stay at the identified location, not captured in other fields. |
| Return transport | Return transport: Details about how the individual returned to their home base. This may be useful if it is necessary to use contact tracing. For example: the carrier and ID of a flight or ship. |
| Date of return | Date of return: The date when the individual returned back to their location of origin. |
| Comment | Comment: Additional narrative about the whole trip, not captured in other fields. |