The problem, specifically
Clinical documents carry the most sensitive data your organisation holds, and the usual answer, posting it to a rendering service, is the one thing your compliance team will not sign off.
It runs on your side of the boundary
Self-hosted means patient data is rendered on infrastructure inside your own governance, with no outbound connection required at all.
Clinically legible by default
Out-of-range values flagged by weight and marker rather than colour alone, so they survive a greyscale ward printer.
Structured, repeatable records
One template per document type means every discharge summary looks the same regardless of who generated it.
Templates for this, ready to render
Every one is real, self-contained HTML and CSS. The previews below are actual renders from each template's own sample data.
Lab Test ReportPathology report with result/unit/reference-range panels, out-of-range values flagged in bold, and a verified-by block.
Medical CertificateFitness and sick-leave certificate stating the period of rest, the practitioner's declaration, restrictions, seal and serial barcode.
Medical PrescriptionClinic prescription with patient and doctor blocks, Rx symbol, dose/frequency/duration table, advice and registration number.
Patient Discharge SummaryHospital discharge summary with admission dates, diagnosis, procedures, discharge medication, red flags and follow-up plan.
Cloud, or entirely your own infrastructure
Start on the hosted API in minutes, or run the identical engine inside your own network where the data never leaves. Self-hosted is licensed per server, so tell us about your setup.