mAIWell

Platform

Platform Overview

The layers of the mAIWell platform, from cloud reasoning down to the appliance.

mAIWell ecosystem architecture. The cloud platform at the top holds the AI engine, protocol library, doctor portal, patient records, insurance integration, healthcare resources and analytics. It exchanges care plans and protocols with the YF1000 host in the centre, which patients, healthcare providers and insurers all reach through. Below the host the Healthcare Bus connects massage, blood pressure, ECG, POCT, ultrasound, camera, temperature and future appliances, each holding only sensors and an MCU.
The platform end to end: cloud above, YF1000 host in the middle, appliances on the Healthcare Bus below. Every appliance is driven by the host and holds no AI, no cloud connection and no decision logic of its own.

Overview

The platform is a vertical stack. Knowledge and planning sit at the top, in the cloud. Execution sits in the middle, on the YF1000 Host. Measurement and actuation sit at the bottom, in appliances.

Each layer talks only to its neighbours. That is what makes the system possible to reason about, audit, and extend.

Why it matters

Most connected-health products put intelligence in the device. Every new capability then means new firmware, a new certification cycle, and a new app.

mAIWell inverts that. Intelligence is centralised, appliances stay simple, and new care behaviour ships as a protocol rather than as firmware.

The layers

  • Cloud Platform — knowledge, care planning, records, provider and payer integration.
  • Knowledge Platform — clinical guidelines and the evidence a plan is built from.
  • Care Planning Engine — turns a patient situation into an Integrated Care Plan.
  • Protocol Library — the executable form of a plan.
  • YF1000 Host — the controller that runs protocols and owns every device.
  • Healthcare Bus — the transport and contract between host and appliances.
  • Healthcare Appliances — sensors and actuators, and nothing more.

Future expansion

The stack is designed so that new appliance classes, new AI providers and new payer integrations attach at a defined layer rather than requiring changes across the whole system.

Next

Architecture