Hospital management operates across a fundamental data architecture problem: clinical outcomes live in the EMR, financial performance lives in the ERP — and the decisions that matter most require both.
This brief defines six KPIs that close that gap. Each one combines clinical data from the EMR with financial data from the ERP, revenue cycle system, or CMS reporting infrastructure. Each one has a measurable financial consequence when it is not tracked — or tracked incorrectly. And each one demands an interoperability infrastructure capable of joining data across the systems that hold it.
The Six KPIs
Each KPI in this framework was selected on strict criteria: it must combine clinical and financial data in a way that neither lens could answer alone, must be tied to a real financial consequence, and must be something executive leadership can act on.
Why the Data Silo Problem Is Getting More Expensive
The financial stakes of managing hospitals with disconnected data have increased substantially. CMS now penalizes hospitals across three simultaneous programs — HRRP, HAC Reduction, and HVBP — with combined exposure reaching 6% of all Medicare payments. For a hospital with $200M in Medicare revenue, that is $12M in maximum annual penalty exposure driven entirely by clinical quality metrics that most CFOs have never seen in a financial context.
Labor — 56% of total hospital cost — is managed through HRIS and payroll systems that have no visibility into the clinical outcomes that staffing levels directly produce. Research shows risk-adjusted 30-day mortality increases 7% for every additional patient per nurse. That is a financial number, not just a clinical one — but the data required to calculate it sits in two completely separate systems.
Service lines are cut based on raw cost data without case mix adjustment. Oncology with a raw margin of −2.1% looks like a loss leader — until CMI adjustment reveals a +7.3% margin and a clinically irreplaceable service. The wrong decision is made because the right data is not combined.
The Integration Architecture
Each of the six KPIs requires data from at least two distinct enterprise systems, joined on a shared identifier that must be mapped and maintained as systems evolve. CPAD joins EMR discharge data with ERP cost data on encounter ID and billing period. The readmission rate joins EMR clinical flags with CMS payment data on Medicare claim ID. The VBC composite joins EMR quality measures with three simultaneous CMS program calculations.
The standards that enable these joins — HL7 FHIR R4 for clinical data exchange, HL7 v2 ADT for real-time event feeds, USCDI for standardized clinical data elements, X12 EDI for claims and remittance — are well-established. The challenge is not the standards. It is the precision of implementation: mapping identifiers across systems, handling different data granularities, validating completeness, and maintaining accuracy as source systems change.
A Delivered Solution, Not a Toolkit
Most interoperability vendors sell a platform — tools and a professional services team that hands the customer the build plan. The integration work, the maintenance, the monitoring, and the ongoing engineering still land on the health system's IT team.
Intely Connect operates differently. The integrations required to power these six KPIs are built by Intely, operated by Intely at 99.99% SLA in AWS, and delivered at a fixed cost on a fixed timeline. The health system owns the outputs — the connected data, the KPI dashboards, the analytics layer — without owning the plumbing.
Once the underlying integrations are in place, the same infrastructure supports an unlimited range of additional analytics. The connections are built once. The insights compound.
