Get your medical records ready before the doctor visit.
For patients and families managing prescriptions, lab reports, scans, and discharge papers across WhatsApp, paper files, and hospital portals. Put everything in order without uploading a document.
No account. No upload. Helping a parent? Make a separate file with their permission. Details stay in this browser tab and are not saved or sent to MedicalRecords.in. See what is—and isn’t—active
Available now · works in this browser
One person · one source list
Records index
Find the original when the doctor needs it
Before you leave home
Records indexed
Missing copy noted
Questions written down
The index is prepared in this tab. MedicalRecords.in does not receive what you type.
Start without an account. Put the next visit in order today.
All three tools work without an account. What you enter stays in this browser tab and is not saved, uploaded, or sent to MedicalRecords.in.
For clinics: make record readiness a pre-visit workflow.
MedicalRecords.in is exploring a patient-controlled pathway for Indian specialty clinics and hospitals: help people prepare the right originals before consultation time, while keeping clinical details out of WhatsApp.
The current friction
Records arrive across paper, phone downloads, lab portals, and hospital systems. Staff and patients spend consultation time finding the right original.
The workflow to evaluate
A patient prepares a source-linked visit pack before the appointment. The clinic opens the original when context matters.
The buyer decision
Measure readiness, missing-record events, staff effort, clinical use, implementation burden, and willingness to pay.
Built around how medical records actually move in Indian homes.
Prescriptions may be on paper, reports may arrive on WhatsApp, and scans may sit in a hospital or lab portal. The useful first step is not another account: it is a clear index that tells one person or family caregiver where each original is kept.
01 · Familiar entry
One secure clinic link
A future invite would carry only appointment context and a link—no diagnosis, report image, or clinical conversation.
02 · Governed work
Patient prepares in the browser
The available tools work locally today. A future account flow must handle identity, consent, authority, and records separately.
03 · Care handoff
A source-linked visit pack is ready
The reference workflow preserves originals and review state. The account-backed handoff is not open in this public-tools deployment.
WhatsApp invitation and intake are not active in this deployment.
Use the private local path available nowPaper file
Prescriptions and discharge papers
WhatsApp download
Reports already saved to your phone from a message thread
Hospital or lab
Portal records and missing-document requests
ABHA-linked
Consented records from connected facilities
Useful without ABHA
Start with the records you already have. Identity linking should add convenience, not block the first useful step.
One file per person
Keep your records separate from a parent’s or child’s, even when someone trusted helps prepare them.
Help with permission
A family member can prepare a separate local index with the record owner’s permission—without silently taking ownership.
Assisted and multilingual
Plain language, complete task journeys, accessible controls, and caregiver-friendly recovery are release requirements.
Current boundary: ABHA linking, WhatsApp invitation or intake, family profiles, and uploads are not active in this public-tools deployment. The local organizer, request pack, and visit checklist are available now.
AI can find the evidence. It never gets the final word.
OpenMed reads clinical text and finds structured evidence and sensitive spans. MedicalRecords.in keeps that output private, linked to its source, and blocked from patient release until a verified doctor reviews it.
Architecture preview. OpenMed processing and account uploads are not active in this public-tools deployment. The local organizer, request pack, and visit checklist remain available now.
Processing contract
Private network · source spans retained
How it works: one chain of evidence, four clear handoffs.
The account workflow below is part of the reference implementation but is not open in this public-tools deployment.
Keep the source
Every timeline item points back to the original report, prescription, or discharge summary.
Create a private draft
OpenMed locates clinical entities and sensitive spans. Its output remains a machine draft.
Require doctor review
A verified doctor checks the source, records a decision, and owns the released interpretation.
Prepare for care
The patient receives a traceable timeline and a visit brief—not an unexplained AI answer.
Built for the moment before the appointment.
The goal is not another dashboard. It is a source-linked record you can understand, carry into care, and discuss with a qualified clinician.
New request intake stays blocked until an operator process exists.
Build a visit checklistOriginals stay traceable
Every summary and review decision points back to the retained source record.
Clinical drafts stay private
Machine-created clinical content remains hidden while review is pending.
Timeline before interpretation
Dates, document types, and source labels remain useful without making a diagnosis.
Doctors own release
Verified identity, registration details, decision notes, and blockers are recorded.
Trust should be inspectable.
Release boundary
Automated tests cover role gates, doctor identity, and release blockers.
Open implementation
Application code, migrations, tests, and deployment manifests are inspectable.
Standards roadmap
ABDM FHIR conformance evidence stays separate from certification claims.
Records ready. Care can begin.
Use the local-only organizer without creating an account or sending entered details.
Account access is not open in this public-tools deployment.