Hello Thomas, I would like to refer you to CMMN <http://www.omg.org/spec/CMMN/>. It seems to mostly have all the attributes u define for "Activity".
CMMN does not define "flows" as BPMN does, its more of a "business event" based workflow definition centred around data rather than process. CMMN defines CaseFile (probably implemented using OpenEHR data models) to store all data related to a case. A small brief, based on your "Activity" definition: - Semantic model includes things like CasePlan, PlanningItem, Task (HumanTask, ProcessTask, CaseTask) which can define a case plan to solve a "case", which in this case is the process of providing "patient care". Concept of Stage can be used to group tasks together as a logical unit. Concept of Milestone, to signal something important. Concept of UserEvent and TimerEvents to - Has the concept of Entry and Exit Sentry, which in turn has 2 parts, one to implement "events" other to implement arbitrary business logic. This can be applied to any PlanningItem (refers to a Stage or Task). Has constructs like, "activation", "repeat", "discretionary tasks" etc. - Every Task/Stage/Milestone/Event has a well defined lifecycle to control their states. - HumanTask coupled with forms can probably model all user interactions - Tasks can be "assigned" to individuals using custom extensions to CMMN specification. PlanningTable can help with deciding who can perform the tasks under what context. - Concept of CaseFileEvent to react to changes in CaseFile data. Along with BPMN2.0, I think we can define very complex "flows" and also be "adaptive". So the idea is to use CMMN to define "WHAT" of a process and BPMN2.0 to define "HOW" of that process. We have successfully used this combination to drive very complex flows in ECommerce business operations. however I think that the combination of BPMN and CMMN can be used to model quite complex flows in clinical work flows as well. "Adaptive Case Management" <http://bpm.com/docs/Taming_the_Unpredictable_Digital_Edition.pdf> Thanks and regards, Subhro. (i am not a PHD or a research scholar, so pl forgive my ignorance, if this does not help with the topic) On Wed, Apr 13, 2016 at 6:42 PM, Thomas Beale <[email protected]> wrote: > > 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 >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
