ARCHETYPE Physical environment screening (openEHR-EHR-OBSERVATION.physical_environment_screening.v0)

ARCHETYPE IDopenEHR-EHR-OBSERVATION.physical_environment_screening.v0
ConceptPhysical environment screening
DescriptionSeries of questions and associated answers used to screen for factors or characteristics in the physical environment which have caused or could potentially cause harm to an individual.
Use

Use to create a framework for recording answers to pre-defined screening questions about factors or characteristics in the physical environment which have caused or could potentially cause harm to an individual.

Common use cases include, but are not limited to:

  • Systematic questioning in any consultation related to exposure, for example:
    --- Have you ever lived or worked in a building with asbestos?
    --- Are chemicals stored in appropriate conditions in your workplace?
    --- Is your workplace well ventilated?

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 or public health surveillance.

MisuseNot 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.
PurposeTo create a framework for recording answers to pre-defined screening questions about factors or characteristics in the physical environment which have caused or could potentially cause harm to an individual.
References
Copyright© openEHR Foundation
AuthorsAuthor name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2020-03-14
Other Details LanguageAuthor name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2020-03-14
Other Details (Language Independent)
  • Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
  • Custodian Organisation: openEHR Foundation
  • References:
  • Original Namespace: org.openehr
  • Original Publisher: openEHR Foundation
  • Custodian Namespace: org.openehr
  • MD5-CAM-1.0.1: CDB173035FCC29D929686045004EA5B7
  • Build Uid: bc5e7448-b6ba-4eb7-bccb-a179bb6bafe3
  • Ip Acknowledgements: This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyrighted material of the International Health Terminology Standards Development Organisation (IHTSDO). Where an implementation of this artefact makes use of SNOMED CT content, the implementer must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/snomed-ct/get-snomed or info@snomed.org.
  • Revision: 0.0.1-alpha
Keywords
Lifecyclein_development
UIDfb25bc8a-ae37-43a6-a0f9-c6034009f2ef
Language useden
Citeable Identifier1013.1.7547
Revision Number0.0.1-alpha
Archetype Concept CommentThe answers may be self-reported.
events
Any eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
data
Screening purposeScreening 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.
Specific conditionSpecific condition: Details about each possible specific environmental condition or factor.
Environmental conditionEnvironmental condition: The condition or factor in the physical environment being screened for.
For example: safe storage of poisonous materials. Coding with a terminology is preferred, where possible.
Presence?Presence?: Has the specified 'Condition' been identified?
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:
Additional detailsAdditional details: Additional details about the specific condition or factor identified in the physical environment.
CommentComment: Additional narrative about the specific exposure situation, not captured in other fields.
protocol
ExtensionExtension: 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
Other contributorsVebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)
Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
John Tore Valand, Helse Bergen, Norway (openEHR Editor)
Translators
  • Norwegian Bokmål: Silje Ljosland Bakke, Marit Alice Venheim, John Tore Valand, Helse Vest IKT AS, Helse Bergen, silje.ljosland.bakke@helse-vest-ikt.no, marit.alice.venheim@helse-vest-ikt.no, john.tore.valand@helse-vest-ikt.no