The 2.5-month research led our team back to the very beginning, but we pulled ourselves up by the bootstraps and generated potential paths to pursue. During our conversation with the client, we found out what our client really wanted was the structured database itself. They were eagerly looking for a database that makes it easy to store and extract patient data to create a research registry.
A new path & understanding current workflow
With the newly set goal of transforming clinical melanoma tumor board documentation into research-ready data, we investigated the University Hospitals workflow. We specifically looked into the workflows of tumor board coordinators and researchers as they are the 2 main stakeholders. Since both of them work with privacy-sensitive patient data, we crafted 2 creative methods to hone down on what the workflows looked like. We named them: simulated environment observation and real-life diary checkins. With these two approaches, we were able to obtain the most accurate workflow and learn how to create the best value for them.
We observed 2 processes related to clinical melanoma data are occurring:
Tumor board report preparation
Data extraction for research
[a] systems a tumor board coordinator goes through
[b] systems a research goes through
These two processes both consist of someone digging through multiple hospital digital systems, including Electronic Health Record, department-specific software, and Google Drive, to gather relevant data. Informed by our client, there is also an overlap in the data for tumor boards and the data needed for research. Thus, we speculate that it is possible to consolidate the two efforts into a single database — what we are calling, the MELAbase.
[ Before ]
[ After ]