MHealth Trizetto
From reactive sick care to proactive, connected care. MHealth Trizetto brings patient-generated health data, practitioner visibility, and care coordination into one experience, built around a critical question: how might a patient, their doctor, and the care team recognize a developing risk and coordinate the next step?
A patient’s health risk shouldn’t exist in disconnected systems
Continuous Glucose Monitoring made it easier to capture readings and follow trends. But a reading on a patient’s phone did not, by itself, create coordinated care. The information still needed to reach the right practitioner, inform the care team, and involve an authorized caregiver when appropriate. The challenge was not simply collecting health data. It was connecting a potential risk to a clear, clinically governed follow-up workflow.
Healthcare was fragmented around the patient
- Disconnected monitoring: Health readings were spread across devices, applications, and paper records, making it difficult to build a coherent picture over time.
- Friction in care access: Finding and booking an appropriate practitioner by condition or specialty could be slow and confusing.
- Low-relevance guidance: Generic health tips did not consistently reflect a person’s condition, goals, or daily context.
- Limited practitioner visibility: Doctors lacked a consolidated view to help distinguish patients requiring timely review from those following a routine care plan.
The opportunity was not another CGM notification. It was a human-centered care experience connecting patient-generated data with practitioner workflows and authorized support networks.
End-to-end UX ownership across two connected applications
As Lead Interaction Designer, I led the experience-design work across the patient-facing and practitioner-facing apps. My responsibilities covered discovery, information architecture, task flows, interaction and visual design, prototyping, stakeholder alignment, and usability evaluation. I also drove the research rather than receiving it as a predefined brief.
- Conducted interviews, surveys, and focus groups to understand behaviors, attitudes, and unmet needs.
- Used Google Analytics data as a quantitative input alongside qualitative research.
- Focused research on adults managing Type 1 or Type 2 diabetes and parents caring for a child with Type 1 diabetes.
- Designed the cross-stakeholder high-risk communication concept, including patient, practitioner, hospital front desk, and authorized family support.
Lean UX, grounded in operational reality
I used a lean, iterative process to move from research and problem framing to concepts, wireframes, prototypes, usability evaluation, and design documentation. The intent was to shorten feedback cycles while preserving the rigor needed for a sensitive healthcare experience.
I brought together stakeholders from Interactive Health across IT, health services, software development, and marketing, alongside two project leads and two designers from our team. Their involvement helped surface technical dependencies, clinical workflow constraints, privacy considerations, and front-desk realities early enough to influence the experience direction.
Two purpose-built apps, designed as one care ecosystem
The product concept brought together a Patient App for monitoring, appointment access, and wellness engagement with a Practitioner App for patient oversight, risk visibility, and follow-up coordination.
- Patient experience: A consolidated place to review blood pressure, glucose, and wellness information from supported third-party devices, alongside appointments and reminders.
- Practitioner experience: A more prioritized view of patient information, potential risk notifications, medical history, prescriptions, and follow-up needs.
- Care coordination: A proposed high-risk notification pathway connecting the patient with relevant clinical and operational stakeholders, subject to configured permissions and clinical protocols.
- Wellness engagement: A Kinitics Wellness integration concept using rewards to encourage healthy behaviors, including medication-refill activity.
Describe automated alert routing as implemented only if supported by the shipped product and verified workflow. Otherwise, present it as the designed concept or intended capability.
Relevance earns attention; generic advice creates noise
A recurring theme in the research was the mismatch between broad wellness messaging and individual circumstances. Recommendations only help when they reflect a person’s health profile, goals, capabilities, and context. Advice designed for one condition or lifestyle is unlikely to feel useful to someone with different needs.
This shaped a core design principle: relevance over volume. The experience should prioritize a smaller number of understandable, context-aware prompts over a stream of generic tips. Treat this as a research-informed design direction; include comparative test results only where the original study documented them.
The short version
Risk lived in silos
A patient's glucose spike, a doctor's calendar, and a family member's awareness never connected — sick care instead of proactive care.
One connected loop
A Patient app and Practitioner app sharing real-time risk data, so a high-risk reading reaches the doctor, front desk, and family automatically.
Proactive, not reactive
Personalized monitoring, streamlined booking, and a gamified wellness loop replacing generic advice and disconnected tools.
Two purpose-built apps, one shared goal: give patients and practitioners the same real-time picture of risk, instead of discovering it after the fact.
What the two apps actually do
Monitor, book, stay informed
Blood pressure and glucose monitoring, appointment management, health alerts for status/appointments/refills, wellness programs, and health manager tips.
Prioritize, don't just schedule
All-appointments listing, high-risk individual notifications, prescription and case history, patient visit detail, and new prescription issuance.
Both apps share one goal: move the relationship from reactive sick care — see a doctor after something's wrong — to proactive, preventive health management where risk is visible before it becomes urgent.
Why a connected care experience mattered
Market and industry figures below need source citations, publication dates, and definitions before publication. Treat them as unverified claims until checked against the original sources.
Continuity of information
Bring relevant readings, appointments, and care context into a more coherent patient experience.
Practitioner visibility
Help practitioners review patient context and identify records or alerts requiring attention.
Coordinated follow-up
Connect digital notifications with clear ownership, permissions, and operational next steps.
Gamification lift
Leaderboards, badges, and points correlate with a 35% increase in engagement and a 30% increase in behavior change.
Monetization path
The Kinitics Wellness integration supports both paid and free subscription tiers alongside the core app.
What made this hard
Real-time, cross-device reliability
Data security, real-time monitoring, and consistent behavior across devices and platforms — none of which are optional in healthcare.
HIPAA, not as an afterthought
Sensitive patient data requires privacy safeguards built into the design from the first flow, not bolted on before launch.
EHRs and insurance data don't line up
Connecting to existing health records and insurance databases for accurate, current information was a genuine interoperability problem, not a UI problem.
Primary and secondary research
Narrow a broad hypothesis — that human-centered design could improve on existing CGM-synced apps — into a specific, buildable interaction model. The research had to answer two separate questions: what do patients actually need day to day, and what does a doctor need to see to act on a risk signal before it becomes an emergency.
Adults with Type 1 or Type 2 diabetes
Direct daily experience managing glucose, medication, and appointments.
Parents caring for a child with Type 1
Different stakes and workflow — caregiving on someone else's behalf, often across school and home.
In-person interviews + observation
Contextual, not lab-based — watching how people actually interacted with a CGM device or existing app in their own routine, not a scripted task.
Literature, forums, experts
Studies and books on diabetes technology, real user comments on forums and blogs, and conversations with medical professionals, authors, and researchers.
Google Analytics
Quantitative usage data cross-checked against qualitative interview findings to see whether stated behavior matched actual behavior.
Active condition management
Currently managing Type 1/Type 2 diabetes personally, or actively caring for a child who is — not a lapsed or newly diagnosed case.
Mixed device familiarity
Both existing CGM/app users and people managing manually on paper, to avoid over-indexing on tech-comfortable participants.
Industry insiders
Healthcare or health-tech employees, to keep feedback grounded in lived patient experience rather than professional opinion.
Research Plan

User Interview Guide

Six themes from affinity mapping
The core problem underneath every interview transcript was the same: users weren't struggling with any single task — they were struggling with fragmentation. Monitoring, understanding, finding a doctor, booking, and tracking progress each lived in a different app, device, or phone call. Affinity mapping the raw research surfaced six recurring themes, each pointing at a specific UX opportunity.
Healthcare Accessibility
Finding the right doctor by disease is confusing; booking takes too many steps; trust in doctor selection is low. → Intelligent doctor discovery.
Fragmented Health Monitoring
Smartwatch, BP machine, glucose meter, sleep app, hospital reports — all separate. Trends become impossible to see. → Unified health dashboard.
Personalization
"Drink more water" gets ignored. "Your BP rose 12% in two weeks — reduce sodium, walk 20 more minutes" gets acted on. → AI-driven personalized insight.
Preventive Healthcare
Users don't want care only after illness — they want early detection and risk prediction before symptoms escalate. → Predictive health alerts.
Decision Support
Users collect data but don't know what to do with it — the largest experience gap in the entire journey. → Explainable health intelligence.
Motivation
Engagement drops off after a few weeks without progress tracking, goals, streaks, or community support. → Goals, rewards, and community.
Check metrics reactively, search symptoms after the fact, compare readings manually, ask family members, and book a doctor only once symptoms worsen.
Monitor daily, understand trends as they form, receive proactive alerts, take preventive action, and consult a doctor earlier — before a crisis.
Monitor health in one place. Find the right doctor quickly. Book easily. Track medical history. Understand reports.
Feel reassured about my health. Reduce anxiety. Gain confidence in decisions. Feel in control.
Share progress with family. Demonstrate healthy habits. Participate in wellness challenges.
Affinity Mapping & Research Synthesis

Research Insights

Research-to-Decision Matrix

Jobs-to-Be-Done Framework

From themes to six buildable concepts
Smart Health Dashboard
One Health Score with drill-down analytics, replacing dozens of disconnected metric cards.
AI Health Coach
Daily recommendations, habit coaching, medication reminders, and lifestyle suggestions.
Intelligent Doctor Finder
Filter by disease, specialty, rating, insurance, distance, and consultation mode.
Preventive Risk Detection
Predicts diabetes, hypertension, obesity, and heart disease risk before symptoms become severe.
Personalized Health Journey
Adaptive home screen based on current conditions, active goals, medication schedule, and risk level.
Family Health Management
Manage parents, children, and spouse from a single dashboard — not four separate logins.
Seven principles, one product vision
Action over information
Every metric guides the user toward a meaningful next step — not just a display of data.
One health timeline
Readings, medications, reports, appointments, and activities in a single chronological view.
Personalized by default
Recommendations tailored to each user's profile, history, and goals — never generic advice.
Reduce cognitive load
Visual trends, plain language, and color-coded indicators simplify complex medical information.
Trust and transparency
Explain how recommendations are generated, surface credible sources, and protect user privacy.
Support preventive care
Prioritize early warnings and habit formation over reactive care after symptoms appear.
Motivate continuous engagement
Reinforce healthy behaviors through goals, progress tracking, reminders, and community encouragement.
Margaret Thompson, 65
Retired, active, managing chronic conditions
High blood pressure and osteoarthritis. Independent, health-conscious, motivated to stay that way — but not a confident technology user.
Monitor, manage, stay independent
Track blood pressure and vitals, follow prescribed treatment for chronic conditions, and preserve an active daily life.
Technology isn't the comfortable part
Needs intuitive interfaces, clear visualizations she can interpret without help, and reminders that keep her motivated without nagging.
Diligent, but manual
Records blood pressure readings in a paper diary today. Visits her provider regularly and leans on family for support and encouragement.
User Persona

What Margaret says, does, and feels
"I find it difficult to book appointments with doctors." "I feel overwhelmed managing my health parameters." "I struggle to remember to take my medications on time."
Downloads the app, searches doctors by specialty, reads reviews, books appointments, tracks parameters manually or via connected device, sets medication reminders.
Frustrated by booking complexity, anxious about her conditions, but hopeful and empowered when the app gives her a personalized, actionable path forward.
The booking flow and doctor profiles, reminders and notifications, visual health trend data, and ratings from other patients about providers.
Empathy Map

Three stories that drove the flows
Health monitoring
"As Margaret, I want to track blood pressure and heart rate easily and view them clearly, so I can share trends with my doctor during appointments."
Appointment scheduling
"As Margaret, I want to see available doctors by specialty, rating, and location, pick a slot, and get reminders — without phone calls."
Personalized exercise
"As Margaret, I want low-impact exercise recommendations suited to my age and conditions, with clear demonstration videos."
From registration to reminder
The core user flow ran registration → home screen → appointment booking → health parameter tracking → personalized recommendations → wellness programs → account settings. Four task flows carried the weight of daily use:
Booking a doctor's appointment
Search by specialty → review ratings and time slots → confirm → receive notification → appointment appears in the Appointments section.
Tracking health parameters
Select parameter → enter manually or via connected device → view trend visualization → set recurring tracking reminders.
Accessing recommendations
App analyzes health data → surfaces medication, lifestyle, and wellness-program suggestions tailored to the user's specific conditions.
Managing account settings
Update personal info → manage notification preferences → connect/disconnect third-party devices → review appointment and wellness history.
Six phases, from search to sustained engagement
Booking
Searching, downloading, registering — hopeful and relieved to find a convenient path.
Check-in
Searching by specialty, reviewing profiles, confirming a slot — feeling organized and prepared.
Pre-encounter
Reminders and prep instructions arrive — anticipation mixed with nervousness.
MD encounter
Check-in, wait, examination, conversation — a mix of relief, trust, and vulnerability.
Post-encounter
Consultation summary and prescription land in-app — clarity, relief, motivation to follow through.
Between visits
Continued tracking and personalized recommendations — a renewed sense of ownership over health.
Patient Journey Map

From sketch to prototype
Design solutions started as sketches — the fastest way to explore content placement and navigation options before committing to a direction. Sketching kept the focus on content hierarchy: making sure the information a stressed, possibly first-time user needed most was never buried. Each concept was tested against the pain points surfaced in research before moving to wireframes and, eventually, a working prototype used in stakeholder review and usability testing.
Intended business value and design outcomes
The outcomes below describe the value the design was intended to support. Add project-specific baseline and post-launch evidence before presenting them as measured results.
Improved user experience
A more intuitive, user-friendly interface driving higher satisfaction, engagement, and retention.
Streamlined processes
Appointment booking, parameter tracking, and medication management consolidated into one workflow, cutting administrative overhead.
Enhanced communication
Secure messaging, reminders, and shared treatment plans improved patient-provider continuity of care.
Data-driven insight
Aggregated health, appointment, and medication data informed strategic decisions and targeted health programs.
Competitive advantage
Personalized recommendations and convenient access differentiated the platform from generic competitors.
Revenue potential
Premium subscriptions and wellness-program partnerships opened new monetization paths beyond the core app.
How we'd know it's working
Connect research evidence to design decisions
The portfolio describes interviews, observation, analytics, affinity mapping, and six research themes. This traceability matrix makes the next step explicit: how an observed problem becomes a design response and how that response should be validated.
The examples below show how to document the rationale. Replace or confirm them with original research notes, actual decisions, and test results before presenting them as project evidence.
| Observed problem / hypothesis | User need | Design response to evaluate | Validation evidence |
|---|---|---|---|
| Health information is fragmented Portfolio research theme | Review relevant measurements and history in one place. | Unified health timeline with source and timestamp labels. | Task success finding a prior reading; comprehension of source and freshness. |
| Patients may not know what to do next Portfolio research theme | Understand information and appropriate next steps. | Plain-language explanation with clinically reviewed guidance. | Comprehension testing; clinical review; error and misunderstanding analysis. |
| Practitioners need to identify cases for review Product hypothesis | Prioritize relevant patients and understand why an alert appeared. | Prioritized queue with context, timestamp, status, and acknowledgement. | Scenario-based usability testing and workflow review with practitioners. |
| Health information is sensitive Product constraint | Control who sees data and understand sharing consequences. | Explicit consent and role-based sharing controls. | Permission comprehension testing and privacy/security review. |
Research evidence log
Store anonymized observations, supporting evidence, confidence level, and research source for each insight.
- Separate direct observations from interpretation.
- Record contradictory findings and unresolved questions.
- Link each insight to affected user groups.
Decision log
Record what the team decided, what alternatives were considered, and what evidence would change the decision.
- Document owner and decision date.
- Capture trade-offs and assumptions.
- Link to design versions and validation results.
Prioritize opportunities before committing to features
The case study presents six opportunity areas. A transparent prioritization method would show why the team selected a particular problem to solve first and which ideas required further evidence or clinical review.
User impact
How frequently and seriously does the problem affect a target user?
Safety and privacy risk
Could a failure, misunderstanding, or disclosure cause harm?
Evidence strength
Is the opportunity supported by research, or is it still an assumption?
Feasibility
What integrations, data quality, operational, and engineering dependencies exist?
Business alignment
Which user and business outcomes does solving the problem support?
Measurability
Can the team define a baseline and observe a meaningful change?
| Opportunity from this case study | Key dependency to resolve | Suggested decision gate |
|---|---|---|
| Unified health dashboard | Data-source reliability, timestamps, units, missing-data states. | Validate comprehension and data provenance before release. |
| High-risk alert workflow | Clinical ownership, approved thresholds, recipient permissions, escalation policy. | Require clinical and safety review before implementation. |
| Doctor discovery and booking | Provider directory accuracy, appointment availability, cancellation rules. | Test end-to-end booking and recovery from unavailable slots. |
| Personalized recommendations | Data sufficiency, clinical review, explainability, limitations. | Start with clearly bounded, reviewed scenarios; do not imply diagnosis. |
| Gamified wellness | Accessibility, user motivation differences, unintended pressure. | Validate with users and monitor opt-out and engagement patterns. |
| Family health management | Consent, proxy access, age-related permissions, revocation. | Validate authorization and sharing comprehension. |
This is a proposed decision framework, not a ranking of the original project's features. Final prioritization requires project constraints and stakeholder evidence.
Map the complete patient-to-practitioner service
A connected experience depends on more than two interfaces. The service blueprint below identifies the handoffs that need explicit ownership, operational procedures, and recovery behavior.
| Service stage | Patient / caregiver | Product and operational response | Practitioner / care team | Failure to design for |
|---|---|---|---|---|
| 1. Capture | Records a reading or connects a device. | Validate format, source, unit, timestamp, and sync status. | Not yet involved unless a defined rule applies. | Missing, stale, duplicated, or invalid data. |
| 2. Interpret | Views the reading and context. | Show clear labels and clinically reviewed explanations within product scope. | Receives relevant context only through approved workflows. | Misinterpretation or false reassurance. |
| 3. Route | Sees an appropriate status message. | Apply approved routing, permission, delivery, and audit rules. | Authorized recipient receives the notification and supporting context. | Delivery failure, unauthorized recipient, duplicate alert. |
| 4. Acknowledge | Receives status appropriate to the workflow. | Track delivery and acknowledgement separately; apply defined escalation policy. | Reviews, acknowledges, or routes the case according to protocol. | Unowned alert or unclear responsibility. |
| 5. Follow up | Books or attends follow-up when directed. | Support appointment status, reminders, and clear next steps. | Documents follow-up and relevant care-plan updates. | Missed appointment or incomplete handoff. |
Do not promise that a doctor, front desk, or family member sees an alert “at the same time” unless the delivery architecture, permissions, monitoring, and operational process support that claim. Define delivery expectations and what users see when delivery fails.
Build clinical safety and privacy into the experience
The product concept includes health monitoring, risk notifications, personalized guidance, and family sharing. These capabilities require documented risk controls. This table is an initial design checklist and must be reviewed by qualified clinical, privacy, security, and regulatory stakeholders.
| Hazard / failure mode | Potential impact | UX and system controls to define | Validation owner |
|---|---|---|---|
| Stale or unavailable reading | A user assumes information is current when it is not. | Show source and last-updated time; distinguish unavailable data from normal readings; define stale-data handling. | Product, Engineering, Clinical |
| Alert is delayed or not acknowledged | A user assumes someone is responding when no response has occurred. | Separate sent, delivered, viewed, and acknowledged states; define ownership and escalation outside the UI alone. | Clinical Operations, Engineering |
| Risk indicator is misunderstood | Unnecessary alarm or false reassurance. | Use clinically approved thresholds, clear language, appropriate urgency, and context; test comprehension. | Clinical, UX Research |
| Recommendation exceeds product scope | User treats general guidance as diagnosis or treatment advice. | Define permitted scenarios, data limitations, explanation, and when to contact a professional. | Clinical, Product, Compliance |
| Health data shared with the wrong person | Privacy breach or loss of trust. | Explicit consent, role-based permissions, access review, revocation, and audit trail. | Privacy, Security, Product |
| Integration or synchronization fails | Incomplete records or a misleading view of health status. | Visible sync status, retry behavior, error recovery, and clear data-source labels. | Engineering, UX, QA |
This checklist is not a clinical risk assessment or a certification of regulatory compliance. Validate applicable legal and regulatory requirements for the target market and product classification.
Validate the highest-risk tasks before release
The portfolio mentions prototyping and usability testing but does not show participant counts, task results, issue severity, or retest evidence. Use the plan below to capture those details without inventing results.
Critical tasks
- Find the source and date of a health reading.
- Explain a displayed measurement in their own words.
- Identify the next step described by an approved scenario.
- Book, reschedule, or cancel an appointment.
- Grant and revoke caregiver access.
Critical tasks
- Identify why a patient appears in the prioritized queue.
- Check reading freshness and supporting context.
- Acknowledge or route a notification.
- Recognize an unacknowledged or failed-delivery state.
- Locate relevant patient history before follow-up.
| Record for each test round | What to document |
|---|---|
| Study setup | Research question, prototype/version, participant criteria, actual sample size, accessibility needs, and test environment. |
| Task results | Completion, time on task, errors, assistance required, confidence, and comprehension. Record the denominator and method. |
| Issue log | Observed behavior, supporting evidence, severity, affected user group, and potential safety consequence. |
| Design iteration | Issue addressed, change made, rationale, owner, and design version. |
| Retest | Whether the issue improved, persisted, or introduced a new problem. Report findings without overstating causality. |
Release gate: Critical comprehension, privacy, and alert-handling issues require documented resolution or explicit risk acceptance by the appropriate accountable stakeholders.
Measure user outcomes, operational reliability, and trust
Replace broad claims such as “higher satisfaction” or “improved retention” with metric definitions, baselines, targets, and measured results. The examples below are proposed measures, not outcomes already achieved by this project.
| Outcome area | Proposed metric | Definition to finalize | Guardrail |
|---|---|---|---|
| Usability | Critical-task completion rate | Successful unaided completions divided by valid task attempts. | Report by task and user group; do not hide critical errors in an aggregate. |
| Comprehension | Correct interpretation rate | Participants who correctly explain the meaning and limits of a displayed reading divided by those tested. | Use clinically reviewed scoring criteria. |
| Data reliability | Successful synchronization rate | Successful sync events divided by eligible sync attempts, with exclusions documented. | Track stale data and silent failures separately. |
| Alert workflow | Time to acknowledgement | Elapsed time from defined alert generation to recorded acknowledgement. | Define severity and operating hours; distinguish delivery from acknowledgement. |
| Care continuity | Follow-up completion rate | Completed follow-ups divided by follow-ups due in the measurement period. | Account for cancellations and clinically appropriate changes. |
| Privacy and trust | Sharing-permission comprehension | Users who correctly identify who has access and how to revoke access. | Pair survey data with permission-related support issues and incidents. |
| Accessibility | Critical-task success by user group | Task success segmented by relevant accessibility needs and assistive technology. | Do not rely on an overall average to conceal unequal outcomes. |
Event taxonomy
Define event name, trigger, properties, source, consent basis, retention, and owner before implementation.
- measurement_viewed
- sync_status_changed
- alert_generated / alert_delivered
- alert_acknowledged
- appointment_booked / followup_completed
- sharing_permission_changed
Outcome review cadence
Review usability, reliability, support signals, privacy concerns, and clinical workflow metrics with accountable teams.
- Set baselines before claiming improvement.
- Define targets with product and clinical owners.
- Investigate metric movement before attributing cause.
Collect only necessary data, follow applicable privacy requirements, and confirm the lawful basis and retention rules for analytics involving health information.
Separate demonstrated work from proposed improvements
To strengthen this case study for senior UX leadership roles, distinguish what was completed during the original project from what you recommend adding now. This protects the credibility of the work and makes your strategic judgment visible.
Original deliverables
- Research methods and actual participant counts.
- Real affinity-map outputs and source-backed insights.
- Design iterations linked to observed findings.
- Usability study results and actual changes made.
- Measured product outcomes, with dates and baselines.
Proposed artifacts
- Clinical hazard analysis, unless completed and reviewed.
- Proposed service blueprint and escalation model.
- Suggested KPI definitions and event taxonomy.
- Future-state roadmap and release gates.
- Any illustrative examples added to this case study.
Review the market statistics in the “Market Opportunity” section and the outcome statements in “Results & Takeaways.” Add reliable citations and project-specific evidence, or label them as estimates, hypotheses, or intended benefits. Do not present general industry statistics as results produced by this project.