A healthcare data warehouse that fills itself

Most data warehouse projects start by building pipelines out of every system. HealthOS keeps an analytics-grade star schema warehouse beside its operational FHIR record, filled from the care already recorded, so dashboards, plain-English questions and your own BI tools read today’s data instead of last month’s extract.

NWAU Periscope in HealthOS on a demonstration year of invented activity: NWAU to date, the position against the phased target, the projected year-end, Commonwealth cap headroom in NWAU and dollars, and tonight’s inpatients as an estimate, above the year by month against the phased target. A banner says how much of the year’s NWAU is illustrative and why.

In the warehouse today

Census

Daily bed and place occupancy across every facility.

Episodes

Admissions, discharges and length of stay, by facility, admission source and separation mode.

Incidents

Falls, pressure injuries, medication errors and restraint events.

Finance

Revenue, cost allocation and margin by service line.

What it does

Data you can trust, ready when you ask

Star schema

A warehouse beside the operational record

Dimension tables for facilities, wards, patient types, providers and funding accounts sit beside fact tables built for care sector reporting, with curated views that answer the questions executives ask, so you are not waiting for a model to be built.

Occupancy trend by facility, ward and room type
Incident rates per 1,000 bed-days, with benchmarking
Connect your own BI tool through standard SQL or FHIR bulk export

The facts are read through one certified model of measures and definitions, so your BI tool, an export and the dashboards in HealthOS agree on what each number means.

Data & insights →

Ask in plain English

No SQL to write

Anyone can ask a question in plain English, such as “falls by facility this quarter”, and HealthOS finds the right pre-built metric and narrates the answer. Thresholds on any metric raise a notification when they are breached.

Activity and NWAU

Where the year will land

Every coded episode is priced in National Weighted Activity Units by IHACPA’s National Efficient Price Determination, against a phased target and the Commonwealth cap, and a public hospital network’s own warehouse extracts can be imported and priced the same way.

NWAU Periscope →

Every event kept

An audit trail you can query

Every intake, assessment, service order and clinical entry is captured as an event, and every change keeps the user, the time and the before and after values, for seven years.

Standard CSV, JSON and FHIR R4 exports, without custom ETL
De-identified cohorts for research

Research →

Your other sources

Bring the rest of your data in

Data from the systems around HealthOS lands in the same record: HL7 v2, FHIR bulk data, CSV, SFTP and staging tables from PostgreSQL, MySQL and SQL Server sources, including cloud data warehouses.

The enterprise service bus →

Questions

Before you ask

Question	Answer
Does it replace our enterprise data warehouse?	It does not have to. HealthOS can feed the warehouse you run, through SQL, CSV, JSON or FHIR R4 bulk export, and read from it through staging tables.
What is not in the warehouse yet?	Claims, AN-ACC and quality facts are in build, and claims reconciliation views are on the roadmap. The Data & insights page keeps the current list.
Is it built on standards?	Yes. The record is aligned to FHIR R4 and conforms with the AU Core profiles, so the warehouse and the exports use standard resources.

Data & insightsDashboards for every role, plain-English questions and threshold alerts. NWAU PeriscopeActivity priced in NWAU against target and the cap, during the year. Enterprise service busHow data from your other systems arrives. In the boardroomWhat HealthOS means for executives and boards.

See the data warehouse in action

We will walk you through it on real data. Bring the hardest thing your current system can’t do.