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) |
Rene spronk (talk | contribs) |
||
| Line 16: | Line 16: | ||
== Recommendation == | == Recommendation == | ||
| − | * | + | *Add a ControlActEvent class (classCode CACT) with as its subject the Document header. |
| + | |||
| + | [[Image:CDA R3 controlAct.gif|300px|center|thumb|Proposed extension (select to enlarge view)]] | ||
| + | |||
== Rationale == | == 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 == | == Discussion == | ||
Revision as of 15:14, 16 February 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
(Resolution is to be recorded here and in the referenced minutes, which are the authoritative source of resolution).
