Difference between revisions of "CSCR-116 add subsetCode, checkPointCode to sourceOf and targetOf Act relationships (Rx harmonization)"
Riksmithies (talk | contribs) |
Riksmithies (talk | contribs) (→Issue) |
||
Line 14: | Line 14: | ||
For Rx to be conformant to Clinical Statement, CS needs to add: | For Rx to be conformant to Clinical Statement, CS needs to add: | ||
subsetCode [optional, 0..1, ActRelationshipSubset] | subsetCode [optional, 0..1, ActRelationshipSubset] | ||
+ | |||
and | and | ||
checkPointCode [optional, 0..1, ActRelationshipCheckPoint] | checkPointCode [optional, 0..1, ActRelationshipCheckPoint] | ||
+ | |||
to sourceOf and target of Act relationships. | to sourceOf and target of Act relationships. | ||
Revision as of 23:35, 15 January 2013
Back to Clinical Statement Change Requests page.
Submitted by: Rik Smithies | Revision date: <<Revision Date>> |
Submitted date: 09-Jan-2013 | Change request ID: CSCR-116 |
Issue
From Rx alignment sheet (posted to list 9th Jan)
For Rx to be conformant to Clinical Statement, CS needs to add: subsetCode [optional, 0..1, ActRelationshipSubset]
and checkPointCode [optional, 0..1, ActRelationshipCheckPoint]
to sourceOf and target of Act relationships.
Use case in Rx for subsetCode is with FLFS relationship to say that only acts in future will fulfill. (Not certain why that is needed, maybe to show this Rx has not already been fulfilled). Subsetting of act relationships in general seems a good use case however.
Use case checkPointCode in Rx Med Order is in precondition and trigger ARs "A code specifying when in the course of the substance administration a precondition for the administration is evaluated."
Recommendation
Add to sourceOf and target of Act relationships: subsetCode [optional, 0..1, ActRelationshipSubset] and checkPointCode [optional, 0..1, ActRelationshipCheckPoint]
Rationale
Discussion
Recommended Action Items
Resolution
TODO Motion to accept: ?,? Against: 0; Abstain: 0; In Favor: 0 ?carried