| TEMPLATE ID | openEHR-Suspected Covid-19 assessment.v0 |
|---|---|
| Concept | openEHR-Suspected Covid-19 assessment.v0 |
| Description | To record the information required to evaluate the potential risk of Covid-19 infection, as part of professional screening or self-assessment. This is heavily based on the current NHS-111 UK self-assessment app at https://111.nhs.uk/covid-19 and a similar risk assessment app developed for pre-hospital admission by DIPS.no. The exact risk factors are subject to continual update as the disease progresses. |
| Use | To record the information required to evaluate the potential risk of Covid-19 infection, as part of professional screening or self-assessment. This is heavily based on the current NHS-111 UK self-assessment app at https://111.nhs.uk/covid-19 and a similar risk assessment app developed for pre-hospital admission by DIPS.no. The exact risk factors are subject to continual update as the disease progresses. Note that a critical part of the information, exposure locations, has been left open, so as to allow the list to be updated very regularly and in alignment with local or national policy. |
| Misuse | This assessment is not intended to act directly as part of any public health reporting documentation - further work is being undertaken to support this use-case. |
| Purpose | To record the information required to evaluate the potential risk of Covid-19 infection, as part of professional screening or self-assessment. This is heavily based on the current NHS-111 UK self-assessment app at https://111.nhs.uk/covid-19 and a similar risk assessment app developed for pre-hospital admission by DIPS.no. The exact risk factors are subject to continual update as the disease progresses. |
| References | |
| Authors | name: Ian McNicoll; organisation: freshEHR Clinical Informatics Ltd.; email: ian@freshehr.com; date: 2020-02-27 |
| Other Details Language | name: Ian McNicoll; organisation: freshEHR Clinical Informatics Ltd.; email: ian@freshehr.com; date: 2020-02-27 |
| Other Details (Language Independent) |
|
| Keywords | covid-19, risk, screening |
| Language used | en |
| Citeable Identifier | 1013.26.267 |
| Root archetype id | openEHR-EHR-COMPOSITION.encounter.v1 |
| Suspected Covid-19 risk assessment | Suspected Covid-19 risk assessment: Interaction, contact or care event between a subject of care and healthcare provider(s). |
| content | |
| Symptoms | Symptoms: The subjective clinical history of the subject of care as recorded directly by the subject, or reported to a clinician by the subject or a carer. |
| 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 | |
| Story | Story: Narrative description of the story or clinical history for the subject of care. |
| Influenza-like symptoms | Influenza-like symptoms: Symptoms known to be indicators of suspected Covid-19 infection |
| Symptom/Sign name | Symptom/Sign name: The name of the reported symptom or sign. Symptom name should be coded with a terminology, where possible. Terminology: SNOMED-CT
Default value: Influenza-like symptoms |
| First onset of symptoms | First onset of symptoms: The onset for this episode of the symptom or sign. While partial dates are permitted, the exact date and time of onset can be recorded, if appropriate. If this symptom or sign is experienced for the first time or is a re-occurrence, this date is used to represent the onset of this episode. If this symptom or sign is ongoing, this data element may be redundant if it has been recorded previously. |
| Presence | Presence: Is the symptom present or not?
|
| Cough | Cough: Symptoms known to be indicators of suspected Covid-19 infection |
| Symptom/Sign name | Symptom/Sign name: The name of the reported symptom or sign. Symptom name should be coded with a terminology, where possible. Terminology: SNOMED-CT
Default value: Cough |
| Presence | Presence: Is the symptom present or not?
|
| Fever | Fever: Symptoms known to be indicators of suspected Covid-19 infection |
| Symptom/Sign name | Symptom/Sign name: The name of the reported symptom or sign. Symptom name should be coded with a terminology, where possible. Terminology: SNOMED-CT
Default value: Fever |
| Presence | Presence: Is the symptom present or not?
|
| Difficulty breathing | Difficulty breathing: Symptoms known to be indicators of suspected Covid-19 infection |
| Symptom/Sign name | Symptom/Sign name: The name of the reported symptom or sign. Symptom name should be coded with a terminology, where possible. Terminology: SNOMED-CT
Default value: Difficulty breathing |
| Presence | Presence: Is the symptom present or not?
|
| Sore throat | Sore throat: Symptoms known to be indicators of suspected Covid-19 infection |
| Symptom/Sign name | Symptom/Sign name: The name of the reported symptom or sign. Symptom name should be coded with a terminology, where possible. Terminology: SNOMED-CT
Default value: Pain in throat |
| Presence | Presence: Is the symptom present or not?
|
| Other symptom | Other symptom: Symptoms known to be indicators of suspected Covid-19 infection |
| Symptom/Sign name | Symptom/Sign name: The name of the reported symptom or sign. Symptom name should be coded with a terminology, where possible. |
| Presence | Presence: Is the symptom present or not?
|
| Body temperature | Body temperature: A measurement of the body temperature, which is a surrogate for the core body temperature of the 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 | |
| Temperature | Temperature: The measured body temperature (as a surrogate for the core of the body). 0..100 °C |
| Travel trip history | Travel trip history: Details of a travel trip with respect to exposure to potential risk. |
| Data | |
| Any event | Any event: * |
| Data | |
| Recent travel | Recent travel: Has the patient travelled recently? The definition of 'recently' may vary depending on circumstances of the wider patient story and known currnet infection risk.
|
| Date of return | Date of return: * |
| Covid-19 infection risk assessment | Covid-19 infection risk assessment: Assessment of the potential and likelihood of Covid-19 infection as determined by identified risk factors. |
| Data | |
| Health risk | Health risk: Identification of the potential future disease, condition or health issue for which the risk is being assessed, by name. Coding of 'Health risk' with a terminology is preferred, where possible. Free text should be used only if there is no appropriate terminology available. For example: risk of cardiovascular disease, with risk factors of hypertension and hypercholesterolaemia.
|
| Contact with confirmed case | Contact with confirmed case: Details about each possible risk factor. |
| Risk factor | Risk factor: Identification of the risk factor, by name. For example: hypertension and hypercholesterolaemia, which may be used as part of the overall assessment for cardiovascular disease; or a genetic marker. Coding of 'Risk factor' with a terminology, where possible.
|
| Presence | Presence: Presence of the risk factor.
|
| Contact with suspected pneumonia | Contact with suspected pneumonia: Details about each possible risk factor. |
| Risk factor | Risk factor: Identification of the risk factor, by name. For example: hypertension and hypercholesterolaemia, which may be used as part of the overall assessment for cardiovascular disease; or a genetic marker. Coding of 'Risk factor' with a terminology, where possible.
|
| Presence | Presence: Presence of the risk factor.
|
| Contact with birds in China | Contact with birds in China: Details about each possible risk factor. |
| Risk factor | Risk factor: Identification of the risk factor, by name. For example: hypertension and hypercholesterolaemia, which may be used as part of the overall assessment for cardiovascular disease; or a genetic marker. Coding of 'Risk factor' with a terminology, where possible.
|
| Presence | Presence: Presence of the risk factor.
|
| Contact with Avian flu | Contact with Avian flu: Details about each possible risk factor. |
| Risk factor | Risk factor: Identification of the risk factor, by name. For example: hypertension and hypercholesterolaemia, which may be used as part of the overall assessment for cardiovascular disease; or a genetic marker. Coding of 'Risk factor' with a terminology, where possible.
|
| Presence | Presence: Presence of the risk factor.
|
| Contact with severe resp disease | Contact with severe resp disease: Details about each possible risk factor. |
| Risk factor | Risk factor: Identification of the risk factor, by name. For example: hypertension and hypercholesterolaemia, which may be used as part of the overall assessment for cardiovascular disease; or a genetic marker. Coding of 'Risk factor' with a terminology, where possible.
|
| Presence | Presence: Presence of the risk factor.
|
| Potential locality exposure | Potential locality exposure: Details about each possible risk factor. |
| Risk factor | Risk factor: Identification of the risk factor, by name. For example: hypertension and hypercholesterolaemia, which may be used as part of the overall assessment for cardiovascular disease; or a genetic marker. Coding of 'Risk factor' with a terminology, where possible.
|
| Presence | Presence: Presence of the risk factor.
|
| Location visited | Location visited: Details of potential exposure to a potentially harmful agent, relating to a specific location, typically an outbreak of infectious disease. |
| Outbreak location | Outbreak location: *
|
| Risk assessment | Risk assessment: Evaluation of the health risk. There may be multiple variations on the assessment of risk. The Choice data type allows for recording of the assessment as either free text or value sets (such as low, medium or hig). The proportion data type allows recording of a percentage, a ratio or a fraction. The quantity data type allows recording of a decimal number.
|
| Problem/Diagnosis | Problem/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 | |
| Problem/Diagnosis name | Problem/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. Terminology: SNOMED-CT
|
| Status | Status: Contextual or temporal qualifier for a specified problem or diagnosis. |
| Diagnostic status | Diagnostic status: Stage or phase of diagnostic process. The status is usually determined by a combination of the timing of diagnosis plus level of clinical certainty resulting from diagnostic tests and clinical evidence available. This data element and 'Diagnostic certainty' in EVALUATION.problem_diagnosis are two important axes of the diagnostic process, and valid combinations will need to be presented by software that exposes both data elements, so it is not possible for users to select conflicting combinations. Preliminary or working diagnoses are intended to represent the single most likely choice out of all differential diagnosis options.
|
| Protocol | |
| Last updated | Last updated: The date this problem or diagnosis was last updated. |
| Service request | Service request: Request for a health-related service or activity to be delivered by a clinician, organisation or agency. |
| Current Activity | Current Activity: Current Activity. |
| Description | |
| Service name | Service name: The name of the single service or activity requested. Coding of the 'Service name' with a coding system is desirable, if available. For example: 'referral' to an endocrinologist for diabetes management. Terminology: SNOMED-CT
|
| Reason for request | Reason for request: A short phrase describing the reason for the request. Coding of the 'Reason for request' with a coding system is desirable, if available. This data element allows multiple occurrences to enable the user to record a multiple responses, if required. For example: 'manage diabetes complications'. Terminology: SNOMED-CT
Default value: Suspected disease caused by 2019 novel coronavirus. |