4. Dashboard's User Stories - "Suspect Case" Stage

[codecakes]

------------- DESCRIPTION --------------- (The stages don't describe an exhaustive use case but should be enough to fill in the wireframe)

As an agent, from the list of cases of a hospital im managing, I can click on the 1st stage to check all open suspect cases.

Clicking on a suspect cases opens a new perspective which contains form fields within Single Page App dashboard.

From here I can go back or fill in the fields.

As the staff in charge I can decide that the suspect-patient be allowed to be move to the next stage to get tested (Case 1) or to not get tested and instead be skipped to "Closed case" stage (Case 2).

Every ticket should have a standard black on white background), and the high-priority tickets should turn red. To determine if a ticket is high priority, it is important to understand that there is an Assigned Doctor Field along with Approved by field, the same Medical Officer/Doctor-On-Call field for all stages (assuming A doctor has been assigned/someone diagnosing the patient).

To determine, which action to take:

• In Suspect Stage: —> If they have approved the patient for testing and the case is awaiting for 24hrs, it should throw notification alert —> If they have approved to be clear, they can skip to closing stage, the penultimate stage. But if they're still there for 24 hrs, the same action as above.

----------------- TO DO'S -----------------

• [x] Make each patient case (i.e. each row in the table) clickable, such that clicking it will open a new perspective containing form fields and information about the patient.
• [x] Within this new perspective, create the following sections:

1. Agent Roster assignments

   • Case ID: ALPHANUMERIC
   • Case Stage: CHOICES[STRING]
   • Created By: UserID(Fkey) [editable]
   • ClosedBy: UserID(Fkey) [editable]

2. Patient Details:

   • Name: STRING
   • Age: INT
   • Residential Status: CHOICE/STRING
   • Address: VARCHAR
   • ContactNumber: BIGINT
   • Temperature: FLOAT [editable]
   • DOB: DATETIME64
   • Co-existing diseases: ARRAY[STRING] [editable]
   • History of contact: ARRAY[STRING] [editable]
   • Travel history: ARRAY[STRING] [editable]

(Note that there are more form items that will need to be added in the next stages/To-Do's/issues, and so there is no need to format it well for now)

• [ ] Verify that it is actually POSSIBLE to edit the form fields where needed
• [x] Within the same perspective, add a BUTTON TO CLOSE the current perspective and go back to the list of all "Suspect Cases"
• [ ] Create conditions:
• Case 1: If the staff in charge approves, patient is allowed to be move to the next stage ("Test Results") -> Approved for Testing.
• Case 2: Staff in charge decides that testing is not required, and so skip suspect-patient to the "Closed case" stage -> Approved for "Closing Stage".

Sketches:

First, the following picture is the view that will pop up when we click on a ticket. Basically, some of the fields are non-editable, and some will be editable, that's why there's a save and cancel button:

A more detailed flow: Once all the necessary fields have been filled and approved, then only the Agent User can move the ticket to the next stage. However the stage modal DOES NOT Pop Up Instantly. An Alert notification is sent to the Assigned User to "Fill the Necessary Details Within X hrs". In this time the agent can fill the necessary steps for the new modal fields. Else when X hrs pass, the ticket is Flagged RED.

Show "Move To" button Enabled Only When Doctor Approves as follows:

• Show Message Approved by Doctor for 1. Testing or 2. Closing Stage only when All necessary Agent fields filled. Else
• Show Message Not Approved by Doctor.

[codecakes]

@joeydebreuk Every ticket should have a standard black on white background), and the high-priority tickets should turn red. To determine if a ticket is high priority, it is important to understand that there is an Assigned Doctor Field along with Approved by field, the same Medical Officer/Doctor-On-Call field for all stages (assuming A doctor has been assigned/someone diagnosing the patient).

[joeydebreuk]

I'll wait with doing design details until we have sketches. I'll just setup the form modals and a way to store the data in browser for now.

[joeydebreuk]

Im not quite sure how to implement: Case 1: If the staff in charge approves, patient is allowed to be move to the next stage ("Test Results") -> Approved for Testing. Case 2: Staff in charge decides that testing is not required, and so skip suspect-patient to the "Closed case" stage -> Approved for "Closing Stage".| Should I add two button at the bottom of the form?

[codecakes]

@joeydebreuk @ksr89 @kelushly just updated with sketches above. ☝️

Im not quite sure how to implement: Case 1: If the staff in charge approves, patient is allowed to be move to the next stage ("Test Results") -> Approved for Testing. Case 2: Staff in charge decides that testing is not required, and so skip suspect-patient to the "Closed case" stage -> Approved for "Closing Stage".| Should I add two button at the bottom of the form?

[joeydebreuk]

@codecakes one of the form fields is "Case Stage: CHOICES[STRING]" But isnt that covered by the "move" select at the bottom?