Internal draft Not published · Not a live product page · For visual review only

Coming on iCare · Design partners

Build custom certified healthcare apps in days, not months or years.

After go-live, the certified chart is supposed to be finished. It is not. iCare Builder authors new capabilities onto the same ONC-certified iCare clinicians already use — programs, pathways, the work that today waits on a roadmap or lives beside the record. On the chart. Shadow, then UAT, then production. No fork of the core.

Schedule a demo Talk to sales

A design-partner conversation about building on iCare. Not a product you can buy today.

The new work is the chart. The path is Shadow, UAT, then production.

After go-live

The certified chart is live. Then the real work starts.

Go-live puts clinicians in a certified record. Then a program starts that the chart cannot hold. A coordinator needs a home for the day. A specialty pathway needs fields, a template, and something behind them that keeps the work with the patient — not in a spreadsheet, not in a shared drive, not in a tool the chart cannot see.

The usual path is months or years: wait for the roadmap, fork the core, or buy a sidecar. That is how a year of work happens somewhere else, and then has to be typed back in. Clinicians still live in the record. The work still has to be reconciled.

iCare Builder is how custom certified healthcare apps get authored onto iCare in days — on the chart, then shadow, UAT, production. Apps here means chart capabilities on iCare: tabs, templates, and supporting backend. Not a mobile store. Not a sidecar. Not a bolt-on for another EHR.

If that wait is yours, the next step is a conversation.

Talk to sales

What this actually is

On the certified chart. Still being built. In days.

Not another app beside the record. Three things have to be true.

  • On the chart

    These are apps on the chart, not beside it: a tab, a template, the work a clinician already does inside the record. When they open the patient, the program is there — same chrome, same certified EHR.

  • It stays in iCare

    What is authored for this organization stays with this organization. It does not become a fork of the certified core, and it does not live in a tool the chart cannot see.

  • Shadow, then UAT, then production

    Nothing is a first deploy to production. Work is proven in shadow, then in UAT, then promoted. The path is the product as much as the tab. Promotion is a decision, not a hope.

How it works

Author it. Prove it. Promote it.

Builder is an in-iCare capability. It is not a way for anyone to stand up an EHR, and it is not a compiler handed to IT on day one.

  1. Author the app

    We author the chart tab, the templates, and the supporting backend against this organization’s iCare — the work this practice actually runs — not against a copy of the core, and not as a parallel product beside the record.

  2. Prove it in shadow and UAT

    The work runs where it cannot harm production. Shadow first. Then UAT. The people who will use it can see it, break it, and say whether it is the chart they meant before anything is promoted.

  3. Promote to production

    When it is ready, it is promoted. Same iCare. Same ONC-certified EHR. Not a fork. Not a first step into production. Not a raw compiler sitting on the certified core.

A day this exists to remove

A program the chart does not have — without waiting a year.

A practice already on iCare stands up a program the record cannot hold. Grant reporting. A specialty pathway. A coordinator workflow that has to sit with the patient, because that is where the day happens.

IT should not wait a year for a roadmap item. They should not fork the certified core so a tab can exist. They should not buy a sidecar clinicians will never open, then re-key the work every Friday.

That day is a request, a spreadsheet, and a promise to look at it next quarter. Builder is the other path: author the app onto this iCare in days, prove it in shadow and UAT, promote it when it is the chart they meant.

Schedule a demo

Fit

Who it is for. Who it is not.

For

  • Now: iCare’s own builders, authoring custom certified healthcare apps onto the chart.
  • Next: a small set of health-system and practice IT already on iCare, as design partners.
  • Buyers, when it is time: practices and systems that will run iCare, or that are switching to it.

Not for

  • If you are not on iCare, this is not a bolt-on for another EHR.
  • Not a keep-your-current-EHR overlay. Not a kit that sits beside the chart.
  • Not a listing in someone else’s marketplace. Builder authors apps on iCare. It does not customize a system you are not running.

Plain language

What it is. What it is not.

We would rather you hear the limits in the first conversation than discover them in the fifth.

It is

  • An in-iCare capability that authors custom certified healthcare apps onto the chart: tabs, templates, and supporting backend — in days, not months or years.
  • Built on the ONC-certified iCare Enterprise Cloud EHR — the same record clinicians already use.
  • A way to keep that work in iCare, scoped to your organization, and to promote it through shadow, then UAT, then production.
  • Coming first to iCare’s builders, then to a design-partner set of IT already on iCare.

It is not

  • Available to buy today. There is no shop SKU, and this page is not an order form.
  • A fork of the certified core — or a raw compiler on that core, on day one or as the product.
  • A third-party app at the edge of the chart, a mobile store listing, or a first step into production.
  • A way for anyone to stand up an EHR. If you need a certified record, that is iCare. Builder is how we keep building it, in days instead of a year-long roadmap.

Underneath

The certified EHR is the floor. The rest is still being written.

  • ONC-certified iCare EHR

    Every new capability sits on iCare EHR version 2, certified by an ONC-ACB under the ONC Certification Criteria for Health IT. Unique certification number 15.04.04.2617.iCar.02.00.1.200220.

    Certification detail

  • Your iCare, not a shared fork

    What is authored for an organization stays with that organization. Custom work is not a fork shared across the certified core, and it is not a side system with its own patient list.

  • Promotion, not a first deploy

    Shadow, then UAT, then production. The first time a workflow meets live charting is after it has been proven — not because someone compiled onto the certified core and hoped.

Design partners · Coming on iCare

Build the next version of the chart.

If you run iCare, or you are going to, tell us the program living in a spreadsheet. We will walk through how Builder authors it onto the certified chart in days, and the path from shadow to UAT to production. That is the demo. That is the sales conversation.

Schedule a demo Talk to sales

James Riley iCare.com Inc.
14101 NW 4th St., Sunrise, FL 33325