Summary
Documentation technology is the foundation of modern healthcare delivery. Convoluted, redundant, and excessive documentation is a pervasive problem that causes inefficiency in all aspects of the industry. At IncludedHealth, we are developing an AI-assisted documentation that summarizes and documents conversations between patients and their care providers. A care provider can push one button and have their entire patient encounter captured in a succinct and standardized format. Upon a pilot launch, the results were staggering. Within 6 months, we demonstrated a 64% reduction in time per encounter! However, despite our promising results, there still remain challenges specific to the demands of the healthcare domain. As our team continues to develop solutions to meet these challenges, we gain even more clarity on what it takes to design a human-backed, AI-powered healthcare system. Takeaways From this session, you can expect to learn the following: Developing AI design in healthcare requires close collaboration between end users and your data science team Piloting GenAI solutions may be more effective than traditional prototyping Trading accuracy for efficiency is a barrier to adopting GenAI tools in healthcare GenAI design in healthcare requires establishing critical boundaries as well as a good understanding of cognitive processing Other factors to consider when designing AI solutions for service-based industries are understanding how training might be impacted, the importance of standardization vs. personalization of data output and the need for more autonomy and control elements due to consequences of unpredictable output errors
Key Insights
-
•
Generative AI can reduce healthcare documentation time by over 60% but doesn't eliminate the need for manual editing and human review.
-
•
Focusing AI tools initially on low-risk use cases like chat encounter summaries mitigates potential clinical harm.
-
•
Large Language Models (LLMs) excel at summarizing text but struggle with capturing exact clinical details and non-verbal cues.
-
•
Designing AI tools requires managing user expectations to prevent disappointment and frustration over imperfect outputs.
-
•
A simple one-button UI with options to regenerate and manually edit notes improves user workflow efficiency and error recovery.
-
•
Implicit metrics such as the 'edit rate'—the fraction of user edits on AI-generated text—help monitor AI output quality unobtrusively.
-
•
Traditional prototyping methods are less effective for AI; incremental live pilots provide critical learning about AI's unpredictable outputs.
-
•
Operational factors like quality assurance metrics impact user attitudes when AI-generated notes lower scores despite time savings.
-
•
Human-centered collaboration between designers, data scientists, and users is essential to shape AI capabilities and discover unforeseen problems.
-
•
AI models must remain static (non-learning) in healthcare to comply with regulations, creating challenges for ongoing improvements.
Notable Quotes
"We saw documentation time reduced by 64% after six months of using the AI tool."
"Documentation is important for liability and useful for patient handoffs, so notes must be concise yet detailed."
"Healthcare is not a silver bullet for AI; a lot of context comes from non-verbal cues where generative AI doesn’t apply."
"The unpredictable black box nature of LLMs means we had to zoom in on small problems first before seeing the bigger picture."
"We emphasized a simple one-button workflow with manual editing and regeneration to handle inevitable AI errors."
"The edit rate, our metric of human-added characters over total characters, tracks AI output quality without burdening users."
"Users were initially excited but six months later expressed frustration and uncertainty about the tool’s usefulness."
"We believe cognitive biases like frequency bias and expectation bias affected how users perceived AI errors over time."
"Our AI tool doesn’t learn from ongoing use due to regulatory constraints, which led to user frustration when performance didn’t improve."
"People are the plot twist in this journey — despite promising AI, only human connection reveals new problems and solutions."
Or choose a question:
More Videos
"Most people with my assistive technology might learn to use the system at a different pace than non-disabled users."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"We’re trying to build a design operations role that balances top-down governance with bottom-up community building."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"The rebrand caused our NPS to plummet and freaked out our executives — that was the trigger to get serious."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Leadership doesn’t only mean managing; it can be mentoring, product leadership, or technical influence."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The chief of staff serves as a bridge between the design program managers, executive assistants, and other ux and product chiefs of staff."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Design takes on a new role as governance practitioner, overseeing branding, content, and accessibility."
Amy EvansHow to Create Change
September 25, 2024
"Super intelligence is the power to gather and share knowledge consistently to ensure no gaps in communication."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"The enterprise feels like a big elephant; different people touch different parts and argue what it really is."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"We wanted a living network of knowledge so yesterday’s insight connects to today’s evidence and tomorrow’s learning."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
