mAIWell

Platform

Architecture

Five principles that decide where behaviour is allowed to live.

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 architecture is defined more by what is forbidden than by what is provided. Five principles decide where any given behaviour is allowed to live, and every design question is resolved against them.

Why it matters

Platforms rot when capability leaks into the edge. One appliance ships a little logic, another ships a little more, and eventually the platform is a thin wrapper over incompatible devices.

Stating the boundary as a principle — rather than as a convention — is what keeps that from happening as the number of partners grows.

Consequences

Because applications never speak to appliances directly, every interaction with a device is mediated, logged and attributable. That is the property regulators, hospitals and insurers care about, and it is a consequence of the architecture rather than a feature bolted on later.

The five principles

  1. Principle 1

    Centralised intelligence, distributed appliances

    Reasoning lives in one place. Everything at the edge is a sensor or an actuator.

  2. Principle 2

    Every appliance is controlled by the YF1000 Host

    An appliance has one upstream relationship, and it is always the host.

  3. Principle 3

    Appliances never make medical decisions

    A device measures or acts. What it means, and what follows, is decided above it.

  4. Principle 4

    The cloud creates protocols; the YF1000 executes them

    Authoring and execution are separate concerns, so care can change without firmware changing.

  5. Principle 5

    Applications never talk directly to appliances

    All traffic goes through the host, which is what makes the platform auditable.

Next

YF1000 Host