Designing Data Services
Summary
Cross-disciplinary collaboration is key to tackling large scale change in hypertension rates (Margins of Victory) in underserved communities (Innovation at the Margins). Low income minoritized populations have shown to have a high prevalence of hypertension but a low treatment rate . There are many factors that play a role in these statistics many of them which are historical and systemic. In order to design a hypertension study for these populations, co-design methods that emphasize collective good must be employed by a comprehensive team. 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
"Sponsor sessions are not sales pitches; they are content-rich and free to anyone who wants to attend."
Bria AlexanderOpening Remarks
September 9, 2022
"It's surprisingly hard to hire product managers and designers in government; I'm looking at how to unblock those system barriers."
Ariel KennanCivic Design in 2022
January 13, 2022
"You have to learn to read the room and understand what drives the people you’re working with to build coalitions."
Mariah Hay Marina Martin Husani Oakley Eduardo OrtizBUILD: Discussion
June 14, 2018
"It's not the demographics or names that should drive personas, but what people are really trying to do."
Lija HoganContexts of Use: A Framework for Connection
December 9, 2021
"Feedback is a lot like holding up a mirror. You're reflecting what's already working and like using a flashlight to hide in the corners."
Vanessa VarinFeedback: The Other F-Word
September 10, 2025
"Since everyone was doing their own research, the quality of the research being done was pretty inconsistent."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"Sometimes it's just not even related to the research skills, sometimes relationships really matter."
Megan Blocker Mujtaba Hameed Victor UdoewaPanel: Excellence in Impact
March 25, 2024
"Designers need to be facilitators of other people's expertise and knowledge, not just creators of designed things."
Sheryl CababaExpanding Your Design Lens with Systems Thinking
February 23, 2023
"If your priorities are roughly aligned with organizational priorities, you’ll be making good trade-offs."
Harry Max Jim MeyerPrioritization for Leaders (2nd of 3 seminars)
June 27, 2024
