Skip to content
← MANUALS
Manual

blueHealthcare launcher & platform

The launcher is the single window a clinic or reviewer opens: one login, a product switcher, and a reverse proxy in front of each entitled product — never a separate URL or install per product.

What this is and is not

The launcher itself makes no clinical or claims decisions. It authenticates a named user, decides which products that install is entitled to run (via a signed, offline-verifiable entitlement file), and proxies requests to each product's own process. Every product keeps its own database, its own tests, and its own decision boundary — the launcher depends on the products; no product depends on the launcher.

Who uses it

An operator (installs and licenses the suite for a site) and named end users with roles — reviewers, adjusters, lab staff — each seeing only the products their entitlement and role permit.

Getting started — demo only

See the hosted demo to try the launcher and switcher today — no install, no local checkout. A local demo mints a demo entitlement for all 8 products and starts the launcher the same way; it will run from the source once the source itself is downloadable, and there is nothing to run it against yet.

The platform — screens

The blueHealthcare platform is the collection of clinical modules you access through the launcher. Each module runs as its own process and keeps its own database; the launcher proxies requests and enforces entitlement rules. Below are the major screens you interact with when a product is open.

The Library screen: product tiles for the entitled products, each with a health indicator and an Open button, a button revealing the lab modules, and a Reason for access selector in the top bar.
Synthetic demo data
Library — the products this install is entitled to, each with its own health indicator. The Reason for access selector in the top bar must be set before any record opens; until it is, a product's panels show access-denied instead of chart data.
A patient chart: the four-area navigation rail on the left, a patient banner showing location, care team and coverage, allergy chips, and the chart review pane with the problem list, encounters and a progress note.
Synthetic demo data
Patient chart — the four-area rail (Front desk, Chart, Orders & results, Office) with Tasks pinned above it, and the patient banner: bed, care team, isolation and coverage. Coverage here reads "Restricted for your role", because this signed-in user is a physician and coverage is not theirs to see.
The Schedule screen: a provider and resource grid for one day, with time rows, columns per provider or room, and slots marked busy.
Synthetic demo data
Schedule — the clinic's daily appointment roster, showing which slots are booked and who is scheduled for each time.
Screen-by-screen walkthrough
Library / switcher — the one screen the shell renders, listing every entitled product Opening a product — a full-page navigation to that product's own UI, not an iframe Audit log — the append-only, hash-chained record of every access
What a receipt proves
The launcher's own audit log is hash-chained and checkpointed daily with a signature, so tampering with history is detectable. This proves what happened in the log — it does not itself certify any clinical or claims outcome; that boundary belongs to each product's own signed receipt.
Known gaps, stated plainly
  • The suite composes 13 planned modules; several are still design-only or early build. This manual and the product list on this site describe only what exists in code today.
  • No production deployment exists yet — everything above describes the local demo.
FAQ
Does the launcher replace our EHR?

The launcher itself, no — it is just the shared window and switcher that composes the suite's products; it runs alongside whatever record system you already have. But the question is usually really about the underlying blueHealthcare platform the launcher opens: for a clinic that already runs an EHR, the platform and the eight assurance products (blueChart, blueClaims, and the rest) are overlays that never replace it. For a clinic with no EHR today, the platform itself is the record system — registration, scheduling, notes, orders, results, medications, and imaging. See the platform page for which mode applies to you.

Does opening a product in the launcher change who is responsible for the decision?

No. A named human remains the only decision authority for every product in the suite, regardless of how it's launched.