AxisOS OmniCare

Built by Crusan & Co. — OmniCare is the first step toward a universal, sovereign healthcare communication OS.

AxisOS OmniCare is an agentic healthcare and edge-telemetry communication system built on AWS Communication Developer Services (CDS / AWS End User Messaging) and Amazon Simple Email Service (SES), delivering unified, continuous patient and device support across SMS, RCS, WhatsApp, and Email. Powered by Amazon Bedrock AgentCore and orchestrated by the AxisOS Nebula Engine & Sovereign Triad, it provides deterministic, multi-agent healthcare communication at production scale under the Three Pillars of AxisOS: HONEST, AUDITABLE, and OWNED.

Inspiration

Healthcare communication is fragmented. Patients receive SMS reminders from one system, WhatsApp messages from another, and email instructions from a third, with no shared context or memory. Worse, traditional chatbots are trapped in the cloud and cannot interact with physical edge devices. OmniCare was created by Crusan & Co. to solve this fragmentation by providing one intelligent, context-aware system that follows the patient across every channel (conversation_id) while interfacing directly with real-world edge hardware.

What it does

OmniCare delivers a unified healthcare and edge-monitoring assistant across SMS, RCS, WhatsApp (including approved Meta Utility Templates), and Amazon SES Email. It manages:

  • Appointment scheduling and reminders (AppointmentsTentacle)
  • Post-visit follow-up care and device checks (FollowupsTentacle)
  • Medication adherence and prescription refills (MedicationTentacle)
  • Real-time AxisOS Sovereign Triad edge hardware telemetry (AxisOSBridgeTentacle)
  • Intent-driven channel switching (SummaryAgent): When a conversation on SMS or WhatsApp requires a detailed care summary or full diagnostic report, OmniCare automatically switches channels and dispatches the long-form report via Amazon SES Email while confirming delivery on the mobile channel.

How we built it

OmniCare is powered by the AxisOS Nebula Engine and the Sovereign Triad (zero-core :8081, agent-lite :8080, axis-agent :8082, zero-comms :8085). It integrates:

  • AWS CDS / End User Messaging for omnichannel communication (SMS, RCS, WhatsApp Business Platform, and Amazon SES Email)
  • Meta WhatsApp Utility Templates (omnicare_followup_confirm, axisos_telemetry_alert) for structured patient and telemetry notifications
  • Amazon Bedrock AgentCore (CareAgent, AxisAgent, SummaryAgent, SupportAgent, SetupAgent) for reasoning and workflow autonomy
  • AxisOS Tentacles for deterministic, auditable channel and hardware tool-use
  • Sovereign Triad Heartbeat Registry ([💃🍪🕺]) for multi-agent coordination and RAMGAK-bracketed memory telemetry
  • FastAPI Ingestion Layer (/webhook/sms, /webhook/rcs, /webhook/whatsapp, /webhook/email) for unified CDS webhook normalization

This architecture allows a single conversation (conversation_id) to start in SMS, continue in WhatsApp, escalate a full report to Email, and execute an edge checkpoint without ever losing context.

Challenges we ran into

Building true omnichannel continuity required solving:

  • Synchronized state across four communication channels (SMS, RCS, WhatsApp, and SES Email) under one deterministic conversation_id
  • Low-latency routing between AWS CDS services, Bedrock AgentCore, and freestanding C99 AxisOS edge agents (~112 µs reflex loop)
  • Consistent agent memory and audit trails across cloud and edge workflows
  • Ergonomic differences between short-form mobile messaging (SMS/WhatsApp) and long-form clinical/diagnostic reporting (SES Email)
  • Bedrock AgentCore multi-agent orchestration inside the AxisOS Nebula Engine

Each challenge pushed improvements into the OS and strengthened reliability.

Accomplishments that we're proud of

We built a functioning, production-grade agentic healthcare and edge communication system. OmniCare can:

  • Manage patient and operator conversations across SMS, RCS, WhatsApp, and Email
  • Maintain one continuous conversation_id and state ledger across channel switches
  • Execute autonomous multi-step workflows and verified hardware edge actions
  • Deliver real healthcare and telemetry value with zero hallucinated status strings
  • Run across AWS CDS + Amazon Bedrock AgentCore + AxisOS Sovereign Triad

Our biggest accomplishment was leveraging AxisOS and the Sovereign Triad heartbeat system to create a future-ready communication model: three tiny, cooperating agents managing data, telemetry, and communication with unprecedented speed (112 µs in DDR4 RAM) and efficiency.

OmniCare & AxisOS support multiple resilient communication methods, including:

  • Local paging via a Pi-based RF link
  • Encrypted patient-held data replicated via DNS TXT fields
  • Two-way SMS, RCS, WhatsApp Templates, and SMTP/SES
  • Serverless cloud execution (87 KB compressed container)
  • Diskless 100% DDR4 RAM hardware execution (0.00% flash wear)

Live Sovereign Triad Outpost (Freestanding C99, zero-libc, FROM-scratch, 87 KB): https://axisos-sovereign-triad-4zye7tn3qq-uw.a.run.app

AxisOS Fleet Deck & Console Integration: https://axisos.pro/console/

GitHub Repository (Full Source, 4-Stage Simulator & Test Suite): https://github.com/mcrusan/AxisOS-OmniCare

This is not a mockup; it is an auditable, production-grade architecture.

What we learned

We learned that omnichannel communication requires more than APIs — it requires an operating system for agents. We learned how to combine AWS CDS with Amazon Bedrock AgentCore, how to maintain deterministic workflows across channel switches, and how unified cloud-to-edge communication dramatically improves both patient care and operator situational awareness.

What's next for AxisOS OmniCare

Next steps include:

  • HL7 / FHIR EHR integration
  • Automated appointment scheduling with calendar sync
  • Closed-loop medication adherence workflows with edge sensor verification
  • Multilingual patient support across WhatsApp and RCS
  • AWS End User Messaging Voice channel integration
  • Clinician & operator dashboard for real-time multi-agent oversight

Built With

Share this project:

Updates

Submission history