Clinical Content, Owned by Clinical Teams
ClinPath includes a full authoring platform. Medical coordinators manage diagnoses, treatment protocols and medications themselves — and see exactly what health workers will see, before anything reaches a device.
Clinical guidance changes: protocols are revised, drugs are added or replaced, regional adaptations are needed. In most digital health tools, every one of those changes is a software change. In ClinPath it is a content change — made by the clinical team in a web application, validated automatically, and distributed to field devices without touching the app.
The authoring platform covers the full clinical catalogue: diagnoses with severity levels and WHO ICD-10 codes, treatment protocols built from reusable blocks, and a medication formulary with dosing rules. Every change is validated on entry and recorded in an audit trail.
One Governed Diagnosis Catalogue
Every diagnosis in every workflow lives in one catalogue, with severity levels and WHO ICD-10 codes assigned through a guided review workflow. Autocomplete against the official ICD-10 classification keeps coding consistent — and makes exported data meaningful to national health information systems.
The platform continuously cross-checks content: a diagnosis without treatment content, or a severe variant missing its own medications, is flagged to the team before it can surprise anyone in the field.
Treatment Protocols from Reusable Blocks
Treatment protocols are assembled from reusable building blocks — referral notices, medication regimens, advice text — shared across diagnoses. Update a block once and every protocol that uses it is updated.
A live preview beside the editor shows the protocol exactly as the health worker will see it, including conditional content: instructions that depend on the patient's weight or on what the facility can provide.
Simulate Before You Ship
The built-in treatment simulator answers the question every medical coordinator asks: what will the health worker actually see? Pick any combination of diagnoses, a patient weight and a facility context, and the simulator renders the exact treatment plan a device would show — same engine, same display, by construction.
An engine-records panel explains every decision: which severity band was selected, why a line was preferred, and which alternatives stand ready — so protocol reviews are grounded in evidence, not guesswork.
Authoring Platform Capabilities
🗂️ Diagnosis Management
One catalogue for all workflows, with severity levels, WHO ICD-10 coding via autocomplete, and a guided terminology review process.
💊 Medication Formulary
Medications, formulations and dosing rules managed centrally. Dose calculations on devices always run against the current formulary.
🧩 Reusable Protocol Blocks
Referral notices, regimens and advice text defined once and shared across diagnoses — one change updates every protocol that uses it.
✅ Continuous Validation
Uploaded workflows and authored content are checked automatically; gaps and inconsistencies are reported to the team, never silently shipped.
🔍 Device Parity Preview
Previews and the simulator use the same rendering engine as field devices — what the author approves is what the health worker sees.
📜 Full Audit Trail
Every content change is recorded — who changed what, and when. Role-based access controls who can author, review and publish.
🏥 Facility-Aware Distribution
Organize facilities in a flexible hierarchy; assign each one its workflows and context (equipment, regional diseases). Devices receive only what applies to them.
🚀 Publish Without Rebuilds
Approved content reaches field devices as data at their next synchronization. No app updates, no redeployment, no downtime.
See It with Your Own Protocols
We are happy to walk your clinical team through the platform
Request a Demo