ACTION.procedure is a great archetype and it is published a long time ago. I guess all reading this post know the archetype and has some opinions on how to use it.
Surprisingly we discovered that we had really different views on the scope for the archetype. This appeared to my during this thread with Heather on the openEHR CKM.
This post is an invitation to share thoughts about the ACTION.procedure and it’s use in current systems, it’s intended purpose/scope and the future direction for the archetype.
We, DIPS AS, is currently implementing an application to support the national patient safety program. Some information, in Norwegian, about the program is found here: https://pasientsikkerhetsprogrammet.no/ The purpose of the program is to reduce the frequency of unwanted events when providing health care. The program is divided into several focus areas like: risk of falling, pressure soar/ulcers, sepsis, changed somatic state, suicide, malnutrition and so on. The application we are building will use a lot of screening archetypes (Stratify, NEWS , NRS2002, etc.)
In addition to this straight forward archetype usage we want to record the action taken to follow up the admitted patient. Examples of such activities is:
- Screening for risk of falling
- Create plan to reduce risk of falling
- Do actions do reduce risk of falling
- Evaluate the plan and/or re-evaluate the risk for falling
- Complete the activity
To record these steps we will use openEHR Taskplanning in a future release. Currently we need to support the use-case with “old-school” archetypes, and we ended up with the following postulate/conclusion:
The ACTION.procedure is perfect match to record the activities as illustrated above. But we need a minor adjustment: we need to add a new careflow step for the action of evaluating/reviewing the ongoing activity.
As far as I understand the intention for ACTION.procedure is to cover more “one-shot” actions, and not to manage long-running activities.
So my intention with this topic is to open a discussion about ACTION.procedure and the modelling for such a use-case as described.
What do you think?
- Is ACTION.procedure well-fitted for the use-case described?
- Should we create some new archetype for my use-case?
- Should it be one or several archetypes?
- Perhaps the suggested design is wrong in the first time?
Look forward to some opinions on this!