Diplodoctor

About

Diplodoctor is a health platform built on one premise: the person the data is about should hold it, and should be told the truth about what can and cannot be done with it. Three things follow from that. Your record is yours. You store and manage your own medical history rather than leaving fragments behind in each clinic that ever saw you. Care crosses borders; records should travel with the patient, not sit in whichever system happened to create them. Diplodoc reads it with you. An AI companion that reviews your history and helps you reason about it — not a diagnosis, and it will say so. Where the law forbids a machine from making a clinical judgement, the platform is explicit about that rather than pretending the limit is a technical one. Blocks are named, not hidden. When something is unavailable because of a regulation, the platform names the law, explains who it protects, and says what would have to change. Most software renders a legal boundary as a vague error, which teaches you that the system is broken when in fact it is obeying a rule someone wrote for a reason. A refusal that explains itself is a feature; a refusal that mumbles is a defect. Pseudonymity is a design stance, not a setting. A patient should be able to hold a health record without their legal name being the key to it. That is a constraint on the architecture — identity comes from what the user chose to publish, never from whatever an identity provider handed over at signup. Telemedicine and medical tourism are the same problem seen twice: care and records that have to move between jurisdictions with different rules. Deployment is one practice per instance — a second clinic gets its own database rather than a tenant column, because separate databases cannot leak between practices and a shared one is only ever as safe as its next query.

Current status

Nothing built yet — this profile is step one. Next: spin the repo out through FleetCrown and put a first working screen live at diplodoctor.orangecat.ch.

Categories