Cerner PowerChart Integration: SMART Launch or MPages

Updated October 31, 2026. Oracle pages read the same day.

Cerner PowerChart integration means putting your product inside the clinician's chart, and there are two common ways to do it: a SMART on FHIR app launched from PowerChart, or an MPage built on Oracle's MPages platform. For a product sold to several hospitals, start with SMART, because it follows a published standard and you host it yourself. Part of the setup sits behind a customer sign-in, so some answers have to come from the hospital.

This guide is for product leaders whose buyers keep saying "it has to be in PowerChart". It sets out what Oracle's public pages confirm, what they do not, and what to ask a hospital before you promise a date. Our Oracle Health integration services page covers the delivery work, and the Cerner API integration guide compares every route.

Why buyers ask for PowerChart, and what they usually mean

Buyers ask for PowerChart because clinicians will not leave the chart mid-visit to open another product. Before you scope anything, find out which of three things the buyer means, because they lead to different work. They may want your screen opened from a chart menu. They may want your data shown beside the chart's own data. Or they may want your results written into the record, which needs no PowerChart screen at all and may be a FHIR write or an HL7 feed.

PowerChart itself is also a very broad search term. Most people searching it are looking for the product or a login, and this guide is for people building on it.

Is this your use case?

Most PowerChart requests fall into one of these. Each one leads to different work and different people.

SMART on FHIR or MPages: how they differ

A SMART app is your own web app, opened from the chart and authorized through OAuth. An MPage is a web view of Millennium data built on Oracle's own platform. Oracle's licensed product list says the MPages Development Kit lets customers "customize the display of Cerner data", with a Runtime License that displays MPages developed by Cerner.

That flowchart is our judgment. Oracle publishes no such rule, and we did not find public terms for a third party building and shipping MPages. Treat the MPages route as a question for the hospital and Oracle.

How a SMART launch from PowerChart works

When a clinician opens your app, the launch sends your app a launch value and the FHIR base URL. Your app reads that tenant's configuration, asks for authorization and gets a short-lived token with the patient in context. These parts are public, and they are the same whichever access point the hospital picks.

On 31 October 2026, Oracle's secure sandbox SMART configuration advertised launch-ehr, public and confidential clients, and S256 for PKCE. A hospital's tenant may advertise something different, which is why Oracle tells developers to discover these values and not hard-code them.

The scopes launch, launch/patient and launch/encounter are defined in Oracle's framework document. A default token lasts 570 seconds. With online_access, your app can refresh while the user stays signed in, and the server may send an active_ttl value that tells your app when a session counts as inactive. Design any long screen around that: keep the draft on the client, and tell the user when they have to sign in again.

What the launch request looks like

This shape comes from Oracle's Authorization Framework, with values replaced by placeholders. Oracle's example uses an older FHIR path and a patient persona. We show a provider persona, as the sandbox SMART configuration advertises it. Your app should read the real endpoint from the tenant's configuration.

GET https://authorization.cerner.com/tenants/{tenant}/protocols/oauth2/profiles/smart-v1/personas/provider/authorize
  ?client_id={your client ID}
  &response_type=code
  &redirect_uri={your registered URI}
  &scope=user/Observation.read launch online_access
  &launch={launch value from the chart}
  &aud={this tenant's FHIR base URL}
  &state={random value}

Oracle says it generally rejects requests without the audience parameter, does not support wildcard scopes, and that the scopes returned may differ from the scopes requested. So your app has to check what it received. A clinician who lost a permission should see a clear message, and a blank panel is the failure to avoid.

Where the app can open, and what is not public

Oracle's own public statements confirm less here than vendors often imply. Its provisioning guide says the customer completes the SMART setup and points to a page titled "Configure SMART Applications to Run in PowerChart or FirstNet". That page sits on a Cerner wiki which returned 403 to us on 31 October 2026.

In Oracle's developer forum, in January 2024, an Oracle staff member wrote that SMART "uses the discern framework, but it requires configuration that it not available everywhere", that revenue cycle supports SMART launches, and that "MPages has some further restrictions on how it can launch SMART apps". The answer points to client-only help pages for the details, so we cannot state those restrictions. That post is nearly three years old, so ask for the current position.

When HL7 is the real answer to "in PowerChart"

If the buyer only needs your data visible in the chart, you may not need a screen at all. HL7 interfaces connect to Millennium, and PowerChart shows what Millennium stores, so a result filed through an interface can be available for viewing there. Our Cerner HL7 and Mirth Connect guide sets out which feeds carry patient data, orders, results and documents.

What to build differently for an embedded browser

Test your app in the client the hospital really uses, because a normal browser test will not catch embedding problems. Oracle's SMART tutorial includes a note about preventing "session bleed caused by single threaded embedded browser and sessionStorage API", and it provides an embeddable library for MPages views. The tutorial carries its own notice that it is being updated, so treat it as a pointer to the problem and check the current library.

Two provisioning details also affect design. Where a hospital hosts through Citrix, Oracle's guide says external website dependencies must be added to the trusted sites, so keep a short, known list of the domains your app calls. And because the launch happens per hospital, keep each hospital's configuration out of your code.

Questions to ask the hospital before you promise a date

These six answers decide most of the plan, and only the hospital holds them. Ask them on the first technical call.

1. Which Millennium hosting type do you use, and are you a shared domain customer on CommunityWorks, PowerWorks or Continuum?
2. Which access points does your team allow for third-party apps: chart level, organizer level, or a specific MPage?
3. Which browser engine does your PowerChart use today, and which version of MPages do you run?
4. Do you allow external sites through Citrix, and who approves them?
5. Do you hold an MPages license that covers this view, and who supports it after go-live?
6. Who files the service requests with Oracle, and what does your queue look like?

What breaks after go-live, as the documents describe it

The first three rows are in Oracle's or Cerner's documents. The last column is our advice.

What to ask before you sign

A buyer asking for PowerChart may be asking for one specific screen, so agree that in writing. Our reading is that these points belong in the scope, since Oracle's public pages do not settle them.

What Nirmitee has shown here, and what it has not

We have a public recording of a SMART app against the Oracle Health and Epic developer sandboxes, with discovery, PKCE, chart reads and a vital-sign write that read back. Watch the run. It runs in the developer sandbox with test patients.

It does not show a launch inside a hospital's PowerChart, and we have no public demonstration of an MPage. For that work we start with the questions above, and we say so in the scope. If you have a hospital asking for PowerChart now, book a PowerChart scoping call, or read about our SMART on FHIR app development.

Sources

All read 31 October 2026.

• Oracle, FHIR Application Provisioning (dated July 2024)
• Oracle, Authorization Framework
• Oracle sandbox SMART configuration
• Oracle developer forum, "Available SMART on FHIR access points" (Oracle staff replies, January 2024)
• Cerner SMART on FHIR tutorial (marked as being updated)
• Oracle Health Licensed Software Solution Descriptions (updated 8 July 2026)
• Oracle accessibility report for MPages 9.2 (dated 11 February 2025)

Oracle Health, Cerner, Millennium, PowerChart and MPages are trademarks of Oracle and/or its affiliates. Nirmitee is an independent company, and this guide is not endorsed by Oracle.