Platform comparison

The composite bar nobody clears.

Feature by feature, against the eight platforms a hospital actually evaluates. The pattern in the ✗ column is the entire product thesis: the back-office platforms go blank at the patient dollar, and the revenue-cycle platforms go blank at the ledger.

best in class ships it partial · dated · via partner absent or undocumented

The ledger half

Where the back-office platforms are strong — and where the revenue-cycle vendors go blank.

CapabilityWorkdayOracleInforNetSuiteIntacctEpicathenaWaystarVeloERP
General ledger & close
2027
AP & three-way match
2027
Budgeting & department statements
2027
Healthcare supply chain
eProc
2027
Par levels at point of care
via Tecsys
2027
Lot / expiry / recall genealogy
partial
2027
Core HR
thin
2027+
24/7 clinical payroll rules
contested
partial
partial
2027+
Biomedical asset & PM
partial

The revenue half

Where the revenue-cycle vendors are strong — and where the ERPs go blank at the patient dollar.

CapabilityWorkdayOracleInforNetSuiteIntacctEpicathenaWaystarVeloERP
Patient accounting
separate platform
pipe only
Eligibility 270/271
Claim scrub & 837 submission
835 auto-posting to a GL
cross-platform
native
Denial workqueue by reason code
AI appeal drafting
2026 agents
Payer contract modeling
FinThrive

The seam — where the category is empty

These four rows are the entire product thesis. Note that this is the only block where the ✗ column runs almost all the way across.

CapabilityWorkdayOracleInforNetSuiteIntacctEpicathenaWaystarVeloERP
One data model across both halves
two platforms
2027 target
Cost per encounter (supply + labour)
warehouse
warehouse
mid-2027
Cross-module AI assistant that acts
Illuminate
Agent Studio
Velocity
SuiteAgents
Sage AI
Penny / Factory
80+ features
AltitudeAI
all six domains
AI included, never an SKU
tiered
tiered
bundled
module

Commercial & operational

The rows a 60-bed community hospital actually decides on — and the one line where the whole category is blank.

CapabilityWorkdayOracleInforNetSuiteIntacctEpicathenaWaystarVeloERP
Reachable below 300 beds
marginal
Published list pricing
partial
Never percent-of-collections
4–8%
Analytics included, not an add-on
tiered
tiered
module
Fixed-price implementation
partner
partner
managed
managed
90 days
Public REST API + webhooks
gated

"2027" entries reflect Epic's publicly stated EpicOps rollout dates. VeloERP's column is a target spec, not a shipped capability — see the roadmap on About for what exists when.

The read of the board

Three rows decide this category.

Row that decides it

835 auto-posting to a GL

Exactly one column can hold this natively, because it requires the remittance and the ledger to be in one database. Oracle can do it across two platforms with an interface; nobody else can do it at all. This single row is the product.

Row that dates it

Epic's 2027 column

Every ✗ in Epic's back-office rows carries a public expiry date. Against the ~44% of hospitals on Epic our advantage is time-limited; against the rest it is structural. We say so rather than pretending otherwise.

Row nobody defends

Fixed-price implementation

The one line where the entire category is blank and the customer pain is loudest. It is also the cheapest thing to claim and the most expensive to honour — which is why we made it a product constraint rather than a marketing line.

See the 835 post to the ledger