| ARCHETYPE ID | openEHR-EHR-OBSERVATION.functional_ability.v0 |
|---|---|
| Concept | Functional ability |
| Description | An assessment of an individual’s ability to perform an activity safely and consistently without human assistance. |
| Use | Use to record an assessment of an individual’s ability to independently perform a single identified activity at a point in time, reflecting the combined impact of physical, sensory, cognitive, emotional, psychological, social, and environmental factors present at that time. Throughout this archetype:
An activity may be:
Assessment of ability is often context-dependent and may vary due to factors such as environment, fatigue, pain, and availability of assistive devices. If the same activity is assessed at the same time under different conditions, such as with and without an assistive device, record each set of conditions together with its corresponding level of ability within the same assessment. This approach supports documentation of how functional ability may vary under different circumstances during a single assessment. The scope of functional ability includes, but is not limited to:
Functional ability may be assessed across a range of areas of activity and participation including, but not limited to:
Record one instance of this archetype for each named activity during a single assessment, including where the same named activity is performed under varying conditions. This archetype is one of a set of three related archetypes designed to represent different aspects of how an individual functions in everyday life. Together, these archetypes support structured representation of functional ability, impairments contributing to functional limitations, and the supports required to enable or assist an individual to perform an activity. The other archetypes are:
|
| Misuse | Not to be used to record a congenital or acquired impairment that limits an individual's functional ability. Use the EVALUATION.functional_impairment_summary archetype for this purpose. Not to be used to record assessments of the supports needed to enable or assist an individual in performing an activity. Use the EVALUATION.functional_support_requirements archetype for this purpose. Not to be used to record the outcome of a regulatory, occupational, or legal assessment for certification, licensing, or clearance to perform a safety-critical activity or duty, such as fitness to drive or return-to-work clearance. Assessments recorded using this archetype may provide supporting evidence for such determinations but do not represent the outcome of those decisions. Not to be used to record a generalised statement about independence or functional ability across multiple activities or life situations. The need for a specific archetype for this purpose is acknowledged but has not yet been developed. Not to be used to represent a summary of patterns or trends in ability over time. |
| Purpose | To record an assessment of an individual’s ability to independently perform a single identified activity at a point in time. |
| References | Functional ability, Draft data group. Sparked AU FHIR accelerator, Australian Clinical Data for Interoperability Release 3. World Health Organization. International classification of functioning, disability and health (ICF) [Internet]. Geneva: World Health Organization; 2001 [cited 2026 Jan 19]. Available from: https://www.who.int/standards/classifications/international-classification-of-functioning-disability-and-health |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2025-12-09 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2025-12-09 |
| Other Details (Language Independent) |
|
| Keywords | ADL, iADL, pADL, capacity, ability, activity, daily, living, independent |
| Lifecycle | in_development |
| UID | 32272e1d-0486-4780-89cf-17f3ea8a9d87 |
| Language used | en |
| Citeable Identifier | 1013.1.5017 |
| Revision Number | 0.0.1-alpha |
| Archetype Concept Comment | Throughout this archetype, the phrase ‘perform an activity’, or similar, refers to carrying out a single activity or a grouping of related activities, or participating in an everyday life situation. |
| state | |
| Assessment conditions description | Assessment conditions description: Narrative description of the circumstances under which an assessment is performed, to support interpretation of the observed assessment results. For example: describing the environment, method, or situation in which the assessment was carried out. This may include whether the assessment occurred in a clinic, hospital, or home setting; whether the individual was in their usual or an unfamiliar environment; any specific conditions that may influence performance, such as noise, lighting, and time of day; use of an unfamiliar assistive device for the assessment; and adherence to or deviation from a defined assessment protocol. |
| Assistive devices description | Assistive devices description: Narrative description about any tools, aids, or technologies used by the individual while performing the activity. For example: smartphone reminders, modified cutlery, reading glasses, hearing aids, mobility aids, prostheses, self-care aids, communication aids, or an assistance animal. |
| Assistive device | Assistive device: Structured detail about one or more tools, aids, or technologies used by an individual while performing the activity. For example: smartphone reminders, modified cutlery, reading glasses, hearing aids, mobility aids, prostheses, self-care aids, communication aids, or an assistance animal. Include: openEHR-EHR-CLUSTER.device.v1 and specialisations |
| Confounding factors | Confounding factors: Issues or contextual factors that may impact on functional ability, not captured in other fields. For example: fatigue, diurnal variation, recent exertion, medication effect, sleep status, mood, situational anxiety. |
| 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 | |
| Activity name | Activity name: The name of the activity being assessed. Coding with an external terminology is recommended. Free text entry should only be permitted where no appropriate coded value is available. For example: rolling over in bed, transferring from bed to chair, walking; climbing stairs; brushing teeth, putting on shoes, menstrual care; reading, speaking, writing; preparing meals, doing housework; using public transport, seeking a job withdraw money from an ATM; attending school, play sport, join a club, attend the theatre. |
| Ability | Ability: The assessed ability to perform the identified activity independently. Coding with a terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available. An individual may be able to independently perform the activity and still experience difficulty. The degree of difficulty is recorded separately using the ‘Difficulty’ data element. ‘Ability’ and ‘Difficulty’ represent complementary components of the functional ability assessment. Recording a value for ‘Difficulty’ is not applicable where ‘Ability’ has been recorded as ‘Unable’. Choice of:
|
| Clinical description | Clinical description: Narrative description of the individual's assessed ability to independently perform the identified activity. For example: problems completing the activity, safety concerns, or consistency issues. |
| Difficulty | Difficulty: The degree of difficulty experienced by the individual when performing the activity independently. Coding with a terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available. Difficulty may be self-reported and/or clinically observed during the assessment. Increased time or effort beyond that typically required to independently perform the activity may indicate difficulty, even where assistive devices are used. Any degree of difficulty may affect the completeness, safety, or consistency of performance of the activity. Recording the degree of difficulty may support assessment of functional support or adaptation requirements. ‘Ability’ and ‘Difficulty’ represent complementary components of the functional ability assessment. Recording a value for ‘Difficulty’ is not applicable where ‘Ability’ has previously been recorded as ‘Unable’. Choice of:
|
| Reason for difficulty | Reason for difficulty: Narrative description of the factors contributing to difficulty performing the activity. For example: impairment, symptoms, environmental or contextual barriers, equipment availability, communication issues, training, or other relevant circumstances. |
| Comment | Comment: Additional narrative about the performance of the activity, not captured in other fields. |
| 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); Sparked AU, CSIRO, Australia; Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor); Tor Bendle, CSIRO, Australia; SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India; Hugo Claudio Briceño García, Catsalut, Spain; Hanne Marte Bårholm, Helse Vest IKT, Norway (openEHR Editor); Grete Hovde Bøe, Sykehuspartner HF, Norway (openEHR Editor); Aleksander Furnes, Helse Nord IKT, Norway (openEHR Editor); Ciprian Gerstenberger, Helse Nord IKT, Norway (openEHR Editor); Tore Gravdal, Tieto Caretech, Norway; Joost Holslag, Joost Holslag Geneeskunde & Advies, Netherlands; Patricia Homem-Silva, University of Porto, Portugal; Evelyn Hovenga, EJSH Consulting, Australia; June Marie Nepstad Knappskog, Helse Nord IKT AS, Norway (openEHR Editor), Norway (openEHR Editor); Heidi Koikkalainen, United Kingdom; Ronald Krawec, Alberta Health Services, Canada; Elin Kristiansen, Sykehuspartner HF, Norway (openEHR Editor); Kanika Kuwelker, Helse Vest IKT, Norway (openEHR Editor); Jörgen Kuylenstierna, eWeave AB, Sweden; Eli Larsen, UNN, Norway (openEHR Editor); Liv Laugen, Oslo University Hospital, Norway, Norway (openEHR Editor); Heather Leslie, Atomica Informatics, Australia (openEHR Editor); Michael Lutz, BITsoft, Germany; Patrick Fergal McSharry, MSMS(I) and SESLHD, Australia; Martin Milde, Helse Vest IKT, Norway (openEHR Editor); Olha Nikolaieva, University Hospital Basel, Switzerland; Mikael Nyström, Cambio Healthcare Systems AB, Sweden; Bipinkumar Rathod, NHS, United Kingdom; Terje Sagmyr, Helse Vest IKT, Norway (openEHR Editor); Norwegian Review Summary, Norwegian Public Hospitals, Norway; Averil Tam, CSIRO, Australia; Nyree Taylor, CSIRO, Australia; Kanthan Theivendran, NHS, United Kingdom; John Tore Valand, Helse Vest IKT, Norway (openEHR Editor); Karsten Øvretveit, Helse Vest IKT, Norway (openEHR Editor); Ines Žabkar, Better, Slovenia |
| Translators |