Works with what you already run
A plain list of what connects today, what's being built, and what's planned — checked against the code, not the pitch. Where something isn't built yet, this page says so.
blueChart loads a structured case-export JSON file against a strict schema — duplicate keys, non-finite numbers, and malformed input are all rejected outright, not silently coerced.
Import many case files at once with a fingerprint for every file. The whole batch is refused if any file is changed, missing, or extra. Being built; not yet released.
Every product signs its output with Ed25519 and ships a standalone, dependency-light verifier that checks a packet with no server, no database, and no network connection.
The clinical platform exposes a FHIR R4 facade — create, read, update, delete, versioned history, and search — for the Tier 1 resource set, plus a generated CapabilityStatement that describes exactly what's implemented rather than a hand-written claim.
ICD-10-CM, LOINC, SNOMED, RxNorm, HCPCS, and CVX are loaded today. We ship no CPT loader — CPT is AMA-owned content this project has no rights to distribute.
An HL7 v2.5.1 interface engine parses and generates ADT, ORU, ORM/OMG, SIU, and RDE messages over MLLP, with ACK/NACK handling for malformed input.
Tracks an imaging order from ordered through scheduled, acquired, and a signed report, each transition a new, versioned record.
We don't store or view images — a study identifier is treated as an opaque string everywhere in this module. Routing it to an outside viewer is planned.
Not built today. Planned, delivered through an integration partner rather than built in-house.
Sign in through your organization's own identity provider over OpenID Connect — the token is cryptographically verified against your provider's published keys before any session is created. We don't offer a SAML integration.
A step-up sign-in requirement for the decisions that matter most — see Security for the current state.
Not built today.
Not built today.
blueClaims reads a plain JSON claim file today — claim ID, loss date, policy ID, claimed loss categories, and evidence document IDs. A standard claims-exchange file format is planned.
If you don't see something you rely on above, tell us what it is — the product or vendor name, and whatever format it exports today. A person reads every submission.
Thanks — got it
A person on the blueHealthcare team reads every submission and will follow up if there's a fit to talk through.
Read the full security posture → · Have a different question? Contact blueHealthcare →