Deployment
Custom Implementation
For hospitals, clinics and health systems deploying Umoja as their EHR or operational platform.
Request scope reviewEngagement & Pricing
Pricing built around the project. Not the headcount.
Umoja does not charge per user or per account. Commercial scope is based on what your organization needs implemented, integrated, hosted, supported and maintained.
No per-user pricingScope-based implementationOptional retainmentUpgrade-by-requestAcquisition option
A 40-user clinic and a 4,000-user health system do not differ only by login count. They differ by facilities, workflows, integrations, migration, infrastructure, security requirements, training, support and operating complexity.
Enterprise
Institutional / Government
For multi-facility, regional or national programs with localization, interoperability and infrastructure requirements.
Discuss enterprise deploymentSupport
Retainment Services
For customers that want continued technical support, monitoring, releases, optimization or managed operations after handover.
Discuss supportOwnership
Platform Acquisition
For organizations interested in acquiring the technology asset rather than operating under a standard software engagement.
Explore acquisitionNo seat meter
Your organization can grow without paying for every additional login.
User population still matters for infrastructure sizing, training, support and rollout planning—but it is not the commercial unit used to meter software access.
✓
Users and accountsNo per-user or per-account software licensing.
✓
Implementation scopePriced according to modules, facilities, workflows, migration and integrations.
✓
Hosting and supportQuoted based on the service model, capacity and responsibilities selected.
✓
Future upgradesSeparately reviewed, scoped and costed when requested.
What drives cost
Scope the work that actually creates implementation effort.
Pricing is intentionally not published as a fake “starting at” number because healthcare deployments vary materially.
| Cost driver | Examples |
|---|---|
| Facilities & departments | Number and diversity of hospitals, clinics, units and service lines |
| Modules | Patient access, nursing, provider, pharmacy, lab, imaging, ED, billing, OR, etc. |
| Workflow customization | Forms, documentation, workqueues, roles, approvals, alerts and navigation |
| Integrations | FHIR, diagnostics, PACS/RIS, insurance, national systems, devices and external APIs |
| Migration | Legacy patient, provider, appointment, document and reference data |
| Infrastructure | Cloud/VPS/on-prem architecture, capacity, monitoring, backups and security controls |
| Training & rollout | Superusers, end users, go-live coverage, phased or big-bang approach |
| Support model | Handover only, retained support, managed hosting, SLAs and release management |
Upgrade model
Change only when you need change.
1. Request
Describe the feature, integration, workflow change or redesign required.
2. Scope
Define requirements, dependencies, acceptance criteria and effort.
3. Quote
Agree cost, schedule, responsibilities and release plan before work begins.
4. Deliver
Build, test, validate and release according to the approved scope.
Get a scope—not a seat quote.
Tell us what you are trying to deploy and we can discuss the factors that would determine implementation, hosting, support and future-change costs.