Non-production POC Synthetic demo data only Not for clinical use

Stakeholder explainer

Aetheris Perioperative Intelligence

A clean, non-production overview of the Aetheris perioperative workflow companion layer for hospital stakeholders.

Non-production POC Synthetic demo data only Not for clinical use

Short explanation

What Aetheris is

Aetheris is a perioperative workflow companion layer. It does not replace HIS, EMR, or CARE. It helps structure surgical case readiness, OT coordination, anaesthesia review, pre-op checklist, inventory and admin visibility, AI draft review, and audit evidence.

Core idea

Aetheris links readiness channels without collapsing clinical, operational, and administrative responsibility into one generic status.

Problem statement

Why this POC exists

01

Scheduled is not always ready

Surgical cases may appear scheduled while readiness channels remain incomplete.

02

Teams work in silos

Surgeons, anaesthesia, OT, pre-op, stores, billing/admin, and quality teams need shared visibility.

03

Delays are hard to trace

Postponements, missing information, blockers, and handoffs are difficult to track without structured evidence.

Current POC

What the current POC demonstrates

Complete journey Blocker journey Postponed journey Read-only dashboard Synthetic data only

Under the hood

How the workflow is staged

1

Mock HIS/CARE context

Patient, encounter, facility, location, role, request, product, and questionnaire context are represented with synthetic CARE-like data.

2

Aetheris workflow layer

Aetheris owns the perioperative surgical case workflow and case-specific readiness coordination.

3

Readiness channels

Anaesthesia, checklist, inventory, admin, OT operations, and AI review are visible as separate but linked channels.

4

AI draft assistance

AI may support draft summaries or missing-item prompts, but only as reviewable draft assistance.

5

Human review and sign-off

Authorized hospital roles retain clinical and operational responsibility for decisions and sign-offs.

6

Audit evidence and reporting

Workflow events, role ownership, timestamps, source labels, and review states support quality and leadership review.

Workflow stages

Perioperative journey visualisation

  1. Case posted
  2. OT review
  3. Provisional scheduling
  4. Anaesthesia readiness
  5. Pre-op checklist
  6. Inventory/admin visibility
  7. Final OT confirmation
  8. Surgery/recovery handoff
  9. Post-op closure
  10. Audit review

Role responsibility

Who needs visibility

Surgeon

Posts the case and reviews surgical summary drafts.

Anaesthetist

Records anaesthesia readiness and reviews anaesthesia drafts.

OT manager

Reviews completeness, coordinates slots, and confirms OT readiness.

Pre-op nurse

Completes checklist items and escalates preparation blockers.

Stores/inventory

Confirms equipment, consumables, substitutes, and item blockers.

Billing/admin

Shows basic admin or insurance visibility without full billing scope.

Quality/audit

Reviews evidence, role ownership, timestamps, and status changes.

Hospital leadership

Needs readiness, delay, postponement, throughput, and quality visibility.

Open Health Network / CARE status

Current integration boundary

No live CARE runtime integration

The current POC has no live CARE or Open Health Network runtime integration. It does not call CARE APIs or connect to production systems.

  • Schema-only/API documentation review has been performed.
  • Mock CARE-like synthetic context is used for patient, encounter, facility, location, user/role, service request, product, and questionnaire context.
  • CARE runtime behavior has not been validated.
  • Future integration may use CARE/Open Health Network APIs for hospital context if runtime testing confirms suitability.
  • Aetheris-owned perioperative workflow objects remain separate from CARE context.

Responsibility split

What belongs where

Layer May provide or own Boundary
HIS / CARE / Open Health Network Patient, encounter, facility, location, user/role, and core hospital context. Current POC uses mock context only. Runtime behavior is not validated.
Aetheris Surgical case workflow, readiness channels, OT coordination, AI draft review, and audit evidence. Aetheris-owned objects remain separate from CARE context.
AI Draft assistance for summaries, prompts, handoffs, and audit evidence preparation. Draft-only. No autonomous clinical or operational decisions.
Human hospital roles Clinical and operational responsibility, review, sign-off, escalation, and final action. Surgeons, anaesthetists, nurses, OT managers, and authorized teams retain responsibility.

Recommendations

Share feedback / recommendations

Share workflow-level feedback using the stakeholder feedback form. Please do not enter patient information, credentials, confidential hospital data, production URLs, passwords, API keys, or sensitive operational details.

Feedback areas covered by the form

  • Does this reflect your OT workflow?
  • Which readiness channels are missing?
  • Which role owns each sign-off?
  • What are common causes of delay/postponement?
  • What reports would leadership need?
  • Which data should come from HIS/CARE and which should belong to Aetheris?
  • Which AI draft use cases are acceptable or unsafe?

Static package pages

Open the packaged stakeholder demo

The dashboard and deck are packaged here as static, non-production review materials using synthetic demo data only.

View dashboard View deck

Boundaries

What must not be claimed

Not production ready Not clinically validated Not live CARE/Open Health Network integration Not real patient data Not real authentication/authorization Not a full HIS/billing/pharmacy/LIMS/RIS/PACS system AI does not make clinical decisions