The honest version
Disaster recovery is an area where vendors are most tempted to overstate. We won’t. JamEMR is in pilot, and our disaster-recovery posture matches that stage: real backups today, formal commitments in development. This page tells you which is which.
What is in place today
- Scheduled backups. Backups of clinical data run on a schedule as part of each deployment’s operations.
- Restore procedures — being formalized. Restore procedures exist and are being formalized into documented, tested runbooks. We deliberately do not publish recovery time or recovery point objectives until we can stand behind them with test evidence.
- Change discipline that protects recoverability. Database schema changes ship as versioned, reviewed migrations, which means a restored database can be brought to a known schema state deterministically — a quiet but important part of real-world recovery.
- Approval-gated operational changes reduce the most common “disaster” of all: well-intentioned administrative mistakes. Privileged changes require explicit human approval.
- Pilot data posture. Pilot deployments run on synthetic (non-real-patient) data until a practice’s compliance prerequisites are complete — so recovery procedures mature before real patient records depend on them.
On our roadmap
In development, in order:
- Documented, tested restore runbooks — restore procedures exercised end-to-end, with results recorded as evidence rather than assumed.
- Defined recovery objectives — recovery time objective (RTO) and recovery point objective (RPO) targets published once validated by testing.
- Formal, SLA-backed disaster-recovery commitments — contractual recovery commitments offered to customers, planned ahead of general availability. Until this work is complete, we do not offer SLA-backed recovery guarantees, and no sales conversation should suggest otherwise.
- Business continuity planning as part of the documented policy pack in progress — covering continuity of operations beyond data restore, including personnel and communications.
What to ask us
If you are evaluating JamEMR for a pilot, reasonable questions include: what is the backup schedule for my deployment, when was a restore last tested, and what happens to my data if the pilot ends. We will answer all three specifically for your deployment — contact [email protected] or [email protected].