Skip to end of metadata
Go to start of metadata
You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 16
Next »
| Status | Description | Terminal State (Y|N) |
|---|
| Active | Signed and active for usage referral | N |
| Completed | Referral has been processed | Y |
| Entered In Error | Referral is cancelled because of human mistake in the process of creation | Y |
| Cancelled | Referral is cancelled because of absence of necessity and other reasons (for example fraud) | Y |
State Transitions
| From | To | Method | Notification to Event Manager (Y|N) | Notification to Patient (Y|N) |
|---|
| Active | - | UseServiceRequest | Y | N |
| Active | - | ReleaseServiceRequest | Y | N |
| Active | Completed | MarkServiceRequestCompleted (through CloseEpisode) | Y | N |
| Active | Entered In Error | MarkServiceRequestAsEnteredInError | Y | Y |
| Active | Cancelled | MarkServiceRequestAsCancelled | Y | Y |
| Completed | Cancelled | MarkServiceRequestAsCancelled | Y | N |
Open Questions
| Question | Answer |
|---|
| There are cases, when sending notification about transition of referral to status B is not very necessary (because it has happen from status A) and due to cost of notification may not be implemented, and at the same time there are cases, when sending notification about transition to status B is obligatory (because it has happen from status C). How we can handle it? |
|
|
|
|
|