Diplodoctor

Technical context

The stack has not been written down yet.

Sign in to ask about architecture, evidence, delivery risks and next steps in your workspace.

Roadmap

1. Read a lab report and say what it means

   in progress · 10/12 steps done

   • Intake by pasted text or a photo of the report, several pages in order — done
   • Every value extracted: name, value, unit, printed range, flag, and the line it was read from — done
   • The flag decided by comparing the numbers, not by the model; urgency never lower than the flags imply — done
   • Plain-language information on each value outside its range, as information and never a diagnosis — done
   • Questions to ask your doctor, written from the values outside their range — done
   • Reports kept in the browser, with export and import — done
   • A value followed across reports in this browser, with units never converted — done
   • The interface and the reading in German, French, Italian, English and Spanish — done
   • Analysis through the fleet's shared model chain, with a rate limit; or your own model — done
   • Shared model keys set on the host, and the first real report read there — done
   • A set of real reports with known values, to measure how often extraction is right — not done
   • Reports that arrive as a PDF — not done
   Where this comes from

2. Private by construction

   in progress · 4/8 steps done

   • Names, birth dates, addresses, insurance, patient and order numbers replaced in the browser before a report is sent — done
   • Details covered on page photos before they are sent — done
   • An anonymised file to hand to a person you choose — done
   • Zero-knowledge proofs wherever an identity would otherwise be exposed, starting with a licence — not done
   • A strict content security policy and security headers — done
   • Read the text of a photographed page in the browser, so photos are anonymised automatically too — not done
   • Model providers that contractually do not train on or retain what they are sent — not done
   • An independent security review before the first real users — not done
   Where this comes from

3. A legal opinion on the medical-device line

   in progress · 0/1 steps done

   • A written opinion on whether the explanation step is a medical device, before it is promoted — not done
   Where this comes from

4. A look of its own

   in progress · 2/2 steps done

   • A light, calm theme, dark on request, the whole look in one file — done
   • A test that keeps any theme readable (WCAG AA) — done
   Where this comes from

5. Say what Diplodoctor is, in one place

   in progress · 1/4 steps done

   • Roadmap and changelog kept in this repository and rendered from the fleet map — done
   • Problem, solution, mission and vision filled in on the Loki profile — not done
   • An OrangeCat profile, so the project can be found and funded — not done
   • A Solon organisation, so its rules can be decided in the open — not done
   Where this comes from

6. One health file

   planned · 4/6 steps done

   • Today, Records, and medicines, appointments and notes beside reports — done
   • Search that forgives a typo, and filters that live in the address — done
   • The file kept for you across devices, sealed on our host, for signed-in people, if they choose — done
   • Ask about your file, in a chat — done
   • Keys only the owner holds, so the operator cannot open the file — not done
   • Reminders: a retest, a refill, a follow-up — not done
   Where this comes from

7. Health matters worked by an agent

   planned · 1/9 steps done

   • Accounts of our own, optional, pseudonymous by default: email and password, link, passkey, two-factor, OrangeCat and the shared sign-in — done
   • One account across the fleet without a second sign-up — not done
   • Matters stored on our host in Switzerland, each sealed with its own key — not done
   • A timeline of results, visits and documents; medications with dose and frequency; family history — not done
   • Reminders: a retest, a refill, a follow-up — not done
   • Drafts proposed for the owner to approve: an appointment request, a letter to the Krankenkasse — not done
   • A dispute with an insurer handed to Causius — not done
   • Caring for someone else, with their consent recorded and revocable — not done
   • Bring a quick-check report into a matter in one step — not done
   Where this comes from

8. People in the loop

   planned · 1/6 steps done

   • The rules: what an AI model may say, what an assistant's view is, what only a licensed professional may give, and who may be pseudonymous — done
   • "Have a person look at it": a redacted file handed to an assistant or a licensed professional you choose — not done
   • Assistants and licensed professionals offer their work as OrangeCat services and are paid there, in any currency — not done
   • How helpful people found an assistant, shown on their profile, from the people they helped — not done
   • A licence proven with a zero-knowledge proof against the public register, so a licensed professional can stay pseudonymous — not done
   • Admission, labelling and evaluation rules adopted by a recorded vote on Solon — not done
   Where this comes from

9. For clinics and practices

   planned · 0/4 steps done

   • A patient hands a clinic their file by choice, anonymised until they decide otherwise — not done
   • A clinic's patients arrive with their results read and their questions written — not done
   • A clinic runs Diplodoctor on a model inside its own walls, so patient data never leaves the practice — not done
   • A clinic's own branding and languages on its own address — not done
   Where this comes from

Changelog

1. October 26, 2026

   Readable roadmap and changelog labels. Development pages now use their own translation namespace in all five languages, separate from medical records.

2. October 26, 2026

   Shared account recovery and sign-in. AccountKit supplies account screens and runtime, including recovery and consistent second-factor enforcement. Existing accounts, health-file ownership and product roles retain their tables.

3. October 15, 2026

   Keep your file in your account, if you choose. One switch in Account. The file is kept sealed on our server and follows you to any device you sign in on. Off by default; turning it off deletes the copy. Ask about your own file. Questions answered from your records only, with names hidden before anything is sent. Information, not a diagnosis. A health file, not a report reader. The header is now Today, Records and People. Today shows what is next, the latest results and your medicines; Records is everything in one list you can search (a typo still finds it) and filter, and you can add medicines, appointments and notes beside reports. The home page says so in fewer words. Accounts, if you want one. Sign in with email and password, a link, a passkey, two-factor, OrangeCat or the shared sign-in, in all five languages. Reading a report still needs none, and nothing health-related is stored on the server. Much less to read. The home page went from about a thousand words to a couple of hundred: what it is, one value read, how it works, why it is private, and who can help. The depth moved to Platform and Security; the intake form, the report page and People were cut by a quarter to a third. A test now holds each page to a word budget. Warm paper and pine green, not clinical blue. Blue is every hospital's colour. The look is one file (app/theme.css), so it stays a one-line change. Every control in the header and footer is at least 44px, at phone, tablet and desktop width, in all five languages.

4. October 14, 2026

   Read a lab report. Paste it or photograph its pages, in any language. Every value comes out with its unit, its printed range and the line of the report it was read from. The numbers decide, not the model. Whether a value is outside its range is worked out by comparing it with the printed bounds, and the urgency shown can never be lower than the values imply. What it means, as information. A plain explanation for each value outside its range, questions to take to your doctor, and the words of a non-lab document explained. Never a diagnosis. Follow a value over time. When the same measurement is in an earlier report in this browser, the earlier value and the direction are shown. Units are never converted. Private by construction. Names, birth dates, addresses, insurance, patient and order numbers are replaced in your browser before anything is sent; reports live in this browser only; an anonymised file can be exported for a clinician. Five languages. The whole site and every reading in English, German, French, Italian and Spanish. Your own model. Connect an API key and the reading runs on your own budget; the key stays in your browser. Roadmap, changelog and the rules for clinicians, said plainly, with nobody listed who does not exist.

5. October 14, 2026

   Three kinds of help, said honestly. Any AI model (there is no "Diplodoctor model"; it is whichever model answers), a health assistant anyone can be, under a name or a pseudonym, whose view is an opinion and whose helpfulness will be shown, and a licensed professional, whose licence can be proven without revealing who they are. /clinicians is now /people. Nobody is listed yet and the pages say so; the zero-knowledge licence proof is planned. A look of its own. Light and calm by default, dark on request or when your device asks, with a toggle in the header. The whole look is one file, app/theme.css, and a test keeps any change readable.