Plain-Language Lab Result Review
Design a patient result view that explains one lab panel without turning reference ranges into a diagnosis.
The brief
Understand the problem
Background
Patient portals often publish values before a clinician has discussed them. Bold abnormal flags can create alarm even when context, trends, medicines, and individual reference ranges matter.
User context
Meena sees that one thyroid result is outside the displayed range. She wants to understand what the test measures, whether her clinician has reviewed it, and what happens next.
Product problem
Patients need accessible explanations and follow-up status while clinicians need room to interpret results in context.
Objective
Create a result summary, value explanation, trend view, and question handoff for a routine lab panel.
What to design
Define the experience
Required experience
- See review status and the panel summary
- Open a value for plain-language context
- Compare the value with prior results
- Send a focused nonurgent question to the care team
Screens and states
- Lab panel summary
- Result explanation
- Trend history
- Care-team question
Core user flow
Follow the critical path
- 01
Meena opens the thyroid panel and sees that clinician review is pending
- 02
She reads what the flagged test measures and why ranges vary
- 03
The trend view shows a gradual change rather than a single isolated value
- 04
She sends a question and sees the expected response window
Product rules
Requirements and constraints
Requirements
- Show specimen date, reference source, review status, and units
- Explain high, low, and in-range values without diagnosing
- Pair charts with a readable table and data labels
- Separate routine messaging from urgent symptom guidance
Constraints
- Reference ranges may vary by laboratory and patient context
- The interface cannot infer treatment from one value
- Sensitive result previews must respect authentication settings
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens covering an abnormal value and clinician follow-up
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Yeseva One & Josefin Sans
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Yeseva One & Josefin Sans
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
