A diagnostic engine for hospital material flow. From cost center to billing event, what slipped through the cracks?
A surgeon scans an implant. It never lands on the invoice. Departments lose CHFs every day with no audit trail.
The same line appears in usage and again as an inventory adjustment. Net zero on the books — real money in flight.
A material's price was updated in SAP but not in OPALE. The wrong number rides every transaction for months.
OPALE, SAP MM, SAP IS-H, Navision. We map their columns to one canonical model. Your data stays where it is.
Each signal is a YAML question: "What's the imbalance between usage and billing for material X this month?" Compiled to SQL, validated against the contract.
When a thesis confirms — "we are losing money on unbilled implants" — the system explains why and what to do.
CHF-quantified, severity-tagged, drill into the affected case in two clicks. The interesting findings come to you.
"Are we losing money on unbilled materials?" Confirmed / plausible / not observed. With the evidence chain attached.
The pharmacist's note that "material 638876a was renamed in 2024" lives next to the data. It travels with the build.
The reference tenant uses nuMetrix to close the books with confidence. Two synthetic mirror tenants run in parallel for calibration — known defect rates, measured recall.
No cloud upload required. nuMetrix runs on a laptop, in a hospital VLAN, or peer-to-peer through a tunnel — your call. Built on jinflow.