3 key areas present significant hurdles:
GOAL: We set out to build a real-time health monitoring and care delivery program, tailored to the specific patient and their chronic disease(s) in order to increase health outcomes and reduce costs to patients and the healthcare system.
Chronic diseases dominate the list of top causes of death and account for 90% of healthcare spend in the US, yet control and clinical outcomes are worsening. Management of chronic diseases, such as hypertension, poses a complex challenge that requires a multifaceted approach that most primary care practices are not equipped to handle.
The Continuous Care Application and accompanying program together are an industry-leading solution designed to revolutionize the management of chronic disease through continuous monitoring and content delivery suited to the patient's unique phenotype. This application is built to provide a seamless and comprehensive approach to monitor, analyze, and support individuals while making the best use of an interdisciplinary health team and innovative technology.
Patient App
The meat and potatoes of the digital program, the app allows patients to track their progress, link multiple devices, receive ongoing content, manage contact with their care team, and receive important notifications, such as reminders to take a reading.
Landing page
The landing page is where patients can learn more about the program as well as initiate the sign-up and onboarding process. This is a key feature as it represents many patients first impression of the program as well as enabling the initial intake of patient information to determine their phenotype.
Big Picture
To determine priorities for engineers to begin the build process, I collaborated with the team to create a detailed user flow of the entire patient journey through the program. The focus was on what would be critical to build from an MVP standpoint, specifically noting where the patient experience is tied to back end development, such as when data would need to be collected and notifications would be required.
Detail
More detailed flows were created to understand specific use cases, such as setting up a device within the program application.