Healthpedia

One health record for the whole family

People read it. AI agents write to it. Nothing goes in until someone in the family says yes.

See how it worksTry the queue
A family walks together: a grandmother with a stick, her son with a folder, a grandson holding a phone and a small child.

Everything, in one place you can read

A timeline for each person, newest first. Medicines with who prescribed them. Labs with the latest value on top and the history underneath. Reports with a plain-language summary beside the original. Red flags one glance away.

Nani's recordSample data

Nani

Three doctors, one record

Record v1.4

  1. Prescription photo added

    v1.4

    Today. Proposed by Claude, approved by Ahmed

  2. Clinic visit, knee pain review

    v1.3

    2 days ago. Voice note from Ahmed

  3. Blood test report uploaded

    v1.2

    Last week. Plain-language summary added

  4. Second opinion recorded

    v1.1

    Last month. Two plans kept side by side

Speak it, snap it, approve it

After a clinic visit, a young man photographs a handwritten prescription with his phone.
  1. 1

    Capture

    After the visit, send a photo of the prescription or a voice note to Claude or ChatGPT.

  2. 2

    Propose

    The agent reads the record and files proposed changes, each with a confidence level and its source.

  3. 3

    Approve

    Someone in the family checks each one against the source and says yes or no.

Claude, connected to HealthpediaSample data
0:24

Nani's visit today. Add this please.

propose_update, 4 fields

I read the prescription and the voice note and filed four proposed changes to Nani's record. One word on the slip was hard to read, so I marked it low confidence. They are waiting in your queue, and nothing changes until you approve them.

Nothing goes in without a yes

Handwriting is hard to read and voice notes get misheard. So every proposal waits in a queue with its evidence beside it. Try it: approve what looks right, reject what does not, then publish.

A woman at a kitchen table with tea ticks a card, a small stack of pending cards beside her.
Confirmation queueSample data

4 proposed changes for Nani

Filed by Claude from a prescription photo and a voice note

1/4 reviewed
  • New medicineHigh confidence

    Vitamin D 1000 IU, once a day

    From the photo

  • Dose changeMedium confidence

    Calcium 500 mg, now with lunch

    From the photo

  • Doctor's noteHigh confidence

    Review again in four weeks

    From the voice note

    “He said come back in about four weeks and we'll see.”

  • Stop medicineLow confidence

    Unclear word, maybe a painkiller

    From the photo

Nothing is in the record until you say yes.

Two doctors, two plans, one page

When doctors disagree, Healthpedia keeps both opinions side by side with the question to take back. Nothing is silently merged, so the next doctor sees the whole picture in a minute.

A doctor reads one clear record while an elderly woman and her grandson sit across the desk.
Opinions, knee painSample data

Dr. A, orthopaedics

Start the new medicine now

Clinic visit, Monday. Same X-ray.

Dr. B, family doctor

Wait two weeks and rest first

Follow up, Wednesday. Same X-ray.

Question to take back to both

Which plan, and in what order? Both are on her record, neither is merged.

Built for your AI assistant

Healthpedia runs an MCP server, so Claude Code, claude.ai and other assistants can read the record and file proposals. Six tools, and only one of them can suggest a fact.

get_member_record

Read one person's record

search_history

Search across visits, labs and notes

get_pending_proposals

See what is waiting for a yes

export_record

Hand a doctor the whole picture

add_document

File a photo or report as evidence

propose_update

Suggest a change. The only way facts get in.

claude mcp add healthpedia https://<your-deployment>/api/mcp \
  --transport http \
  --header "Authorization: Bearer <MCP_API_KEY>"

Bearer key for Claude Code, and a full OAuth flow so it also works as a claude.ai custom connector.

The queue is a safety system

Evidence first

Every proposed field sits next to its source: the crop of the photo or the exact sentence from the voice note.

Pick what is right

Approve the fields that are right and leave the rest. Low confidence is marked, never hidden.

Originals stay put

Photos and reports are kept as they arrived. Every fact links back to the document it came from.

Every change is signed

Each approval bumps the record's version with which agent, which source and who said yes.

Hands still work

Every entry can be edited by hand. Agents are a faster hand, never the gatekeeper.

A family-kept record that helps doctors see the whole picture. Not medical advice; decisions rest with the treating doctors.

It started as a PDF

My grandmother lives in Lahore and sees three doctors. Their plans did not always agree, and the only place the whole picture lived was a PDF our family kept by hand, updated from prescription photos and voice notes. Every habit in that PDF became a feature here.

Muhammad Bin Sohail, who built it

Open HealthpediaMore of my work