This wiki has undergone a migration to Confluence found Here
Difference between revisions of "PCCR-030-New trigger events"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
== Discussion == | == Discussion == | ||
+ | Jan 2012 PC: | ||
+ | |||
+ | two of these are already present, or do make little sense. However the nullify interaction does help to solve some issues with the ability to cancel a request and simply send a new one when due time. suspend would require the receiver to keep records of patients not accepted which does not look a valid use case. | ||
== Recommended Action Items == | == Recommended Action Items == |
Revision as of 22:47, 17 January 2012
ID | PCCR-030 |
Description | New trigger events |
Submitted by | Results from analysis "Evaluating HL7 Care Provision DSTU" |
Submitted date | 2010-10-05 |
Status | approved |
Priority | medium |
Please note:
Back to Patient Care Change Requests page.
|
Contents
Issue
Continuing Care in Ontario requested additional dynamic models in Care Provision. These include: a need to add 3 new trigger events (and corresponding interactions) for
- Suspend Care Transfer Request
- Resume Care Transfer Request
- Nullify Care Transfer Request
Recommendation
Patient Care Topic / Artefact
Dynamic Model
Rationale
Discussion
Jan 2012 PC:
two of these are already present, or do make little sense. However the nullify interaction does help to solve some issues with the ability to cancel a request and simply send a new one when due time. suspend would require the receiver to keep records of patients not accepted which does not look a valid use case.
Recommended Action Items
These are available in a walkthrough format. Need to be discussed in PC. Sept