CSCR-068 Change fixed contextControlCodes to defaults
Editing of Change Requests is restricted to the submitter and the co-chairs of the Clinical Statement Project. Other changes will be undone. Please add comments to the "discussion" page associated with this Change Request.
Back to Clinical Statement Change Requests page.
|Submitted by: Rik Smithies||Revision date: 20-Jun-2006|
|Submitted date: 20-Jun-2006||Change request ID: CSCR-068|
Several relationhips in the pattern have contextControlCode fixed, in effect, because they use a specific value and no there are no subtypes of any ContextControl values.
The consumable participation has contextControlCode fixed to "AN", additive non-propagating. Whilst I agree that you may not normally want the CSM to conduct down, it seems strange to have the context fixed at "additive". What would it mean to add two CSM participations ?
responsibleParty is similary fixed at "AP". Would you never want this to override other parties specified further up ?
ControlActEvent.subjectOf.contextControlCode is fixed at AN also.
Is it possible that some of these were meant to be defaults rather than fixed values ? Most contextControlCodes in the model specify just defaults.
- Suggest consumable.contextControlCode is relaxed to a vocab of "ContextControl" with a default of "ON"
- Suggest responsibleParty is treated similary and relaxed to a vocab of "ContextControl" with its existing value "AP" made the default.
- Suggest ControlActEvent.subjectOf.contextControlCode is treated similary and relaxed to a vocab of "ContextControl" with its existing value "AN" made the default.
Support to maintain consistency.
Recommended Action Items
Jan 11, 2007 - Motion (Rik, Patrick) to accept suggestions as stated. Against: 0, Abstain: 9, In Favor: 15
Jan 25, 2007 - 0.2.4.02 of CSP updated - CVB