Oracle Health (Cerner) integration services for apps, portals, RPM and CRM

We build connections from apps, portals, remote monitoring tools and CRMs to Oracle Health Millennium, the platform many teams still call Cerner, through its FHIR R4 APIs and SMART authorization. Registration happens in Oracle's code Console with a free CernerCare account, and each Oracle Health customer then decides whether to enable your app. We work from Oracle's documentation and sandbox, and the free audit shows you in writing what that documentation supports for your use case.

Referral detail screen in a provider portal with status, contact, procedure codes and approve or reject actions

What does integrating with Oracle Health involve?

Oracle says its Millennium Platform APIs let you use the HL7 FHIR standard in your SMART application. In practice your product calls a FHIR R4 (4.0.1) API over HTTPS, sends and receives JSON, and authorizes with OAuth 2.0 and SMART scopes. Oracle also documents Bulk Data Access APIs for exporting data on groups of patients.

If you have an older integration, check its version first. Oracle's documentation says it no longer supports DSTU 2 FHIR APIs and asks developers to move to R4 as soon as possible.

Server URLs differ by tenant, meaning the customer and environment you are connecting to. Oracle notes that a request to an unknown tenant, or one where your app is not authorized, returns a 403 error. Event feeds inside a hospital may still run on HL7 v2 interfaces that the customer's integration team manages, outside these APIs.

How do registration and the sandbox work?

Oracle requires a free CernerCare account to register applications. You log in to code Console, register the app with its application type and privacy setting, and receive a client ID for use with Oracle's authorization server. Backend apps are registered as System or Confidential and use a system account.

There are two sandboxes. The open sandbox needs no authentication and exposes read-only resources; Oracle recommends it for first proofs of concept. The secure sandbox is for testing with authorization, with a separate URL when a patient or a patient's proxy is the one signing in. Oracle notes that no writes are available in the sandbox without authentication.

We use the open sandbox to check data shapes in the first days, then move to the secure sandbox for sign-in, scopes and writes.

Which kind of Oracle Health app are you building?

Oracle's authorization documentation describes three personas. A provider app signs in a clinician. A patient app signs in a patient or proxy. A system app runs with no user and uses system scopes, such as reading patient records, through a confidential client and system account. Oracle supports SMART v1 and v2 scopes, and some Oracle Health products support the SMART launch feature that passes context into an app.

Patient-facing apps have extra requirements. Oracle lists HTTPS, TLS 1.2 or higher, a valid certificate from a trusted authority, and a DNS TXT record on your domain that carries your client ID. If you skip these, Oracle may describe your app as an Unknown Application to patients during sign-in. Oracle notes that certificate and DNS changes can take up to 12 hours to be recognized, so we set them up early.

What can you read and write, and what needs the customer's approval?

Oracle's R4 API uses GET to read, POST to create and PUT to update. Its scope list includes write scopes for resources such as Observation, Appointment, Condition, Encounter and Patient. Which interactions a given customer supports is listed in that tenant's capability statement, so we check it there for each customer.

Oracle states that once an app is registered, Oracle Health customers may then enable client applications to access their protected resources. That enablement is the approval that decides your go-live, and the customer's IT and security teams run it.

What your app sees can also differ by user. Oracle notes that encounter or organization security, privileges and preferences may filter data, and that a patient persona may see less than provider or system access. We design screens that make sense when data is missing.

What do we need from you to start?

A sponsoring health system or practice that runs Oracle Health Millennium, with a named contact in its IT team. You can build in the sandbox before you have one, but enablement in production comes from that customer.

A CernerCare account in your company's name, or agreement that we create one for you, so the client ID and keys stay with you after the project.

A signed BAA before we touch PHI, the list of features in the first release, and one person on your side who answers the customer's questions.

What drives the timeline and cost of an Oracle Health integration?

We do not publish a price, because the drivers differ by project. The main ones are the number of distinct reads and writes, the personas you need, whether you are moving an older DSTU 2 integration to R4, and how many customers you are rolling out to.

Oracle's documentation links to a separate page on API access and fees for registering an app. Read its current version before you budget; we go through it with you during the audit. Oracle's documentation also mentions a label shown when an app is formally Validated through its Developer Program.

The customer's calendar sets much of the timeline. Its IT team schedules enablement alongside everything else it supports, and its security review will ask about every service that touches the data.

What are the risks, and how do we reduce them?

Building on DSTU 2. It is no longer supported, so any new work targets R4.

Late patient-app setup. A missing DNS record or weak TLS setup can mark your app as unknown to patients, and fixes take hours to be recognized. We set these up in the first sprint.

Assuming the sandbox matches production. Tenants differ in configuration and in which interactions they support, so we read each tenant's capability statement and test with the customer.

Security gaps found late. We sign a BAA before PHI, scope access so each clinician sees only their own patients, and run a penetration test before launch.

How we run a Oracle Health (Cerner) integration

  1. 1

    5-day free technical audit

    We read your product, your data flows and the vendor's current documentation, then list every read and write your features need and the API or interface that serves each one. You get a written report, whether or not you hire us.

  2. 2

    Scope and dated plan

    From the report we agree the scope, the order of work and a plan with dates, including the points where we wait on the vendor or your customer. We sign a BAA before any PHI is in reach.

  3. 3

    Build in the vendor sandbox

    We register the app in code Console, prove the data shapes in the open sandbox, then build sign-in, scopes and writes against the secure sandbox. For any part of Oracle's platform we work from its documentation and sandbox.

  4. 4

    Testing

    We test each persona, token handling and every read and write, then repeat the main flows in the customer's environment once it enables your app.

  5. 5

    Go-live with a penetration test

    Before launch we run a penetration test and fix what it finds, then go live with the customer and watch the first days of real traffic. Access is scoped so each clinician sees only their own patients.

Oracle Health (Cerner) integration questions

1

Is Oracle Health the same as Cerner?

For integration purposes, yes. The Millennium platform documentation sits under Oracle Health, while the developer tooling and sandbox still use Cerner names, such as CernerCare accounts and Cerner Central system accounts. Search for both names when you read the documentation.

2

How do you work on an Oracle Health project?

For any part of a vendor's platform, we work from its documentation and sandbox. On an Oracle Health project that means Oracle's Millennium Platform API documentation, the open and secure sandboxes, and each customer's capability statement. The 5-day audit ends with a written report on what that documentation supports for your use case.

3

Can our app write data into Oracle Health?

Oracle's R4 API supports creating and updating resources, and its scopes include writes for resources such as Observation and Appointment. Whether a given write works for a given customer depends on that tenant's capability statement and on what the customer enables. We confirm each write before building it.

4

Do we still need DSTU 2?

No. Oracle says it no longer supports DSTU 2 FHIR APIs and asks developers to update to R4 as soon as possible. If your product still calls DSTU 2 endpoints, moving to R4 should be the first item on the plan.

5

Can we start before we have a customer?

Yes. A free CernerCare account, code Console registration and the sandboxes are enough to build and test. Going live needs a customer that enables your app for its environment.

6

What does an Oracle Health integration cost?

We do not quote a number without seeing your scope, and Oracle's own fees for registering an app are on a separate page you should read in its current version. Our 5-day free technical audit ends with a written report and an estimate for the build.