Doctors get more time with patients on the same number of beds, and the hospital can say health data never left its systems.
Hospitals · 08 / 12
Private LLM for health data
Doctors get a patient summary before the visit and can search internal treatment guidelines at once, on hospital systems, with health data going nowhere.
Hospitals “Doctors want AI to summarise a patient’s history before the visit, but health data cannot leave the hospital by law.”
The problem
A doctor has a few minutes per patient, and one patient’s history is spread across several HIS screens: the last visit’s notes, lab results, current medication, allergies, and a referral letter from another hospital scanned as an image. The doctor scrolls through all of it before calling the patient in, then types the discharge summary and the insurance paperwork after clinic.
A public tool would summarise it, and health data cannot leave the hospital by law, so the legal team will never approve it. The doctor keeps reading.
How we solve it
We install a language model on the hospital’s own servers or in a cloud account the hospital controls, connected to the HIS and the medical records system through an API or a read-only database link. Before calling the patient in, the doctor opens a one-page summary: the history relevant to today’s complaint, current medication, allergies, and the lab results that changed since last time, each linked back to its HIS entry.
Permissions follow the role. Doctors see only patients in their care, and every view is logged for medical records and the DPO to check. We design the storage and permissions with the hospital’s legal team to meet PDPA and health-data rules. There are no external API calls.
The system summarises and drafts. Diagnosis, prescribing and the signature on every document remain the doctor’s. The system writes nothing into the medical record until the doctor has checked and confirmed it.
How it runs
- Medical records in the HIS
- Lab results and images from LIS and PACS
- Referral letters scanned as images
- Internal treatment guidelines
- Check the patient is in the doctor’s care
- Read and summarise the relevant history
- Draft the summary and referral letter
- Log every view
- One-page summary to the doctor before the visit
- Drafts for the doctor to sign
- Answers from the internal guidelines
- Access log for the DPO
Before and after
What you get
- 01
A model inside hospital systems that summarises records and searches internal treatment guidelines
- 02
Role-based permissions: doctors see only patients in their care, nurses and medical records staff see what their role needs
- 03
Designed with the hospital’s legal team to meet PDPA and health-data rules
- 04
Drafts of discharge summaries, referral letters and insurance claim documents from data in the HIS, for the doctor to check and sign
- 05
Search across allergies, past lab results and current medication in plain questions, citing the date and the HIS entry
Who gets what
Installed inside hospital systems, connected to the HIS read-only at first, role-based permissions through Active Directory, every access logged, designed with the legal team.
Doctors stop hunting for last visit’s lab results across screens and stop typing discharge summaries in the evening.
Who this fits
Connects with what you already run
Development process
- 1
Discover
Requirements, users and success metrics, with scope and price fixed before we start.
- 2
Design
UX and system architecture; the prototype is approved before anything is built.
- 3
Build
AI-accelerated sprints with a demo every week, reviewed by senior engineers.
- 4
Test
QA, security and performance verified against the agreed scope.
- 5
Launch & care
Production deploy, team training, and a monthly care plan.
Turn your business problem into a system that works for you
Tell us today — get an executive-ready proposal with the plan and budget.
Talk to an engineer about this