| ARCHETYPE ID | openEHR-EHR-OBSERVATION.physical_activity_screening.v0 |
|---|---|
| Concept | Physical activity screening questionnaire |
| Description | Series of questions and associated answers used to screen for physical activity. |
| Use | Use to create a framework for recording answers to pre-defined screening questions about the broad range of physical activies. 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 management that has been performed at any time in the past and information about management performed within a specified time interval - for example the difference between "Have you ever trained regularily?" compared to "Have you been training the past 4 weeks. 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 physical activity, it is recommended that clinical system record and persist the specific details about the physical activity using archetypes specific for the clinical purpose. |
| Misuse | Not to be used to record a training diary, use other relevant archetypes for this purpose. |
| Purpose | To create a framework for recording answers to pre-defined screening questions about the broad range of physical activites. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2020-03-13 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2020-03-13 |
| Other Details (Language Independent) |
|
| Keywords | treatment, screening, intervention, questionnaire, care, support, therapy |
| Lifecycle | in_development |
| UID | 230d7980-6ba3-465e-89ce-6c79e26673be |
| Language used | en |
| Citeable Identifier | 1013.1.8270 |
| Revision Number | 0.0.1-alpha |
| Archetype Concept Comment | The answers may be self-reported. |
| 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. |
| 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 or the name of the actual questionnaire. |
| Any physical activity? | Any physical activity?: Is there a history of physical activity relevant for 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. Choice of:
|
| Description | Description: Narrative description about the history of any physical activities relevant for the screening purpose. |
| Physical activity | Physical activity: Details about a specific physical activity or grouping of physical activities relevant for the screening purpose. Use separate instances of this CLUSTER to differentiate between specific investigations or groupings of investigations. |
| Physical activity name | Physical activity name: Name of a specific physical activity or grouping of physical activites activities. For example: Active football player, mall walker. Coding of the 'Pysical activity name' with a terminology is preferred, where possible. |
| Specific physical activity? | Specific physical activity?: Is there a history of the physical activity? 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 physical activity. 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 physical activity; the interval of time during which the physical activity was carried out; the duration of the physical activity; the age of the individual at the time of the physical activity; 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: Additonal details or questions about the specific physical activity. Include: openEHR-EHR-CLUSTER.organisation.v1 |
| Comment | Comment: Additional narrative about a specific physical activity question, not captured in other fields. |
| Additional details | Additional details: Structured details or questions about screening for physical activity. Include: All not explicitly excluded archetypes |
| 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 |
| Other contributors | Vebjørn Arntzen, Oslo universitetssykehus HF, Norway (Nasjonal IKT redaktør) Astrid Askeland, Dips AS, Norway Silje Ljosland Bakke, Helse Vest IKT AS, Norway (Nasjonal IKT redaktør) SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India Hanne Marte Bårholm, Helse Vest IKT, Norway (Nasjonal IKT redaktør) Yexuan Cheng, 浙江大学, China Are Edvardsen, SKDE, Helse Nord RHF, Norway Alexander Eikrem-Lüthi, Lovisenberg Diakonale Sykehus, Norway Kåre Flø, DIPS ASA, Norway Grant Forrest, Lunaria Ltd, United Kingdom Heather Grain, Llewelyn Grain Informatics, Australia Mikkel Johan Gaup Grønmo, Regional forvaltning EPJ, Helse Nord, Norway (Nasjonal IKT redaktør) Anca Heyd, DIPS ASA, Norway Joost Holslag, Nedap, Netherlands Evelyn Hovenga, EJSH Consulting, Australia Gunnar Jårvik, Helse Vest IKT AS, Norway Øygunn Leite Kallevik, Helse Bergen, Norway Anjali Kulkarni, Karkinos, India Kanika Kuwelker, Helse Vest IKT, Norway (Nasjonal IKT redaktør) Jörgen Kuylenstierna, eWeave AB, Sweden Liv Laugen, Oslo universitetssykehus, Norway (Nasjonal IKT redaktør) Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Per Meinich, Helse Sør-Øst RHF, Norway Mikael Nyström, Cambio Healthcare Systems AB, Sweden Jussara Rotzsch, Hospital Alemão Oswaldo Cruz, Brazil Andre Smitt-Ingebretsen, Sørlandet sykehus HF, Norway Natalia Strauch, Medizinische Hochschule Hannover, Germany John Tore Valand, Haukeland Universitetssjukehus, Norway (Nasjonal IKT redaktør) Marit Alice Venheim, Helse Vest IKT, Norway (Nasjonal IKT redaktør) Ina Wille, Helse-Vest RHF, Norway |
| Translators |