Static stakeholder demo home
The recommended starting point for viewing the static Aetheris demo package: what Aetheris is, which page to open first, and how the older supporting pages fit together.
Short explanation
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.
Aetheris links readiness channels without collapsing clinical, operational, and administrative responsibility into one generic status.
Recommended route
This home page is the professional entry point for the static Aetheris demo package. Use it as a viewing guide before opening the individual static pages.
Purpose: best current product story; explains role views, hybrid workflows, readiness channels, ownership, handoffs, audit/quality learning, and inactive AI boundary.
Purpose: explains the next-day OT readiness huddle idea.
Purpose: older/supporting static review materials showing earlier huddle board ideas.
Purpose: supporting summary materials; not the primary product story.
Static package pages
Every page in this package is synthetic, static, non-production, and not for clinical use. The broader prototype shell is the best current product-story page.
Recommended path: for most viewers, start with the broader synthetic prototype shell, then return here for older/supporting huddle materials.
Depicts: the current broader product story across role views, hybrid workflows, readiness channels, handoffs, audit/quality learning, and inactive AI boundary.
Use when: a stakeholder wants the clearest current view of the intended Aetheris story.
Boundary: static synthetic review page only; no backend, storage, API, integration, or AI service.
Open broader synthetic prototype shellDepicts: the next-day OT readiness huddle concept and why shared readiness visibility matters.
Use when: a viewer wants the huddle concept before looking at older board mockups.
Boundary: static synthetic review page only; not for clinical use or validation claims.
View huddle overviewDepicts: an older/supporting visual mockup for huddle board review.
Use when: reviewing earlier huddle board planning and visual layout ideas.
Boundary: older supporting static material; no real patient or hospital data.
Open static huddle mockupDepicts: an older/supporting display-only demonstrator with synthetic A/B-style cards.
Use when: comparing earlier huddle board display ideas, not as the main product story.
Boundary: frontend-only static review material; no inputs, data service, or runtime behavior.
Open frontend-only demonstratorDepicts: supporting static dashboard/review material.
Use when: a viewer needs a compact supporting summary rather than the primary product story.
Boundary: supporting static review page only; no production-readiness or ROI claims.
View dashboardDepicts: supporting static slide-style review material.
Use when: a viewer needs presentation-style summary material after seeing the main prototype shell.
Boundary: supporting static review material only; no compliance, accreditation, safety, or cybersecurity claims.
View deckOlder/supporting materials
Some pages were created earlier as planning and review steps, so they may show narrower huddle-focused concepts. They are not wrong; they are supporting materials. The broader synthetic prototype shell is the best current product-story page.
Problem statement
Surgical cases may appear scheduled while readiness channels remain incomplete.
Surgeons, anaesthesia, OT, pre-op, stores, billing/admin, and quality teams need shared visibility.
Postponements, missing information, blockers, and handoffs are difficult to track without structured evidence.
Current POC
Under the hood
Patient, encounter, facility, location, role, request, product, and questionnaire context are represented with synthetic CARE-like data.
Aetheris owns the perioperative surgical case workflow and case-specific readiness coordination.
Anaesthesia, checklist, inventory, admin, OT operations, and AI review are visible as separate but linked channels.
AI may support draft summaries or missing-item prompts, but only as reviewable draft assistance.
Authorized hospital roles retain clinical and operational responsibility for decisions and sign-offs.
Workflow events, role ownership, timestamps, source labels, and review states support quality and leadership review.
Workflow stages
Role responsibility
Posts the case and reviews surgical summary drafts.
Records anaesthesia readiness and reviews anaesthesia drafts.
Reviews completeness, coordinates slots, and confirms OT readiness.
Completes checklist items and escalates preparation blockers.
Confirms equipment, consumables, substitutes, and item blockers.
Shows basic admin or insurance visibility without full billing scope.
Reviews evidence, role ownership, timestamps, and status changes.
Needs readiness, delay, postponement, throughput, and quality visibility.
Open Health Network / CARE status
The current POC has no live CARE or Open Health Network runtime integration. It does not call CARE APIs or connect to production systems.
Responsibility split
| 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 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.
Share stakeholder feedbackFeedback
The package links above explain what each static page depicts and when to use it. Please review the broader synthetic prototype shell first when forming stakeholder feedback.
Boundaries