Build once. Prescribe everywhere.
MedBackend is the backend where clinical pipelines are versioned, signed off, and executed across any FHIR system — reused like software packages, governed like clinical practice.
Medical logic should be reusable
Every integration project rebuilds clinical workflows from scratch, then rebuilds the evidence that they work. MedBackend treats that logic as versioned infrastructure instead.
Versioned, not rewritten
Clinical pipelines are stored as immutable, checksummed versions with a full lifecycle — draft, review, active, deprecated, retired. Roll forward or back without touching backend code.
Published by sign-off
A pipeline goes live when a named person signs it off, and that sign-off is the transaction that publishes it. Approval is not a process around the system; it is the mechanism inside it.
Runs on any FHIR system
One pipeline executes against any FHIR R4 server, alongside legacy sources and external APIs — without a bespoke integration per site.
Clinical pathways as governed infrastructure
Define a pathway once as a state machine over FHIR resources. MedBackend versions it, routes it through review and sign-off, runs it against live patient data, and keeps the evidence that it did.
Lifecycle with real states
draft → review → active → deprecated → retired. Only one version is active at a time, enforced at the database. Retiring a pathway with runs still in flight fails closed instead of stranding them.
Sign-off is the publish
Recording a sign-off is what promotes a version to live — writing the immutable version blob, flipping the registry, and republishing configuration in one transaction, in that order.
Evidence, not log archaeology
Every run assembles into a timeline from FHIR AuditEvents — what changed, from what to what, caused by what. Export any run as a JSON evidence bundle.
Readable by clinicians
Each pathway renders as a state diagram and a plain-language description, with no YAML and no pipeline vocabulary. The people who sign off can see what they are signing.
Built for review
Versioned execution and QMS export give quality and regulatory teams a record shaped the way they already work.
Designed for regulated environments
Compliance posture is a property of the architecture, not a checklist bolted on afterwards.
HIPAA-ready architecture
Access control, encryption in transit and at rest, and an audit trail for every operation.
GDPR-ready governance
Data minimisation, tenant isolation, and traceable processing.
Swiss data residency
Compute and data services both run in Swiss regions. Sovereignty is a deployment property you can point at, not a promise.
Auditable by design
FHIR AuditEvent for every operation, immutable pathway versions, and exportable evidence bundles.
Ready to stop rebuilding clinical logic you have already written?
Walk through your integration surface with us and see what a versioned, signed-off pipeline would look like in your environment.