Skip to content
← AI FEATURES
AI features › Blue

Blue: the setup assistant, for a clinic doing this without an IT department

Blue

A signed, downloadable installer that walks a new clinic through setting up blueHealthcare on its own machine. Setup works fully without AI. An optional AI layer can answer setup questions — off until two people at the clinic turn it on, and it answers only from the manuals bundled with the download. Being built

"Blue" is a working name for this assistant, shared with the AI assistance described elsewhere in blueHealthcare — not yet checked as a trademark. Your clinic can rename it locally, the same as anywhere else Blue appears.

How it works

Download, verify, install — with a person confirming every step.

1 · DOWNLOAD Signed package one file, one signature 2 · VERIFY Checked before it runs a tampered file is refused 3 · INSTALL Deterministic wizard works with no model at all plain-language health checks 4 · OPTIONAL Blue Q&A off until two people turn it on manuals only, never patient data A named person at the clinic confirms every step — install, health check, and any AI answer accepted. Nothing in steps 1–3 calls a model. Step 4 is the only place one can run, and only once turned on.
Deterministic first, AI optional. A clinic that never turns step 4 on loses nothing — the first three steps are the whole of setup.
What it does, and doesn't

Works with AI fully off

The install steps, the plain-language health checks, and the signed confirmation record that setup completed all run with no model anywhere in the path. A clinic can use Blue's setup assistant and never turn on its AI layer at all.

Signed, and checked before it runs

The download is signed. The installer checks that signature first; a package that fails the check is refused before any of its code runs.

A person confirms every step

Each install action is a fixed, named step — never a free-form command. A named administrator confirms it, and that confirmation is what the signed record shows happened.

Runs on the clinic's own machine

Setup happens on hardware the clinic controls. Nothing about the install itself depends on reaching MOBLUEHQ or anyone else over the network.

The optional AI layer
BLUE · SETUP Q&A Being built No patient data

Answers a setup question from the bundled manuals

Off by default. Two people at the clinic have to turn it on before it runs at all. When it's on, it answers a question about the setup itself — never about a patient, since no patient exists yet at this stage — and shows the manual page every answer came from.

Synthetic example walkthrough
Who
Grace Mwangi (synthetic example), the office manager setting up a two-room clinic with no IT staff.
Situation
The wizard reaches a step asking her to choose a backup schedule, and she doesn't know what the options mean.
Blue shows
"Daily backups keep the last 30 days; weekly backups keep the last 12 — see Setup Manual, page 6, 'Choosing a backup schedule.'"
They do
Grace reads the manual page, picks daily, and continues the wizard herself.
What it never does
  • Never runs unless two named people at the clinic have turned it on.
  • Never reads or reasons about patient data — none exists yet at setup.
  • Never replaces a step in the deterministic wizard — it only answers questions about them.
  • Never answers from anything but the manuals bundled with the download; no network call.
Where Blue's setup assistant runs
No fallback here either. If a clinic never turns the AI layer on, setup still completes end to end. If the AI layer is on and becomes unavailable, setup continues without it — the wizard never blocks on a model being reachable.
← BACK TO AI FEATURES OVERVIEW