Dedicated cloud infrastructure
Single-tenant deployment isolated from the multi-tenant platform. Your choice of region (AU, EU, UK, US, on-prem partner) with your own KMS keys and audit boundary.
For Enterprise
Hospital networks, multi-site practices
MedMETs Enterprise is built for organisations that need dedicated infrastructure, custom integrations, and governance tooling — not the multi-tenant plan with a few extra seats.
- Dedicated cloud
- Custom HL7 FHIR
- SSO + AD
- 99.9% SLA
Multi-site, single source of truth
One platform. Every site. Audited end-to-end.
Your network connects to a dedicated MedMETs tenant. Sites stay autonomous; the Medical Director gets one console.
- 1dedicated tenant
- 5regions available
- ∞seats per network
- 99.9%uptime SLA
Enterprise platform
Six pillars of the enterprise plan
Everything in the Professional plan, plus the infrastructure, integration, and governance layer that hospital networks need to deploy safely at scale.
Custom HL7 FHIR integrations
Bidirectional integration with your existing EHR, PAS, LIS, and RIS — built by the MedMETs integration team to your spec, not via a self-serve connector marketplace.
SSO + Active Directory
SAML 2.0 and OIDC SSO with your IdP of choice. Group memberships drive role assignment; deprovisioning happens automatically when the upstream account is disabled.
Medical Director governance
Dedicated Medical Director module: policy enforcement across the network, central template + checklist library, audit log review queue, KPIs by site and clinician.
Custom model fine-tuning
If your network has a specific speciality mix, vocabulary, or documentation standard, the AI can be fine-tuned to your case mix. Your data stays in your tenant.
99.9% uptime SLA + 24/7 support
Contractual SLA with credits for breach. 24/7 dedicated support with named technical account manager and pager rotation visibility for sev-1 incidents.
Implementation
From kick-off to network-wide rollout
Enterprise rollouts run 12–20 weeks depending on network size, integration complexity, and pilot scope. The plan is fixed in writing at discovery — no scope creep, no shadow timelines.
Discovery + scoping
2-week structured discovery with your CIO + Medical Director. Output is a written implementation plan covering integrations, governance, training, and go-live milestones.
Infrastructure provisioning
Your dedicated tenant is built in the region of your choice with your KMS keys, your SSO, your network policies. Pen-tested by your internal security team before any data lands.
Integration build
HL7 FHIR adaptors built to your EHR and PAS. Test environment shadowed for 4 weeks before any production integration is enabled.
Site-by-site rollout
Pilot site first (typically a single department or speciality), then network-wide rollout in batches. Your dedicated implementation team is on-site for each batch.
Talk to sales
Enterprise plans are custom-quoted based on number of clinician seats, infrastructure requirements, integration scope, and support level. The sales team will route you to a clinical-success lead in your region.