Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

StatusDescriptionTerminal State (Y|N)
ActiveSigned and active for usage referralN
In ProgressService Request is being processedN
CompletedReferral Service Request has been processedY
Entered In ErrorReferral Service Request is cancelled because of human mistake in the process of creationY
CancelledReferral Service Request is cancelled because of absence of necessity and other reasons (for example fraud)Y


State Transitions

From (Status)From (State)To (Status)To (State)MethodNotification to Event Manager (Y|N)Notification to Patient (Y|N)
Active--
UseServiceRequest

Is Used = True

Use Service Request YN
Active--
ReleaseServiceRequest
Is Used = FalseRelease Service RequestYN
ActiveIs Used = TrueIn Progress-

Make Service Request As In Progress

Submit Encounter Data Package

NN
In Progress-Completed
MarkServiceRequestCompleted (through CloseEpisode)
-

Mark Service Request As Completed (Kafka Consumer on Close Episode)

Dispense Service Request

Y
N
Y
Active-Entered In Error-
MarkServiceRequestAsEnteredInError
Recall Service RequestYY
Active-Cancelled-Cancel Service RequestYY
In Progress-Cancelled
MarkServiceRequestAsCancelled
-Cancel Service RequestYY
Completed-Cancelled-
MarkServiceRequestAsCancelled
Cancel Service RequestYN

Open Questions 

QuestionAnswer
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?