Meeting Minutes February 1st 2023
Feb 1st 2023
- Discuss Roles for design iterations
- Choose a direction that we want to go in
Settle on a testing plan for Campus Pharmacy
- We donβt need patients to sign up, pharmacy staff should just be able to add patients, ideally, this would happen via Kroll, but in the absence of the ability to integrate with Kroll, the information can be manually entered, or even added via CSV or something. To express that we could have integration, we can expose an endpoint for adding a user.
First Design Iteration:
- Improve LCD to have more explicit instructions β
- Patient add by CSVβ
- Remove Price Field
- Enter code via keypad sent via SMS β
- Store Pickup Time from door state β
- Allow the pharmacist to authorize the user for the day and display the authorized pharmacist. β
Second Design Iteration:
- Proper unlocking mechanism/self-unlocking hinge
- Lockerbox made of wood, proper screws + hinges β
- Be able to provide a report with time, who retrieved the prescription, what prescription etc., DIN,
Tasks:
- Add all of the tasks to Jira and then assign them appropriately 2.
Roles
- Aliya
- Patient add by CSV
- Lockerbox made of wood, etc
- Hussein 3. Find best SMS solution 4. Integrate SMS solution 5. Work on integration authentication of code with hardware?
- Joshua 6. Improve LCD instructions 7. Integrate keypad into the firmware 8. Lockerbox made of wood, etc 9. Store pickup time from door state
-
Sammy 10. Need the ability of pharmacists to create a patient profile. This profile can be used at any pharmacy. To create a Patient: 1. Full Name 2. Phone Number 3. Date of Birth 11. Allow the pharmacist to authorize the user for the day and display the authorized pharmacist.
This will require coordination with Hussein for the patient notifications