Designing Data Services
Summary
Our process to build this study focused on sharing power with members of the community to decentralize the designer and build design capability with the participants. We prioritized building relationships to combat mistrust of healthcare professionals and address difficult topics like social determinants of health (healthcare access, housing challenges, employment, etc) – both key factors in high hypertension rates.
This presentation will bring together the collaborative team that built the Pressure Check study. First, a Yale cardiologist who is an expert in this space and acknowledges the influence and perspective that the design process can provide. The second speaker is a design research and strategy professional who defined an inclusive and relational protocol that tapped into the deepest needs of the study community and translated them into the study materials. The third, is a visual designer who incorporated the learnings into patient education and study tools to overcome deeply ingrained perspectives on healthcare. This team and the outputs demonstrate how critical it is to have a team that brings in shared and lived experiences into service design.
Key Insights
-
•
Lack of interoperability between healthcare IT systems causes delays and disrupted patient care, as seen in John’s genomic test example.
-
•
Genomics England moved from a research project to an integrated platform supporting NHS routine care with genomic data.
-
•
Modular data services using common data standards enable flexible, reusable technical components for multiple healthcare applications.
-
•
Service designers at Genomics England work alongside engineers and bioinformaticians early to ensure technical infrastructure serves real-world needs.
-
•
Service maps help identify data transformation patterns to create standalone data service modules usable across different use cases.
-
•
Designing data services focuses on developers as primary users, enabling them to build clinician-facing services like cascade testing or trial selection.
-
•
Comprehensive documentation, developer tooling, and support channels are critical to developer adoption of data services.
-
•
Framing data services through patient and clinician perspectives helps stakeholders make informed decisions and fosters broader inclusion.
-
•
Service design applied at the technical data layer can have exponential impact by aligning infrastructure with business objectives and user needs.
-
•
Collaboration and curiosity enable service designers to overcome intimidation by technical layers and build shared language with developers.
Notable Quotes
"The lack of consistency between healthcare IT systems causes critical information delays and interrupted care."
"Data standards are like selecting English as the common language, even if systems natively speak Portuguese or Spanish."
"Service designers embedded in leadership can preempt strategic directions and influence technical projects early."
"We are designing data services for developers, not final clinician-facing experiences."
"APIs need to provide capabilities like verifying patient identity to ensure data access is accurate and secure."
"Imagine data capabilities as Lego bricks versus a box set with instructions to build specific models."
"Developer experience hinges on clear documentation, sandboxes, sample data, and responsive support."
"Speculative use cases connect technical components to human impact and help prioritize work into slices of value."
"Don't shy away from technical conversations; service designers should map data journeys like user journeys."
"The impact of service design at the data service level is exponential, making infrastructure more human scale."
Or choose a question:
More Videos
"VOC wasn’t a replacement for user research, but an enhancer that captured nuggets researchers might miss during discovery."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"When you’re in a culture that celebrates complexity, making things simple is still a very hard thing to do."
Peter MorvilleThe Architecture of Understanding
May 13, 2015
"I was kind of wandering around aimlessly trying to find the next job."
Renee ReidBecoming a ResearchH.E.R (Highly Enterprise Ready)
June 3, 2019
"You don’t need special software to get started analyzing gestures and embodied actions; you just need video and a notepad."
Dane DeSutterKeeping the Body in Mind: What Gestures and Embodied Actions Tell You That Users May Not
March 26, 2024
"A good two-factor system offers multiple methods, like authenticator apps, calls, and texts, with generous timeouts."
Sam ProulxOnline Shopping: Designing an Accessible Experience
October 3, 2023
"While technical errors matter, broader issues like content relevance and navigation create more mission failures."
Andrew Custage Michael MallettThe Digital Journey: Research on Consumer Frustration and Loyalty
March 29, 2023
"The primary goal of a hackathon is the community building aspect and getting people to talk to each other and learn from each other."
Shelby SwitzerMaking Space for Community Knowledge-sharing in a Distributed World
December 10, 2021
"We should think of AI as something that amplifies what we already are: if we think research is about impact, AI will help us understand and track it."
Llewyn PaineCoexisting with AI: A practical guide for researchers to navigate tools, ethics, and integration
March 11, 2025
"Researchers make customers visible inside the organization, but also help the organization learn about itself."
Robin BeersNavigating organizational systems: Rethinking researcher’s role in driving change
March 13, 2025
