OneVision
Providers, payers & health systems

Healthcare

Every system that touches PHI has to survive an audit. Including the ERP.

ERP, EPM, and security work for providers and payers, built around HITRUST and HIPAA expectations so the back office can stand up to the same scrutiny as the clinical estate.

Draft for review — Draft sector positioning. Confirm the compliance frameworks named on this page are ones OneVision genuinely works to before this goes live.

You are probably here because

  • Clinical supply chain cannot tolerate a cutover window measured in days
  • ERP access reviews are a spreadsheet exercise before an audit rather than a control
  • Segregation of duties in finance and procurement was never designed, only inherited
  • A HITRUST or HIPAA assessment has surfaced findings in back-office systems
  • Cost accounting cannot answer what a service line actually costs to deliver

What makes this sector different

In healthcare the clinical systems get the security attention and the back office gets the exceptions. But the ERP holds vendor master data, payroll, and often enough PHI-adjacent information to matter — and access to it is rarely reviewed with the same discipline.

We treat the ERP as in-scope. Supply chain, finance, and payroll are implemented so a HITRUST assessment or an internal audit finds documented access, segregation of duties, and a clean trail, without slowing down clinical supply.

What we actually do here

Clinical supply chain continuity

Cutover planning built backward from the constraint that supply to a floor cannot stop, including rehearsed fallback.

Access control & segregation of duties

Role design and access review that satisfies an assessor because it reflects the organization, not because it was documented after the fact.

Service line costing

Cost models in EPM that let finance and clinical leadership discuss the same number for what a service line costs.

Audit-ready reporting

Financial and operational reporting with a trail an internal auditor can follow without asking for a query to be run.

0 min

Acceptable clinical supply downtime at cutover

24/7/365

Operating window every change has to fit inside

Annual

Assessment cycle the configuration has to keep passing

Standards & reporting

What you are measured against

We would rather name the frameworks up front than discover in week six that the configuration cannot satisfy one of them.

HITRUST CSF

Back-office system controls mapped to the framework your organization is already assessed against.

HIPAA security rule

Access, audit, and integrity controls applied to ERP data with the same seriousness as clinical systems.

Cost reporting & 340B

Reporting requirements accounted for in the design rather than discovered during the first submission.

Draft for review — Every framework above needs confirming against what OneVision can genuinely speak to in a first call. Naming one you cannot is worse than omitting it.

Enabled visions

What enabling a vision has meant in healthcare.

Nationwide healthcare provider

$27m

Overhead removed, with sales revenue up 8%

A national provider wanted its ERP and EPM systems consolidated so that sales and operations performance could finally be managed against one set of numbers.

The full record

Platforms we run in healthcare

Services we deliver most here

Straight answers

Questions from this sector

Can an ERP cutover really happen without disrupting clinical supply?

Yes, but only if the cutover plan is built backward from that constraint and rehearsed against real data. The failures we get called into are almost always ones where the plan was built forward from the project timeline instead.

Is the ERP in scope for HITRUST?

Treat it as in scope until an assessor tells you otherwise in writing. It holds enough sensitive data that assuming the opposite is how findings happen.

Our clinical and finance teams disagree about cost per case. Can EPM fix that?

EPM can make the disagreement explicit and resolvable by putting the allocation assumptions in one visible model. It cannot decide the assumptions for you — that is a leadership conversation, and it is usually the real work.