Occentra comparison

Occentra vs Meddbase

Buyers looking for a Meddbase alternative for occupational health management are usually weighing a focused occupational health platform against a broader clinical and practice-management system.

Occentra is the stronger choice where occupational health needs an explicit Referral-to-Case model and versioned configuration, rather than sitting inside a wider EHR, billing and portal suite.

Book a walkthrough Explore the platform

Reviewed 20 September 2026 by the Occentra product team

Why Occentra

Why organisations evaluate Occentra as a Meddbase alternative

Meddbase is a documented occupational health and clinical operations platform: employer portal referrals, Case Management work items, consultations, health surveillance, billing rules and report authorisation sit inside a wider EHR and practice-management product. Cority acquired Meddbase in January 2025 and describes it as joining Cority Health Cloud, while Meddbase remains a distinct product. Occentra is built only around occupational health delivery, with Referrals, Cases and versioned Forms as first-class records.

Occupational health as the product, not one configuration of a clinic system

Clients, Employees, Referrals, Cases, Tasks, appointments, Forms, Documents and Reports are the operating language in Occentra. Meddbase's occupational health workflows sit inside a broader clinical and practice-management platform that also serves private practice, billing and electronic health records. That breadth is useful when those jobs belong in the same system. It is a different starting point from a platform designed only for occupational health.

A Referral that stays distinct from the Case

In Occentra a Referral is the request for service. Accepting it opens a Case, and the Tasks, appointments, documents and outcomes for that work sit inside the Case. Meddbase Case Management is commonly initiated from the Occupational Health Portal or by booking on behalf of an employer, then processed as incoming referral work items, collaboration, appointment booking and follow-up referrals. Both models can run a live service. They organise ownership, triage and history differently.

Versioned Forms rather than consultation-bound clinical forms

Occentra administrators publish Form Templates as versions and keep earlier submissions bound to the version that was completed. Meddbase captures clinical information on custom Clinical Forms inside a Consultation, and employers can attach management questionnaires to portal referrals. Versioned product configuration is the better fit when the same questionnaire must change over years without rewriting the meaning of earlier answers.

Operational data that occupational health teams can report from directly

Occentra stores Form answers against published templates and reports from Referral, Case and Form records. Meddbase publishes a Reporting Engine, portal dashboards for managers and clients, and options to send data to visualisation tools or a warehouse. Structured occupational health records matter when turnaround, caseload and outcomes need to come from the same objects the team uses to do the work.

Key differences

Where Meddbase's clinical platform and Occentra diverge

Focused occupational health platform versus broader clinical operations

Occentra

Occentra is developed as one occupational health platform, with each capability designed against the same Client, Employee, Referral and Case model.

Meddbase

Meddbase is a cloud EHR and practice-management platform with substantial occupational health workflows, used by occupational health providers, corporate occupational health and health-assessment businesses, and now part of Cority.

Why Occentra has the advantage:

A single occupational health model keeps configuration, reporting and permissions consistent across the service, instead of occupational health sharing structures built for wider clinic operations.

Referral-to-Case versus portal-initiated Case Management

Occentra

A Referral is the request. Accepting it opens a Case, so intake, triage and delivery remain separately measurable.

Meddbase

Meddbase Case Management is initiated by an Occupational Health Portal referral or by a user booking on behalf of the employer. Incoming referrals become Work Items for collaboration, reassignment to a Case, appointment booking, follow-up referrals and SLA tracking in the portal.

Why Occentra has the advantage:

Keeping the Referral as its own record makes it clearer what was requested, who accepted the work, and which operational Case then carried it.

Versioned Form Templates versus consultation Clinical Forms

Occentra

Administrators build Form Templates and controlled value lists in the product, publish them as versions, and keep earlier submissions bound to the version that was completed.

Meddbase

Meddbase Clinical Forms are used in the Consultation, can be custom built, and support discharge actions that start occupational health report writing. Portal referrals can attach a management questionnaire. Patient review can authorise the report, request factual changes, or decline release to the employer.

Why Occentra has the advantage:

Versioned Forms keep historical answers meaningful as questionnaires change. Report release in Occentra is an explicit occupational health process, rather than a consultation discharge plus patient-authorisation sequence.

Product configuration versus portal, billing and eligibility setup

Occentra

Service variation is handled as account configuration: Form Templates, lookups, roles and a live Xero Projects integration for billable Work Entries.

Meddbase

Meddbase onboarding for an occupational health client covers employers, appointment types, Billing Rules, Charge Bands, eligibility, portal permissions, SLAs and whether managers may refer or book. Eligibility is described as connected to a booking-to-billing engine.

Why Occentra has the advantage:

Occentra keeps occupational health configuration inside one operating model, and leaves invoicing in the finance system. That is simpler when the buyer does not need charge bands and portal eligibility as the commercial spine of the service.

Capabilities

Meddbase and Occentra side by side

A summary of how each product approaches occupational health work. Occentra's status is stated as it stands today. Meddbase's positioning is taken from its current occupational health pages and help centre, and may differ by module and contract.

Capability

Occentra

Meddbase

Operating model

Referral management

Referrals have their own lifecycle, referrer context and preserved state history

Occupational Health Portal referrals, on-behalf bookings, incoming referral Work Items, collaboration and follow-up referrals

Why it matters Keeps the original request separate from operational delivery

Case management

Accepting a Referral opens a Case as the operational workspace for delivery

Case Management with case titles, reassignment between cases, portal Case Insights and SLA tracking

Why it matters One place where accepted work is owned, progressed and closed under explicit conditions

Appointments and diary

Practitioner diaries and Case appointments with timezone handling and conflict controls

Slot Finder booking from referral processing, direct manager bookings from the portal, and consultation attendance leading into clinical documentation

Why it matters Appointments belong to the Case, so scheduling and occupational health work stay connected

Configuration

Configurable Forms

Form Templates are configured in the product, published as versions and validated on submission

Custom Clinical Forms in consultations, plus management questionnaires attached to portal referrals

Why it matters Configuration is versioned so historical meaning is preserved

Manager and employer access

Managers and HR users can submit referrals and see case status without clinical detail

Occupational Health Portal for referrals, direct bookings, questionnaires, document sharing, case tracking, messaging, SLA alerts and reporting

Why it matters Managers see referral status without clinical detail, keeping operational and clinical boundaries clear

Employee access

Employees can complete assigned forms and questionnaires through a controlled interface

Patient review and authorisation of occupational health reports, with optional download, factual-change requests or declined release to the employer

Why it matters Employee access is tied to assigned Forms on the Case, while report release remains an occupational health process rather than patient portal authorisation

Practitioner workflow

Assessments and clinical workflow

Case appointments with versioned Forms used to capture structured assessment information

Consultation view with Clinical Forms, optional extra form episodes, SNOMED matching, discharge actions and occupational health report writing

Why it matters Assessment information stays attached to the Case and the published Form version, rather than only to a consultation episode

Health surveillance

Surveillance work is organised through Employees, Referrals, Cases, versioned Forms and Appointments

Health surveillance with risk-profile population management, automated recalls, manager compliance reporting and direct diary bookings via the portal

Why it matters Surveillance uses the same occupational health records as referrals and cases, so history is not held in a separate tracker

Reporting and records

Reporting

Named operational Reports with typed parameters, an operational dashboard and CSV export

Reporting Engine, portal dashboards for managers and clients, and options to publish datasets to visualisation tools or a warehouse

Why it matters Structured Referral, Case and Form answers support operational reporting directly

Commercial / implementation model

Integrations

REST APIs, webhooks and a live Xero Projects integration for billable Work Entries

Public APIs, including Occupational Health Portal APIs used to exchange referral and case data with the provider system

Why it matters Occupational health work stays in Occentra, while finance and surrounding systems receive only the records they need

Billing and eligibility

Billable Work Entries recorded against Cases, with Xero Projects used for downstream invoicing

Billing Rules, Charge Bands and eligibility connected to portal referral, booking and a booking-to-billing engine

Why it matters Clinical and operational records stay separate from invoicing, which reduces the chance that commercial rules become the workflow

Product direction

Developed as one coherent platform, with new capability added to the same operating model

Distinct Meddbase product following Cority's January 2025 acquisition, described as joining Cority Health Cloud

Why it matters The platform is designed as one coherent occupational health system

Incumbent fit

When remaining with Meddbase may still be reasonable

A move from Meddbase should start with workflow fit, not a feature list. Meddbase already combines occupational health Case Management with clinic operations, an employer portal, billing rules and patient report authorisation. If that combination is how the service actually runs, remaining can be the more practical choice.

Employer users already work in the Occupational Health Portal for referrals, bookings, questionnaires, SLA tracking and follow-up
Billing Rules, Charge Bands and eligibility already control what can be booked and how it is charged
Consultation Clinical Forms, patient report authorisation and wider EHR or private-practice work are part of daily delivery
Health surveillance recalls, manager bookings and portal compliance dashboards are already embedded

Where occupational health needs to be the core system, with an explicit Referral-to-Case model and versioned configuration, Occentra is the more coherent foundation. Treat migration as a mapping of referrals, cases, forms, surveillance history and commercial rules, not as a screen-for-screen replacement.

Demonstration

Six questions when evaluating a move from Meddbase

These questions expose whether Occentra's operating model can carry the work you run in Meddbase today, and what would have to be remapped rather than copied.

How does a portal or manager referral become a distinct Referral and then a Case, and who owns triage, booking and report release?
Which historical Cases, Clinical Forms, questionnaires and surveillance recalls need to move, and how will their meaning be preserved?
Can administrators change Forms as versioned product configuration without rewriting earlier answers?
How should employee report review work if today it depends on patient authorisation before employer release?
How are health surveillance recalls, eligibility and manager bookings represented if they currently depend on Meddbase's surveillance and portal setup?
Which Billing Rules, portal permissions and API behaviours must continue during a move, and which can sit in finance or integration instead?

Ask both vendors to demonstrate these using one of your live Meddbase workflows, including an incomplete referral and a report that is not yet released, rather than a prepared product script.

See a Meddbase workflow in Occentra before you decide

Bring one live referral, case, surveillance cycle or report-release process. We will map it onto Occentra's Referral-to-Case model, show what configuration covers today, and identify migration questions before anyone commits to a move.

Book a walkthrough Register interest