Add ControlAct to CDA Header
|Submitted by: René Spronk||Revision date: <<Revision Date>>|
|Submitted date: <<Submit Date>>||Change request ID: <<Change Request ID>>|
- CDA R2 doesn't support workflow. This principle was re-enforced during a meeting of O&O and other WGs during the WGM in Orlando (January 2009). This proposal seeks to introduce a mechanism in CDA R3 whereby one could support workflow.
- Add a ControlActEvent class (classCode CACT) with as its subject the Document header.
- The proposed change allows for the identification whether the document contents are "for information only" or whether any acts requested in the document should actually be performed (and by whom).
Recommended Action Items
Intent of the document is to reflect the static model. Any workflow management control is outside the document. This applies only to the header. Proposal rejected. See SDWG minutes from 7/21/2009 for details:
From the minutes
Request to add a control act to the CDA header. After some discussion, the commonly held view by participants is that the document is a static model. We assume that the dynamic behaviors are in the messages or in the web services layers used to transport the document.
Motion: Intent of the document is to reflect the static model. Any workflow management control is outside the document. This applies only to the header. By: Hans, Second: Liora Abstain: 0 Against: 0 For: 16 Motion passed
Note: Based upon this committee vote, the original proposal submitted was rejected.