MedAssist
- Year
- 2026
- Role
- UX Researcher, Designer and Builder
- Deliverable
- A working web simulation
- Duration
- 12 days, 9 to 20 October 2026
- Course
- Product & Interaction Design
0
Responses analysed
16-item empathy questionnaire. 277 collected, 17 dropped for missing items.
0
Kinds of empathy
Affective urgency and inhibition, split by factor analysis.
0
Symptoms in the sheet
Each given a tier. Approved by the designer; clinician review pending.
0
Acceptance scenarios
Every one has to pass before deploy, tested against the real engine.
01 Brief
What it is
02 Problem
What was wrong
01.
One tone for everyone.
02.
Worry changes how people write.
03.
Safety cannot depend on tone.
04.
The asker is often not the patient.
03 Research
What I did
Survey
The 16-item Toronto Empathy Questionnaire plus age and gender, as an online form.
Sample
277 collected, 260 analysed. 57% male, 41% female, 2% other. Mean age 24.6.
Analysis
14 methods: reliability, factor analysis, item response theory, invariance, network psychometrics, latent profiles and clustering.
Regulation
Telemedicine Practice Guidelines 2020, CDSCO software guidance, the DPDP Act 2023, and Anthropic's policy for health content.
Pattern study
A clean-room study of how Ada Health runs a symptom check, from public sources only.
04 Findings
What I found
01.
Empathy has two sides.
02.
Women scored 4.07 points higher.
03.
Two profiles, and a small low-reactive group.
04.
The scale does not work the same for everyone.
05 Define
Three dials
Mode: how warm
Empathetic, Balanced, Factual or Minimal. It starts from the questionnaire, moves one step warmer on distress signals at most every two messages, and never colder than it started.
Register: how formal
Casual or Professional, chosen at onboarding and independent of warmth. The simplest language goes to the over-60 age band.
Severity: how worried
Mild, Moderate or Severe, looked up from a reviewed sheet of 134 symptoms. During a conversation it can only go up.
Minimal stays dormant
It is reachable only by manual override, because the low-reactive group is small and a wrong guess would silence someone who needed warmth.
06 Pipeline
Six steps
1. Emergency floor
What happensA fixed phrase list across 13 categories, with misspellings and negation handling. If it trips, the Crisis screen opens and the model is never called.
2. Read the person
What happensFive passive signals update the distress score and the Mode.
3. Read the symptom
What happensSymptoms are extracted into structured data, then looked up for Severity. Extraction never decides the floor.
4. Reply
What happensThe model gets Mode, Register, Severity, age band, who it is about, the memory so far and the rulebook.
5. Output guard
What happensEvery reply is checked for doses, verdicts, brand names and child-medicine rules. A failing reply is replaced by a safe template.
6. Render
What happensShort bullets, bold key phrases, a see-a-doctor line on moderate and severe, and a persistent disclaimer.
07 Design
What I decided
Emergencies never wait.
The browser runs the floor before sending, so the Crisis screen opens instantly, even offline. The server runs it again before any length cap or rate limit.
Short answer first, then questions.
A reply gives a safe answer before it asks. Warning-sign questions use Yes, No and Not sure, and Not sure counts as the warning answer.
Show what it knows.
A small, editable panel holds the facts from the chat, so the model never asks again for something already there.
One primary action per screen.
SOS, 108 and 112 are one tap away everywhere, and the Crisis screen replaces the conversation instead of sitting on top of it.
Colour never carries meaning alone.
Crimson is reserved for emergencies and errors, every state has an icon or text, and high contrast and text size are in settings.
A kind exit instead of a block.
Under 18 leads to a calm screen that keeps 108, 112 and Tele-MANAS 14416 visible.
08 Testing
How I checked
Engine unit tests
What it coversFloor, rulebook, output guard, severity, memory, signals, rate limits
Status25 test files
Acceptance scenarios
What it covers24 scenarios from a first-time user to question limits
StatusWritten first, run on every change
Browser walkthrough
What it coversOnboarding, chat and Crisis on a real page
StatusRun on Days 4 and 5
Clinician review
What it coversSafety rules, emergency triggers, 134 tiers, sample replies
StatusPack written, reviewer not yet named
09 Bugs
What the tests caught
The floor missed "unconscious"
Only misspellings matched. Fixed, and a test now covers correct spellings for every category.
A carer cannot type what the sheet expected
A person in a coma cannot type. The floor was extended to carer phrasings and the sheet gained a column for who can report each symptom.
Doctor-only terms in the sheet
They were rewritten as what people can see, such as black, tar-like stools, or excluded.
A note on the numbers
- The research is a survey of 260 people, mostly aged 21 to 25 and mostly students. It describes how they answer a questionnaire, not how they behave when ill.
- The three starting tones come from a scoring key on a cleaned set of 271 responses. They are a labelling heuristic, not the published profile analysis.
- Live replies come from a language model. The rules around it are deterministic but the wording is not, so tests check rules and tiers, not exact sentences.
10 Limits
What is still open
- No doctor or pharmacist has reviewed the content yet, so the app must not be called clinically validated.
- No safety red-team round has run yet, including carers describing someone else.
- No usability test with real users has run.
- Hindi, Gujarati and Hinglish are not supported. Those messages show an English-only notice with 108 and 112.
- The severity sheet comes from a dataset licensed CC BY-NC-SA 4.0, so it is non-commercial. Tiers were approved by the designer, not a clinician.
11 Next
What comes next
Clinical review
Send the review pack to a doctor or pharmacist and apply their changes to tiers and questions.
A safety red-team
Including a round of carers describing someone else.
Real users
Deploy, record a walkthrough and test with real people.
More languages
Hindi, Gujarati and Hinglish, which the app does not support today.
Get in Touch