01
Find the right visit
Patients start with the service, specialisation and clinician options configured for the provider.
PatientHub by MPED
A clearer digital front door for your healthcare organisation.
PatientHub gives healthcare providers a configurable patient-facing journey for finding services and appointments, completing booking details and receiving a clear confirmation.
Your organisation purchases and configures PatientHub. Your patients use the experience you launch for them.
View the patient portalMicrosoft Marketplace purchase will be shown here only when the UK offer is verified and available.
patienthub.mped.co.uk
UK provider tenantPatient journey ready to demonstrate
Built forHealthcare organisations, clinics and medical providersCommercial modelB2B SaaS for a healthcare provider organisationMarketUnited Kingdom / GBP
The product experience
One coherent journey, from finding care to confirmation.
Real screens from the PatientHub UK tenant show the experience your organisation makes available to patients.
02
Choose an appointment
The booking journey brings visit type, clinician, date and payment option into one guided flow.
03
Complete and confirm
Patients provide the required details, review the appointment and receive a clear booking confirmation.
For healthcare providers
Your organisation owns the service relationship.
PatientHub is purchased for a healthcare provider. Patients are the end users of the configured portal, not the commercial buyer.
A provider-specific environment
Each healthcare organisation is represented by its own tenant context, identity, locale, timezone, currency, feature settings and calendar-provider configuration.
A guided patient journey
Offer a consistent route from service discovery to available appointment, patient details and confirmation.
Operational visibility
Role-aware administration includes a tenant dashboard and controlled views of doctors, services, availability and bookings. Current configuration onboarding is assisted by MPED.
A platform that can grow
PatientHub supports a native scheduling path and integration-led deployments, with optional product modules introduced under explicit tenant configuration.
Provider identity
Your patient experience. Your provider identity.
PatientHub resolves branding by provider hostname and tenant settings, including product naming, logo, palette, contact details and local market defaults.
- Provider logo and identity
- Tenant-specific colour palette
- Local contact details
- UK English, Europe/London and GBP for the UK tenant
PatientHubDigital patient accessIdentity, colour, contact and market settings resolve from the provider tenant.
Integration
A patient-facing layer in front of your scheduling workflow.
PatientHub can use the MPED native calendar or a validated provider integration. The exact connection is confirmed during technical discovery and onboarding.
Named third-party integrations are offered only after provider-specific technical and contractual validation.01Patients↓
02PatientHub experience↓
03MPED integration and tenant layer↓
04Provider scheduling and operational systems
How PatientHub is deployed
A controlled provider onboarding, not a patient purchase.
- 01
Evaluate PatientHub
Review the patient journey, provider model and integration fit with MPED.
- 02
Create the provider engagement
Use the assisted sales path today. Marketplace purchase will appear only after a verified UK offer is available.
- 03
Provision the organisation tenant
MPED establishes the healthcare organisation context and controlled administrator membership.
- 04
Configure and connect
Apply provider identity, services and scheduling configuration, then validate required integrations.
- 05
Validate the patient journey
Run provider-specific acceptance checks before exposing the service to patients.
- 06
Launch to patients
The provider makes its configured PatientHub experience available to its patient community.
Operations and access
Verified platform foundations, without unsupported certification claims.
Tenant-aware runtime
Host and forwarded-host context resolve provider-specific runtime settings and keep UK and Polish tenant configuration separate.
Role-aware administration
Tenant administration uses membership and permission checks and is disabled by default until explicitly enabled.
Azure operational foundation
The represented infrastructure uses HTTPS, managed Azure services, Key Vault configuration paths and Application Insights telemetry.
PatientHub by MPED
See what PatientHub could look like for your organisation.
Start with a provider-focused demonstration and an integration fit review.