Type: openEHR ARCHETYPE
Purpose: To record summary information about the supports needed to enable or assist an individual to perform an activity.
Use:
Use to record summary information about the supports needed to enable or assist an individual to perform a single activity. This includes an individual who is fully dependent on others to complete the activity.
Supports may include human assistance, assistive devices, assistance animals, and environmental conditions, such as a quiet room.
Support requirements may be identified for activities of everyday life in any setting, such as at home, in residential care, or in hospital.
Support requirements may be identified across a range of areas of activity and participation including, but not limited to:
An activity may be:
This information is persistent and is updated as support requirements change. It may inform care planning, allocation of staff and equipment, and determination of service eligibility. It may be recorded on its own or as part of a care plan. Recording a support requirement identifies a need. It does not imply that the support will be provided against the individual's wishes.
Record one instance of this archetype for each activity, reflecting the support needed when the individual's need for support is greatest. Where an assistive device changes the human assistance needed, such as a hoist for transfers, include the device in the name of the activity.
This archetype is one of a set of three related archetypes designed to represent different aspects of how an individual functions in everyday life:
In practice, these archetypes are often used alongside others, such as CLUSTER.symptom_sign and EVALUATION.problem_diagnosis. For example:
| ARCHETYPE ID | openEHR-EHR-EVALUATION.functional_support_requirements.v0 |
|---|---|
| Concept | Functional support requirements |
| Description | Summary information about the supports needed to enable or assist an individual to perform an activity. |
| Use | Use to record summary information about the supports needed to enable or assist an individual to perform a single activity. This includes an individual who is fully dependent on others to complete the activity. Supports may include human assistance, assistive devices, assistance animals, and environmental conditions, such as a quiet room. Support requirements may be identified for activities of everyday life in any setting, such as at home, in residential care, or in hospital. Support requirements may be identified across a range of areas of activity and participation including, but not limited to:
An activity may be:
This information is persistent and is updated as support requirements change. It may inform care planning, allocation of staff and equipment, and determination of service eligibility. It may be recorded on its own or as part of a care plan. Recording a support requirement identifies a need. It does not imply that the support will be provided against the individual's wishes. Record one instance of this archetype for each activity, reflecting the support needed when the individual's need for support is greatest. Where an assistive device changes the human assistance needed, such as a hoist for transfers, include the device in the name of the activity. This archetype is one of a set of three related archetypes designed to represent different aspects of how an individual functions in everyday life:
In practice, these archetypes are often used alongside others, such as CLUSTER.symptom_sign and EVALUATION.problem_diagnosis. For example:
|
| Misuse | Not to be used to record an individual's ability to perform an activity or participate in a life situation. Use the OBSERVATION.functional_ability archetype for this purpose. Not to be used to record an impairment of physiological or psychological function. Use the EVALUATION.impairment_summary archetype for this purpose. Not to be used to record a diagnosis, including a diagnosis of impairment or disability. Use the EVALUATION.problem_diagnosis archetype for this purpose. Not to be used to record the outcome of a functional independence assessment or scoring system. Use an appropriate OBSERVATION archetype for this purpose. Not to be used to record a request or order for a support, service, or device. Use an appropriate INSTRUCTION archetype for this purpose. Not to be used to record who is allocated or rostered to provide support, the organisation providing it, or where it is provided. This belongs to care planning and service arrangements. Not to be used to record the interventions that were provided during a specific care event or intervention. Use an appropriate ACTION archetype to document interventions or services delivered as part of care provision. |
| Purpose | To record summary information about the supports needed to enable or assist an individual to perform an activity. |
| References | Functional support requirements, Proposed data group, Australian Clinical Data for Interoperability (AUCDI) Release 4 [Internet]. Sparked FHIR Accelerator, CSIRO; [cited 2026 Nov 05]. Unpublished. Granger CV, Hamilton BB, Linacre JM, Heinemann AW, Wright BD. Performance profiles of the functional independence measure. Am J Phys Med Rehabil. 1993 Apr;72(2):84-9. 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: 2026-03-16 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2026-03-16 |
| Other Details (Language Independent) |
|
| Keywords | |
| Lifecycle | in_development |
| UID | 4bce40ec-2b5e-40eb-86b4-c5fdf3951d04 |
| Language used | en |
| Citeable Identifier | 457.148.137 |
| 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. The term "assistive device" refers to any tool, aid, or technology used by an individual to support, maintain, or optimise performance of an activity, including digital technologies and medical devices. |
| data | |
| Activity name | Activity name: The name of the activity for which support is required. Coding with an external terminology is recommended. 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, withdrawing money from an ATM; attending school, playing sport, joining a club, attending the theatre. Free text entry should only be permitted where no appropriate coded value is available. |
| Support description | Support description: Narrative description of all supports needed to perform the activity. Supports may include human assistance, assistive devices, assistance animals, and environmental conditions. |
| Assistive devices description | Assistive devices description: Narrative description of the assistive devices needed to perform the activity. For example: smartphone reminders, modified cutlery, reading glasses, hearing aids, mobility aids, prostheses, self-care aids, or communication aids. |
| Assistive device details | Assistive device details: Structured detail about one or more assistive devices needed to perform the activity. For example: smartphone reminders, modified cutlery, reading glasses, hearing aids, mobility aids, prostheses, self-care aids, or communication aids. Slot archetypes CLUSTER.device.v1 and specialisations This slot is also open to other Cluster archetypes. |
| Assistance type | Assistance type: The type of human assistance needed to enable or assist the individual to perform the activity safely or effectively. More than one 'Assistance type' may be recorded. "No assistance" may be recorded where only supports other than human assistance are needed, or where human assistance is no longer needed. Choice of:
|
| Physical assistance level | Physical assistance level: The degree of physical involvement needed from one or more people to enable or assist the individual to perform the activity safely or effectively. Record only where 'Assistance type' includes "Physical assistance". Physical assistance may relate to safety, balance, coordination, strength, or motor execution. The levels are informed by, but deliberately not aligned with, the Functional Independence Measure (FIM). They add standby and contact guarding. Each level is described in plain language rather than by proportion of effort. Where FIM or another scale is required, its values may be used in place of the local value set in a template. Choice of:
|
| Number of people | Number of people: The number of people needed to provide human assistance for the individual to perform the activity safely or effectively. The number of people needed may vary with environmental conditions or the use of assistive devices. min: >=1 |
| Support person details | Support person details: Structured details of one or more specific people who must provide the assistance. Use only where the assistance must be provided by a particular person or role, for example: shopping only with their mother, or support from a familiar support worker. This may be a named individual, a relationship, such as partner or family member, or a defined role, such as carer, therapist, or support worker. Slot archetypes CLUSTER.person.v1 This slot is also open to other Cluster archetypes. |
| Additional details | Additional details: Additional structured detail about the functional support requirements for an activity. Slot archetypes This slot is open to all Cluster archetypes. |
| Comment | Comment: Additional narrative about the functional support requirements for an activity not captured in other fields. For example: variation in support requirements with circumstances, such as fatigue, pain, or time of day. |
| protocol | |
| Last updated | Last updated: The date when these functional support requirements were last updated. |
| 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. Slot archetypes This slot is open to all Cluster archetypes. |
| Other contributors | Vebjørn Arntzen, Oslo University Hospital, Norway Sparked AU, CSIRO, Australia (openEHR Editor) SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India Tara Bonet Chinillach, Catalan Health Service, Spain Clara Calleja Vega, CatSalut. Servei Català de la Salut., Spain Lars Fuhrmann, German Society of Ophthalmology, Germany William Goossen, Results 4 Care, Netherlands Patricia Homem-Silva, University of Porto, Portugal Evelyn Hovenga, EJSH Consulting, Australia Heather Leslie, Atomica Informatics, Australia (openEHR Editor) Michael Lutz, BITsoft, Germany Patrick Fergal McSharry, MSMS(I) and SESLHD, Australia Mikael Nyström, Cambio Healthcare Systems AB, Sweden Vuk Radnić, Better, Slovenia Norwegian Review Summary, Norwegian Public Hospitals, Norway Averil Tam, CSIRO, Australia Nyree Taylor, CSIRO, Australia (openEHR Editor) |
| Translators |