This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Add ControlAct to CDA Header"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
|||
| Line 31: | Line 31: | ||
== Resolution == | == Resolution == | ||
| − | + | 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. | |
Revision as of 15:25, 21 July 2009
Return to SDTC page; Return to CDA R3 Formal Proposals page.
| Submitted by: René Spronk | Revision date: <<Revision Date>> |
| Submitted date: <<Submit Date>> | Change request ID: <<Change Request ID>> |
Issue
- 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.
Recommendation
- Add a ControlActEvent class (classCode CACT) with as its subject the Document header.
Rationale
- 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).
Discussion
Recommended Action Items
Resolution
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.
