...
| Status | Description | Terminal State (Y|N) |
|---|---|---|
| Active | Signed and active for usage referral | N |
| Used | Referral has been already used and could not be used anymore without rolling back | N |
| In Progress | Refehhal has been already used and taken into workN | |
| 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 | In Use- | UseServiceRequest | YY | N | Used | ||||
| Active | RollBackServiceRequest | Y | Y | Used | In Progress | MarkServiceRequestAsInProgress (through CreateEncounter)- | ReleaseServiceRequest | Y | N |
| In ProgressActive | Completed | MarkServiceRequestAsCompleted MarkServiceRequestCompleted (through CloseEpisode) | Y | N | |||||
| Active | Entered In Error | MarkServiceRequestAsEnteredInErrorRecallServiceRequest | Y | Y | |||||
| Active | Cancelled | MarkServiceRequestAsCancelledCancelServiceRequest | Y | YUsed | Cancelled | MarkServiceRequestAsCancelled | Y | Y | |
| In Progress | 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? | |