| ARCHETYPE ID | openEHR-EHR-OBSERVATION.exposure_screening.v1 |
|---|---|
| Concept | Exposure screening questionnaire |
| Description | Series of questions and associated answers used to screen for potential exposure to a chemical, physical or biological agent which has caused or may cause harm to an individual. |
| Use | Use to create a framework for recording answers to pre-defined screening questions about situations or events where the individual has been, or may have been, exposed to a harmful agent. Examples of agents and groupings of agents are 'hepatitis C' and 'blood borne infectious agents'; or 'asbestos' and 'carcinogenic substances'. Common use cases include, but are not limited to:
The semantics of this archetype are intentionally loose, and querying this archetype would normally only be useful or safe within the context of each specific template. In a template, each data element would usually be renamed to the specific question asked. Where value sets have been proposed for common use cases, these can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. The EVENT structure from the reference model can be used to specify whether the questions relate to point in time or over a period of time. Use a separate instance of this archetype to distinguish between a questionnaire recording information about exposure that has happened at any time in the past and information about exposure within a specified time interval - for example the difference between "Have you ever used any drug by injection?" compared to "Have you injected any drug during the last 6 months?". The source of the information in a questionnaire response may vary in different contexts but can be specifically identified using the 'Information provider' element in the Reference Model. This archetype has been designed to be used as a screening tool or to record simple questionnaire-format data for use in situations such as a disease registry. If the screening questionnaire identifies the presence of exposure it is recommended that clinical system record and persist the specific details about the exposure using a relevant exposure archetype, for example the EVALUATION.exposure to record details about the actual exposure. |
| Misuse | Not to be used to record persistent details about a known or identified exposure. Use the EVALUATION.exposure archetype for this purpose. Not to be used to create a framework for recording answers to pre-defined screening questions about exposure to potentially harmful psychosocial factors like poverty, or traumatic experiences like bullying or war. Use an appropriate screening questionnaire archetype for this purpose. Not to be used to record information about substance use such as cigarette smoking or alcohol use. Use the OBSERVATION.substance_use_screening or an appropriate EVALUATION archetype for this purpose. |
| Purpose | To create a framework for recording answers to pre-defined screening questions about situations or events where the individual has been, or may have been, exposed to a harmful agent. |
| References | |
| Copyright | © Nasjonal IKT HF |
| Authors | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2020-03-14 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2020-03-14 |
| Other Details (Language Independent) |
|
| Keywords | |
| Lifecycle | published |
| UID | d51743b9-d234-4f4c-8db8-453326c60831 |
| Language used | en |
| Citeable Identifier | 1246.145.1087 |
| Revision Number | 1.0.3 |
| Archetype Concept Comment | The answers may be self-reported. |
| protocol | |
| Extension | Extension: Additional information required to extend the model with local content or to align with other reference models or formalisms. For example: local information requirements; or additional metadata to align with FHIR. Include: All not explicitly excluded archetypes |
| data | |
| Screening purpose | Screening purpose: The context or reason for screening. This data element is intended to provide collection context for the question/answer groups when queried at a later date. It is not expected that this data element will be exposed to the individual, but only stored in data. For example: pre-admission screening, the name of the actual questionnaire or screening for previous exposure to a group of agents, such as antibiotic resistant bacteria. |
| Agent name | Agent name: The name of the chemical, physical or biological agent or grouping of agents to which an individual may have been exposed. For example: noise, environmental cigarette smoke, insect venom, ionising radiation, or a virus. Coding of 'Agent name' with a terminology is preferred, where possible. Free text should be used only if there is no appropriate terminology available. |
| Any exposure? | Any exposure?: Presence of any relevant exposure. Choice of:
|
| Description | Description: Narrative description about the history of exposure to the identified chemical, physical or biological agent or grouping of agents. |
| Specific exposure | Specific exposure: Details about each possible specific exposure circumstance. |
| Situation | Situation: The exposure event, or situation or activity where exposure may have occurred. For example: Bee sting; travel to an 'at risk' location; exposure to infected body fluids; or worked as a healthcare provider. Coding of 'Situation' with a terminology is preferred, where possible. |
| Presence? | Presence?: Has the specified 'Situation' occurred? 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. Choice of:
|
| Timing | Timing: Indication of timing related to the exposure situation. The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an exposure situation occurred. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for the exposure situation; the interval of time during which the exposure situation occurred; the duration of the exposure situation; the age of the individual at the time of the exposure situation; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year. Choice of:
|
| Additional details | Additional details: Additional details about the specific exposure event, location or associated contacts. Include: openEHR-EHR-CLUSTER.person.v1 and specialisations or openEHR-EHR-CLUSTER.address.v1 and specialisations or openEHR-EHR-CLUSTER.organisation.v1 and specialisations or openEHR-EHR-CLUSTER.anatomical_ openEHR-EHR-CLUSTER.anatomical_ openEHR-EHR-CLUSTER.anatomical_ |
| Comment | Comment: Additional narrative about the specific exposure situation, not captured in other fields. |
| Additional details | Additional details: Structured details or questions about screening for exposure. Include: All not explicitly excluded archetypes |
| events | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Other contributors | Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor) Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor) Hugo Claudio Briceño García, Catsalut, Spain Gunn Elin Blakkisrud, DIPS ASA, Norway Kåre Flø, DIPS ASA, Norway Rosane Gotardo, Systema Ltda., Brazil Evelyn Hovenga, EJSH Consulting, Australia Mika Kiviaho, Tietoevry, Finland Anjali Kulkarni, Karkinos, India Jörgen Kuylenstierna, eWeave AB, Sweden Liv Laugen, Oslo universitetssykehus, Norway (Nasjonal IKT redaktør) Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Nina Louise Jebsen, Haukeland Universitetssykehus, Norway Michael Lutz, BITsoft, Germany Svenne Naumann, Finnmarkssykehuset, Norway Terje Nordberg, Helse Bergen, Norway Mikael Nyström, Cambio Healthcare Systems AB, Sweden Ragnhild Schultz, OUS, Norway Anders Thurin, VGR, Sweden John Tore Valand, Helse Bergen, Norway (openEHR Editor) Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor) |
| Translators |
|