CHRIS-OS is middleware. It sits above every system your organisation already runs — clinical, rostering, HR, finance, WHS, incident management — ingests their data into a single canonical layer, and runs seven AI agents continuously on top of it.
The output is not a report. It is work done — documents drafted, submissions filed, leaders briefed, actions queued. Every output is timestamped, append-only, and auditable by regulators.
Source systems flow in. Intelligence flows up. Actions flow out. CHRIS-OS is the connective tissue — the layer that didn't exist.
From data ingestion to approved submission — four stages, all automated except the moment that requires human judgement.
CHRIS connects to your existing systems via authenticated API connectors. Each connector runs on a schedule — rostering every 15 minutes, HR daily, finance on-demand. Data is normalised at the connector boundary before it enters the canonical layer. Individual names are never stored — aggregation happens first. This eliminates Privacy Act exposure and makes CHRIS safe to position to staff, unions, and regulators.
All source data lands in a single Postgres schema — the canonical layer. Every table is append-only and timestamped. No data is ever modified or deleted — only new rows are added. This creates a complete, auditable history of every operational signal CHRIS has ever seen. The canonical schema spans 11 domains and 8 source system categories.
Seven agents run on scheduled cycles or event triggers. Each agent reads from the canonical layer, applies its intelligence model, and produces structured outputs — queue items, drafted documents, briefings, or submissions. Agents are built on Claude (Anthropic's API) with structured system prompts per domain. The Town Crier coordinates across agents to prevent alert fatigue.
CHRIS never acts autonomously on anything consequential. Every output lands in a review queue with context, evidence, and a single approval button. The DON's job is review and authorise — not author and compile. Once approved, CHRIS executes: submitting to GPMS, filing with ACQSC, delivering to leaders via iMessage. Every execution is logged and timestamped.
Each agent has a specific domain, a defined cadence, and a set of outputs. Together they watch every dimension of an aged care organisation simultaneously.
Monitors care minutes per shift and day, 24/7 RN coverage, SIRS incident classification, clinical audit schedule, and roster compliance. Triggers alerts when thresholds are breached.
Scans AN-ACC classifications for reclassification opportunities, benchmarks financial performance against StewartBrown data, identifies accommodation pricing optimisation, and surfaces revenue gaps.
Analyses rostering patterns for structural gaps — not individual missed shifts, but repeating patterns that indicate a permanent staffing problem. Surfaces root causes and recommendations.
Triggered by incident events. Drafts SIRS notifications, corrective action plans, board pack entries, and QI submission data. The DON reviews and approves — not authors.
Analyses psychosocial hazard signals from pulse surveys across all 16 ISO 45003 domains. Detects convergence events, identifies turnover precursors, and prescribes evidence-based micro-practices.
Coordinates output across all other agents. When the Sentinel and Steward both flag the same issue, the Town Crier decides what reaches which leader and when. One coordinated signal, not five separate alerts.
Monitors 35 external sources — government, regulators, legal analysis, sector news — every 2 hours. Surfaces regulatory changes, sector developments, and compliance intelligence. Powers The Newsroom.
The distinction between a tool and a platform is this: a tool gives you information. A platform delivers work. CHRIS delivers work — and waits for your approval.
When an event occurs — a fall, a complaint, a SIRS trigger — the Chronicler drafts the required documentation within minutes. SIRS notification, corrective action plan, board pack entry. The DON receives a draft ready for review, not an alert telling them to write one.
Every output lands in a structured review queue with context, evidence, deadline, and a single action button. The DON sees three ranked actions for today — not forty alerts. Each card has everything needed to decide in under 90 seconds.
CHRIS compiles QI data, formats it to the GPMS schema, and submits directly to the ACQSC portal after DON approval. The GPMS reference number is logged automatically. The DON never touches the GPMS portal.
Every leader receives a briefing tailored to their role — the Monday Briefing for the DON, team briefings for team leaders, board packs for the Board. Delivered via iMessage before they walk in the door.
Built on the same cloud infrastructure used by Australia's major health systems. No on-premise hardware. No IT project. Connected to your existing systems within weeks, not months.
Aged care handles some of Australia's most sensitive personal data. CHRIS is designed from the ground up for that environment — not adapted to it after the fact.