mAIWell

Platform

YF1000 Host

The controller every appliance connects to and every protocol runs on.

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.
Product sheet for the YF1000 Intelligent Healthcare Host: a 10.1-inch tabletop touchscreen unit shown front, rear and side, with port callouts, a specification row, and the healthcare appliances it connects to.
YF1000 Intelligent Healthcare Host — tabletop unit. 10.1" display, front/rear/side views with port detail, and the appliance classes that attach over the Healthcare Bus.
Product sheet for the YF1000 with kiosk base: a 21.5-inch floor-standing unit shown front, side and rear, with rear I/O detail and deployment settings including clinics, pharmacies, corporate wellness and public spaces.
YF1000 with kiosk base — the same host in a floor-standing 21.5" enclosure for clinics, pharmacies and public spaces.

Overview

The YF1000 is the platform controller. It is the only component that talks to appliances, and the only component that executes protocols.

It is a host, not a product category: it is neither a massage device nor a blood pressure monitor. Appliances provide those functions; the YF1000 decides when and how they run.

Responsibilities

  • Device discovery, authentication and driver management
  • The Healthcare Bus
  • Workflow and protocol execution
  • On-device AI runtime
  • Cloud synchronisation and OTA
  • Security and local data storage

Why a host at all

Centralising these responsibilities means an appliance vendor implements a device, not a platform. It also means the security surface, the audit trail and the update path each exist in exactly one place.

This is the same reason an operating system exists: not because applications could not talk to hardware, but because it is far better that they do not.

Future expansion

The host is expected to run on general-purpose edge silicon and to support multiple form factors — home, kiosk and clinical — from one runtime.

Next

Healthcare Bus