This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "CSCR-121 expand ControlAct to have AUT and RESP participations (Rx harmonization)"

From HL7Wiki
Jump to navigation Jump to search
Line 12: Line 12:
 
From Rx alignment sheet (posted to list 9th Jan)
 
From Rx alignment sheet (posted to list 9th Jan)
  
TODO
+
THIS IS COMPLETE BUT MAY NEED TIDYING
 +
 
 +
For CsControlActs in CS and Rx:
 +
 
 +
CS has just a CACT and subjectOf pointing to choice box, outgoing only, nothing incoming.
 +
 
 +
Rx DMIM has that too
 +
CACT attributes are a fit.
 +
But it also adds AUT or RESP to assigned person or assigned device.
 +
 
 +
CS AUT and RESP (off choice) goes to AssignedEntity, which assume is superset of AssignedPerson and AssignedDevice (looks to be but not double checked)
 +
 +
And Rx has an A_DetectedMedicationIssue on it (previously called IssueEvent)
 +
Which is a whole area featuring ALRT, is a subtype of OBS. Seems as if would be CS compatible (even if minor changes needed, hence don’t need to add it as a CMET itself)
 +
 
 +
So seems if CACT was in choice box that would cover it, but that is overkill.
 +
 
 +
Alternative that is less modelling, and adding less unneeded stuff is:
 +
Add AUT and RESP to ControlActEvent as shadows (since these go to AssignedEntity and so AssignedPerson and AssignedDevice and add note to say intended use) (assuming this way to use shadows works - you only get the bits on the "end" of the arrow, not the start).
 +
Add a subjectOf act rel back to Observation in choice box as a shadow (for ALERT and so rest of CMET) . That way we don’t link to entire choice or have a messy act relationship going all the way up the diagram, or moving too much around.
  
 
== Recommendation ==
 
== Recommendation ==

Revision as of 00:04, 16 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-121

Issue

From Rx alignment sheet (posted to list 9th Jan)

THIS IS COMPLETE BUT MAY NEED TIDYING

For CsControlActs in CS and Rx:

CS has just a CACT and subjectOf pointing to choice box, outgoing only, nothing incoming.

Rx DMIM has that too CACT attributes are a fit. But it also adds AUT or RESP to assigned person or assigned device.

CS AUT and RESP (off choice) goes to AssignedEntity, which assume is superset of AssignedPerson and AssignedDevice (looks to be but not double checked)

And Rx has an A_DetectedMedicationIssue on it (previously called IssueEvent) Which is a whole area featuring ALRT, is a subtype of OBS. Seems as if would be CS compatible (even if minor changes needed, hence don’t need to add it as a CMET itself)

So seems if CACT was in choice box that would cover it, but that is overkill.

Alternative that is less modelling, and adding less unneeded stuff is: Add AUT and RESP to ControlActEvent as shadows (since these go to AssignedEntity and so AssignedPerson and AssignedDevice and add note to say intended use) (assuming this way to use shadows works - you only get the bits on the "end" of the arrow, not the start). Add a subjectOf act rel back to Observation in choice box as a shadow (for ALERT and so rest of CMET) . That way we don’t link to entire choice or have a messy act relationship going all the way up the diagram, or moving too much around.

Recommendation

  • todo

Current Rx Rx CACT.png Proposed CS to do the same CS Rx CACT.png

Rationale

Discussion

Recommended Action Items

Resolution

TODO Motion to accept: ?,? Against: 0; Abstain: 0; In Favor: 0 ?carried