Difference between revisions of "XDW Minutes 2011.06.06"
Jump to navigation
Jump to search
(Created page with " == No “conflict” of two approaches, but rather a possible complementation == * The purpose of XDW is to document workflow-steps of the “past”. :* To predict/trigger t...") |
|||
| Line 3: | Line 3: | ||
== No “conflict” of two approaches, but rather a possible complementation == | == No “conflict” of two approaches, but rather a possible complementation == | ||
| − | * The purpose of XDW is to document workflow-steps of the | + | * The purpose of XDW is to document workflow-steps of the “''past''”. |
:* To predict/trigger the next workflow-step has been left out of XDW | :* To predict/trigger the next workflow-step has been left out of XDW | ||
| − | * The purpose of HL7 messages are to trigger workflow-steps in the | + | * The purpose of HL7 messages are to trigger workflow-steps in the “''future''”. |
:* To persist the “path” of workflow steps is a weakness of messages | :* To persist the “path” of workflow steps is a weakness of messages | ||
| − | * Conclusion | + | * Conclusion |
| + | :* HL7 messages would add functionality to XDW - both concepts complement each other! | ||
== The complexity of dealing with the topic “What’s the current status of an order” == | == The complexity of dealing with the topic “What’s the current status of an order” == | ||
Latest revision as of 11:26, 7 June 2011
No “conflict” of two approaches, but rather a possible complementation
- The purpose of XDW is to document workflow-steps of the “past”.
- To predict/trigger the next workflow-step has been left out of XDW
- The purpose of HL7 messages are to trigger workflow-steps in the “future”.
- To persist the “path” of workflow steps is a weakness of messages
- Conclusion
- HL7 messages would add functionality to XDW - both concepts complement each other!
The complexity of dealing with the topic “What’s the current status of an order”
- It's not addressed in XDW
- The topic is shifted to the domain which uses it
- The paradigm is:
- An actor performs a workflow step and doesn’t care about the next step
- All the business logic for determine the new status of this order is at the “succeeding” actor and has to be performed “before” executing the “next” workflow-step
- It is addressed by HL7 messages
- They have to deal with that because they want to trigger the next step
- The paradigm is:
- An actor performs a workflow step AND performs the business logic to the determine the “new” status
- All the business logic for determine the “new” status of this order is at the “preceding” actor and has to be performed “after” executing the “current” workflow-step
Overall conclusion
- The question is whether XDW should be enhanced by a messaging concept to add the functionality of “triggering future workflow-steps”.