Product architecture

How Meridian Health works

A single platform that ties together patient care, physician workflows, partner referrals and operations — built around a shared clinical rules engine.

Three portals, one clinical core

Patient portal

Treatment plan, refills, messaging, files, billing.

Clinician & admin portal

Review queue, patient charts, unified inbox, billing ops, reporting.

Partner portal

Refer clients, track conversion, view payouts.

Order lifecycle

Patient request

Refill, new Rx, or intake

Rules engine

Eligibility, safety, dosing

Provider review

Approve, decline, adjust

Pharmacy

Dispense & ship

Billing

Charge & receipts

Patient update

Tracking + care msg

Clinical rules engine

Safety checks

Drug interactions, contraindications, allergy screen, dose ceilings.

Eligibility

Age, jurisdiction, plan enrollment, labs recency.

Auto-routing

Urgent items surface to on-call; routine items go to standard queue.

Refill logic

Cadence, remaining refills, adherence signals, lab windows.

Escalation

Flags for red-flag responses in intake and messaging.

Audit trail

Every rule fire and provider decision is versioned and reviewable.

System boundaries

Clients

  • Patient web
  • Clinician web
  • Partner web
  • Admin console

API layer

  • REST / RPC
  • Auth & RBAC
  • Realtime
  • File signing

Services

  • Rules engine
  • Orders
  • Billing
  • Referrals

Data

  • Postgres
  • Object store
  • Analytics
  • Audit log

Explore the working platform

Jump straight into any role — everything below the marketing surface is live.