How Uverse Health works.
A layered platform: shared identity and infrastructure at the base, workspaces for every participant above it, and coordinated care moving across them.
From a need to coordinated care.
Identity. People and organizations are identified once and recognized across the platform.
The layers.
Identity & access
Accounts, organizations, roles and sign-in across every workspace.
Shared services
Messaging, notifications, audit, analytics and billing inherited by every tenant.
Tenant model
Platform, country, region, health system and facility — modelled as they exist.
Workspaces
Patient, provider, organization and operations workspaces built on the same graph.
ClinicOS
The clinical operating layer for in-clinic encounters.
Learn moreAPIs
Developer access to the same platform services.
Learn moreOne coordinated platform, layered for every participant.
Identity sits underneath everything. Workspaces and services share the same platform layer, and every record is scoped to a country, organization, facility and workspace.
Every participant gets the workspace they need.
Uverse Health capabilities are provisioned and configured per organization, jurisdiction and deployment.
Uverse Health Platform
Shared identity, tenancy, audit and coordination services.
Platform API
Governed, tenant-scoped API for integrations.
Identity & Authentication
Verified identity and sign-in across workspaces.
Uverse Wallet
Payments and transaction records for care.
Patient Workspace
Identity, care search, visits, records and follow-up.
Provider Workspace
Credentials, availability, encounters and documentation.
Marketplace / care search
Find services, compare availability and pricing.
Vendor Workspace
Verified supplier participation and catalog coordination.
Research participation
Study discovery and consent-aware recruitment.
ClinicOS
The encounter from arrival to disposition and follow-up.
Hospital Workspace
Facility operations, referrals and capacity coordination.
Pharmacy Workspace
Orders, dispensing coordination and inventory signals.
Laboratory Workspace
Specimens, pending results and result routing.
Imaging Workspace
Imaging orders, scheduling and report coordination.
Payer / Insurance
Eligibility and coordination with participating payers.
Employer
Employee health program coordination.
Pharmaceutical Workspace
Verified supply, traceability and distribution.
Organ donation coordination
Registry and coordination with participating organizations.
AI-assisted clinical routing
Clinical decision support, clinician reviewed.
Uverse Pharma Africa
Closed-loop pharmaceutical supply for African markets.
One platform. Every layer of the healthcare ecosystem.
Uverse Health models the real hierarchy of care delivery — platform, country, state, health system, every facility inside it — plus the enterprise organizations that intersect with it.
Every tenant inherits shared services, audit and policy from its parent — and can override at its own tier.
Built for every participant in the healthcare ecosystem.
Purpose-built surfaces on one shared operating system — patients, providers, ancillary services, payers, public health, government, research and donation networks.
Infrastructure every tenant inherits.
Cross-cutting services shipped once, governed centrally, available to every tenant on the platform.
A sample view of the coordination graph.
How availability, activity and public-health signals flow through the operating system. Illustration only — roles, organizations and signals are samples.
- AvailablePrimary care clinicianSample Clinic
- Next slotSpecialistSample Hospital
- AvailablePharmacistSample Pharmacy
- BusyLab teamSample Lab
- Care coordinator sent a sample referral · Sample Hospital
- Specialist accepted a sample referral · Sample Clinic
- Lab team returned a sample result · Sample Lab
- Pharmacist confirmed a sample order · Sample Pharmacy
- Sample population-health signalSample Organization
- Example coordination alertSample Health System
- Illustrative care signalSample Region
Deploy Uverse across your network.
Health-system, payer, government, research and donation-network deployments — with data residency, SSO and enterprise onboarding.
Contact enterpriseBuild on the coordination graph.
FHIR R4, SMART on FHIR, HL7, OIDC and OAuth2 — plus first-party APIs for referrals, orders, identity and audit.
Open developer portalTalk to the Uverse Health team.
Tell us about your organization and what you want to coordinate. We'll respond with what is available for your deployment.
