Web | Care Standards | Doctors
I created interaction and UI designs for CDS Connect, the first public web repository for CDS tools, by working with leaders from the Agency for Healthcare Research and Quality (AHRQ), and the Center for Disease Control (CDC). CDS Connect has now successfully scaled to more than 50+ tools and 30+ healthcare organizations collaborating to drive its development.
I was a lead designer in a core 6 person team of 2 designers, 2 engineers, 1 product manager, and 1 SME.
I executed on interaction design, UI design, design validation, and client management for all examples shown below.
5 months | 2/2016 - 7/2016
Agency for Healthcare Research and Quality
CDS tools (Clinical Decision Support) are modules that can be implemented within EHRs (Electronic Health Records), to improve quality of care by helping doctors make clinical decisions that follow the most up to date standards of care.
Currently, evidence-based standards of care are not universally followed. One reason is that there is no easy way for doctors to explore and obtain CDS tools.
CDS Connects product goal was to create a public web repository that allows any doctor to share, use, and improve clinical decision support (CDS) tools.
CDS Connects business goal was to release a beta version of CDS Connect to begin growing its collaborators and content.
CDS Connect, as of August 2019
User needs and insights were synthesized through qualitative data I gathered from monthly user feedback meetings of 15 subject matter expert doctors and leaders in the field of clinical medicine, health IT, and public health, from the Agency for Healthcare Research and Quality (AHRQ) and the Center for Disease Control (CDC).
These meetings served as opportunities for me to ask questions and gather qualitative information on pain points related to finding and using CDS tools.
Insights were used to collaboratively sketch concepts with my design colleague, and iterated based on continual feedback from the monthly panel of experts, as well as weekly feedback from core team members and our primary doctor SME whom was also a clinical informaticist.
I took this approach as doctors did not always know the exact CDS tool they were looking for. The challenge was that doctors may be looking from the perspective of types of conditions, latest guidelines, type of tool, or medical specialty. The search interaction had to take all perspectives into consideration, leading me to design multiple ways of exploring the set of CDS tools.
Similar to YouTube playlists, “Topics” are created groupings of content under which CDS tools can be organized, whether they be under a certain patient population, condition, a specific published guideline, or a new grouping which uniquely fits for a type of practice or clinical situation.
Once a doctor enters a CDS tool page, they can explore what the tool does, how it should be used, and any evidence that is driving the content.
Evidence-driven medicine is of utmost importance to doctors. Therefore, to build trust, my colleague and I designed multiple ways of showing how a CDS tool evolved from creation, to where it is today.
In earlier designs, this started from showing the authors of the tool. The doctor could then explore information on the guideline or source driving the tool, as well as its status for readiness of use.
After sharing this apporach to the panel of 15 clinicians and health informaticists at AHRQ and CDC, I found that information on the source and status for readiness of use was far too important to be hidden behind additional clicks.
To further push transparency, early versions included concepts displaying data on use of the tool by doctors over time. This also had the added benefit of using social data to demonstrate efficacy and trust in the tool.
These concepts, despite receiving highly positive qualitative feedback from doctors at AHRQ and CDC, had some key issues:
I scaled back these features in later versions to a more implementable text area, from which doctors could provide written accounts of CDS tool use, and removed the example implementations section.
Concepts like displaying data on use of the tool, was saved in the design documentation to be implemented at a longer term date.
CDS Connect onboarding
CDS tool exploration
CDS Connects product goal was to create a public web repository that allowed any doctor and health informaticist to share and use clinical decision support (CDS) tools.
CDS Connects business goal was to release a beta version to begin growing its collaborators and content.