I added a bit more background information on the ABD workflow project:
Activity-Based Design is based on the idea that an 'Activity' is the
unit of clinical work, and thus also the unit of formal definition of a
workflow. An Activity as currently conceived includes:
* semantic model (elements) - something like an archetype or template
* potentially pre- and post-conditions for execution
* definition of workflow execution state
* potentially a definition of user interaction, e.g. how to react to
user choosing terms etc
* activity-based costing data, e.g. ICD codes, charge ids
* qualification - who can perform this Activity?
* scheduling information
Workflows are assumed to be made of sub-workflows and ultimately
Activities. It is assumed so far that there are 3 kinds of workflows:
* imperative - essentially fixed, deterministic; probably good for
mainly admin tasks
* adaptive - workflows that can be modified or executed differently
than the definition, without forcing abandonment
* cooperative - workflows that are adaptive and involve multiple
execution agents.
The ABD work is current research at Intermountain Healthcare, and has at
least 12 months to run. Accordingly, all current thinking is, in the
usual way, somewhat speculative. Implementations are being built to test
the current state of the ideas as they are at any point in time.
The wiki page for posting resources is here
<https://openehr.atlassian.net/wiki/display/spec/questions/42336259/resources-relating-to-adaptive-clinical-workflow-frameworksformalisms>.
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
