A doctor approached me with a problem: despite advancements in technology and improvements in electronic health record (EHR) systems in recent years, patients' progress notes that doctors must record in the hospital are still largely manual and incredibly tedious. This inefficiency often causes miscommunication between doctors and even the neglect of serious medical issues, sometimes leading to tragic consequences.
As a hypothetical solution to this problem, I am designing an organization tool that could automate hospital patient notes, relieving strain and saving time for doctors.
I recruited a team of my peers through the multiple stages and domains required to complete this project. This included user research, which I led on a high level, as well as product design, which I am choosing to contribute to more directly. Below is the Figma file showcasing many steps of my design process, including the tool's features, rough sketches, and wireframes for a few key screens.
I want to focus on one particular screen that represents a novel solution for the progress note-taking process.
This would be the screen where doctors can input patients' symptoms, or "issues". There are a few key solutions here:
a) The software would auto-populate some fields, such as "System" based on the Issue.
b) It still incorporates an assessment ("Working diagnosis") and plan, which all doctors are accustomed to including in their progress notes.
c) Fields like "Date and time recognized" carry over into each day of the patient's stay; there's no need to rewrite this information every day.
d) From the information provided, the system would automatically create three documents each day that would streamline patient care and minimize confusion and redundancy.