01
Connect
Bring together observations, symptoms, device status, pathway schedules, staff actions and hospital context.
- Patient and caregiver app
- Connected and manual observations
- Hospital and staff workflow events
Technology platform
How the distributed hospital works.
Rātana connects observations from patients, devices, apps, staff workflows and hospital systems; converts them into live patient state; and routes the right work to the right team with full auditability.
Current release · 5,000 active monitored patients · 100% virtual-bed occupancy
Connect
Bring together observations, symptoms, device status, pathway schedules, staff actions and hospital context.
thenUnderstand
Turn raw events into a live patient state with trends, freshness, pathway context and visible reasons.
thenCoordinate
Route accountable work to clinical, operational, home-visiting, device and escalation teams.
thenGovern
Make important access, state changes, decisions, overrides and handovers attributable and reviewable.
Architecture
Four layers, one operating picture.
The platform does not simply collect remote-monitoring data. It turns events from the home and hospital into prioritised, explainable and accountable clinical work.
02
Understand
Turn raw events into a live patient state with trends, freshness, pathway context and visible reasons.
- Patient state and baseline
- Trend and deterioration priority
- Missing-data and device-quality risk
03
Coordinate
Route accountable work to clinical, operational, home-visiting, device and escalation teams.
- Prioritised clinical queues
- Named owner and due time
- Escalation, handover and discharge
04
Govern
Make important access, state changes, decisions, overrides and handovers attributable and reviewable.
- Role and care-context access
- Policy and pathway versions
- Complete action history
Inside each layer
How the operating picture is built.
Each layer has a distinct job, a defined input and a useful output. Together they turn distributed events into controlled clinical operations.
LAYER 01
Connect
Secure app entry, device and vendor events, staff capture, and FHIR-shaped interfaces bring data into one event stream. Every event keeps its patient, source, timestamp, quality and episode context.
- Takes in
- Vitals · symptoms · device state · tasks · hospital context
- Produces
- Validated, attributable events
LAYER 02
Understand
The state engine compares each event with the patient's baseline, recent trend, pathway rules, expected schedule and device quality. It separates physiological concern from stale, missing or unreliable data.
- Takes in
- Validated events · baseline · pathway rules · prior state
- Produces
- Current state, priority and reasons
LAYER 03
Coordinate
Workflow rules turn patient state into a specific action, destination queue and response time. Work carries an owner, due time, acknowledgement, escalation path and disposition until a clinician records the outcome.
- Takes in
- State · urgency · pathway · team coverage · open work
- Produces
- Owned task, timer and escalation path
LAYER 04
Govern
Identity, role, organisation, region, team and patient relationship determine access. The platform records sensitive reads, state changes, score versions, acknowledgements, decisions, overrides, handovers and exports.
- Takes in
- Identity · role · care context · policy · action history
- Produces
- Controlled access and reviewable evidence
Signal to action
A home observation is only useful if it becomes work.
Abnormal physiology, missing observations and device failure are handled differently because they require different responses.
- 01
Observe
A reading, symptom, task or hospital event arrives.
- 02
Validate
Identity, time, source and signal quality are checked.
- 03
State
Acuity, freshness, device status and pathway progress update.
- 04
Prioritise
Rules produce a work priority with visible reasons.
- 05
Queue
The right team receives an owner, timer and next action.
- 06
Act
A clinician reviews, responds, escalates or hands over.
- 07
Audit
The decision, reasoning and outcome are recorded.
Patient state
The journey, not an isolated reading.
Each active episode combines observations, trends, pathway expectations, symptoms, device reliability, care ownership, open work, escalation context and discharge readiness.
StableClinical reviewRapid responseNo dataDevice concernLikely dischargeTransfer in progress
ACTIVE EPISODE
Patient state
- Pathway
- Respiratory
- Latest state
- Clinical review
- Data freshness
- 4 minutes
- Owner
- Respiratory team
- Open work
- Review within 20 min
- Device quality
- Signal verified
Explainable priority
Rising respiratory rate, falling oxygen saturation and increased breathlessness since the last review.
Clinical analytics
Explainable analytics, not autonomous medicine.
Thresholds, trend changes, diagnosis-specific rules, missing-data risk and device quality create a transparent work priority. Clinicians remain responsible for decisions and escalation.
Show why a priority changed
Separate clinical and signal-quality risk
Keep clinicians in control
Record overrides and reasoning
Connected care
Tolerant of messy home data.
Home devices lose signal, batteries run low and observations are missed. Rātana treats signal quality and missing data as patient-safety conditions, never as reassurance.
Connected
Low battery
Poor signal
Stale data
Missing observation
Suspected faulty reading
Interoperability
FHIR-shaped by design.
A mock integration facade lets hospital teams evaluate workflows and data contracts before production hospital-record integration begins.
PatientEncounterObservationCarePlanTaskDeviceDocumentReferenceProvenanceAuditEvent
Production patterns may include FHIR R4, SMART on FHIR, AU Core, US Core and local terminology mapping. Any writeback requires governance and integration sign-off.
Access and accountability
Designed around least privilege.
A distributed hospital needs carefully bounded access for patients, caregivers, clinical teams, operations, device support and emergency handover users.
Access follows role and care context
Proxy access is explicit and approved
Emergency access is time-bound
Sensitive actions are attributable
Current and future state
A working model today. Production assurance next.
The current platform validates the operating model at network scale. Clinical deployment would add formal validation, governed integrations and service assurance.
| Area | Current release | Production requirement |
|---|---|---|
| Data | Generated patient and event data | Governed patient data, consent, retention and local privacy compliance |
| Devices | Simulated feeds and interface events | Validated fleet, provisioning, maintenance and clinical engineering controls |
| Hospital record | FHIR-shaped integration facade | Signed-off interfaces, monitoring and governed writeback |
| Prioritisation | Configurable rules and prototype scoring | Clinical validation, safety case and ongoing performance review |
| Access | Seeded roles and simulated onboarding | Identity integration, least-privilege policy and formal access review |
| Operations | Cloud-backed demonstration release | Resilience, security, support, monitoring and service commitments |
See the platform operating at network scale.
Follow a patient signal from home observation through prioritisation, clinical review, escalation, handover and governance.
Take it for a run