Oracle Health (Cerner) Integration Services: Ignite APIs and HL7
Cerner integration services connect your product or department to Oracle Health, the EHR formerly known as Cerner, used by many hospitals and health systems across the United States. Taction Software builds Oracle Health integrations using Millennium FHIR R4 APIs, Ignite platform capabilities, SMART on FHIR apps and Millennium HL7 interfaces. Because the Cerner brand is transitioning to Oracle Health, developer programs and access processes continue to change. This page was last reviewed in September 2026. Discuss your Oracle Health integration with our engineers.
Oracle Health and Cerner Integration Surfaces
Oracle Health Millennium offers several integration surfaces, and most products use more than one. Certified FHIR APIs provide standardized data access, SMART on FHIR supports embedded apps, CCL supports customer-controlled data queries, and HL7 v2 interfaces carry real-time clinical events. Choosing correctly depends on your workflows, data needs and customer relationships. Our wider EHR/EMR integration services apply similar approaches across other vendors, so multi-EHR products stay consistent. Each surface is summarized below.
Millennium FHIR R4 APIs
Oracle Health provides certified FHIR R4 APIs for Millennium aligned with US Core and USCDI, covering patients, encounters, conditions, medications, observations and more. They are the standard route to structured data access.
Ignite APIs
Ignite is the name long used for Cerner's API platform, including FHIR endpoints and related services. Search and documentation still use both names, so expect Cerner and Oracle Health references side by side.
SMART on FHIR Apps
SMART on FHIR apps launch inside Millennium with patient and user context, giving clinicians embedded tools. Apps request scoped access through OAuth 2.0, and each customer decides which apps to enable.
CCL and Direct Data Access
Cerner Command Language, or CCL, queries Millennium data for reports and extracts. CCL requires customer-level access and approval, so it suits health system projects rather than independent vendor integrations. Plan approvals early.
Millennium HL7 Interfaces
Millennium supports HL7 v2 interfaces for ADT, orders, results, scheduling and charges. Customer interface teams configure these connections, so HL7 projects always require health system participation and scheduling. Book interface slots early.
Registration, Access and the Oracle Transition
Developer access for Oracle Health starts with registration through its developer program and code console, where vendors create applications, request scopes and test against sandbox environments. Production access still depends on each customer health system. Since Oracle acquired Cerner, branding, documentation locations and program details have changed, and Oracle has announced further EHR platform developments. Always confirm current processes with Oracle Health before committing to timelines, because older guides may no longer match today's requirements.
Code Console Registration
Vendors register applications in the developer code console, define app type, launch method and scopes, and receive client credentials for sandbox testing. This step can begin without a customer relationship.
Sandbox Testing
Sandbox environments provide synthetic data for development and testing. They help validate FHIR calls and SMART launch flows, but production environments differ in configuration, data quality and enabled capabilities. Validate everything later.
Customer Enablement
Each Oracle Health customer decides whether to enable your app in production. Health systems review security, data use and support, then configure access, often coordinated through their own IT governance processes.
Changes From the Oracle Transition
Documentation portals, program names and support channels have shifted as Cerner became Oracle Health. Treat older tutorials cautiously, verify links and requirements, and monitor Oracle announcements for platform changes. Recheck before each rollout.
Date-Stamping Integration Plans
Because vendor programs change, record the date you verified each requirement. Revalidate before customer rollouts, especially when Oracle announces new EHR capabilities, API versions or program terms. Share dates with customers transparently.
Our Oracle Health Integration Services
As a Cerner integration services company, we help digital health vendors and hospitals connect to Oracle Health reliably, across FHIR, SMART and HL7. We build against sandbox environments, then validate in customer environments, where real configurations and data variations appear. Our FHIR integration and HL7 integration teams handle both modern APIs and traditional interfaces, so every workflow uses the approach Millennium supports best. Each of our services is described below in detail.
Cerner Services API Integration
We build FHIR R4 integrations with SMART authorization, backend services, pagination, US Core validation and error handling, designed for Millennium behavior in real customer environments rather than sandbox assumptions. Rate limits are respected.
SMART on FHIR App Development
We build embedded apps with correct launch context, narrow scopes and fast load times, fitting clinician workflows inside Millennium while meeting customer security review and approval requirements. Clinician feedback shapes every release.
Cerner Services HL7 Interface Work
We write specifications, build engine-side channels and test HL7 interfaces with customer teams, covering ADT, orders, results and charges, including identity matching and merge handling. Our Mirth Connect consulting team builds engine channels.
Data Extraction and Middleware
For analytics or cross-system workflows, our healthcare API development team builds middleware that normalizes Oracle Health data for products, warehouses and partner systems securely. Every data flow is audited and fully documented.
Customer Onboarding Support
We prepare security documentation, data flow diagrams and test plans, and support technical calls with customer IT teams, helping each health system approve and activate your integration faster. Each rollout gets faster.
Oracle Health Integration Timeline
Oracle Health integration timelines depend heavily on customer processes, not development effort alone. Registration and sandbox work can move quickly, but production enablement, security review, interface scheduling and change windows add time. The phases below reflect common patterns and are indicative planning ranges, not guarantees. Health systems control their priorities, and major platform changes can affect schedules. Planning customer activities alongside development protects launch dates and sales commitments. Each phase is outlined below.
Discovery and Registration: 2–4 Weeks
Define workflows, data needs and integration surfaces, then register applications in the code console. This phase confirms which activities depend on a customer sponsor and which can start independently. Decisions are documented.
Development and Sandbox Testing: 6–12 Weeks
Build FHIR, SMART or HL7 components and test with sandbox data. Scope, write requirements and workflow count determine duration, while sandbox results still need customer environment validation later. Plan validation time carefully.
Customer Review and Enablement: 4–12 Weeks
Customers review security, data handling and support commitments before enabling production access. Thorough documentation shortens reviews, but timing depends on each organization's governance and IT workload. Start reviews during development.
Customer Testing and Go-Live: 4–10 Weeks
Customer teams configure access or interfaces, test in their environments and schedule go-live during approved change windows. Close monitoring follows activation, with engineers available for stabilization support. Timing follows customer schedules.
Frequently Asked Questions
Is Cerner now called Oracle Health?
Yes. After Oracle acquired Cerner, the business and its EHR products moved to the Oracle Health brand. Many developers and health systems still use the Cerner name, and documentation references both. Millennium remains the core EHR platform for many existing Oracle Health customers across the United States.
What APIs does Oracle Health provide?
Oracle Health provides certified FHIR R4 APIs for Millennium aligned with US Core and USCDI, SMART on FHIR launch capabilities and backend authorization, historically grouped under the Ignite platform name. It also supports HL7 v2 interfaces and customer-controlled data access through CCL for reporting and extracts.
How do developers register for Oracle Health APIs?
Developers register through Oracle Health's developer program and code console, creating an application, selecting launch type and scopes, and receiving credentials for sandbox testing. Production access requires each customer health system to review and enable the app. Check current program details, because processes have changed during the Oracle transition.
Can vendors access Cerner data using CCL?
CCL, or Cerner Command Language, queries Millennium data but requires customer-level access and approval. It typically supports health system reporting and extract projects rather than independent vendor integrations. Vendors usually rely on FHIR APIs or HL7 interfaces, with CCL used only when customers approve specific data extracts.
How long does Oracle Health integration take?
A typical Oracle Health integration takes four to nine months from discovery to production at a customer site. Development often takes six to twelve weeks, while customer security review, enablement, testing and change windows add most remaining time. Later customer rollouts usually move faster once documentation and processes are proven.
Does Oracle Health support HL7 interfaces?
Yes. Oracle Health Millennium supports HL7 v2 interfaces for ADT, orders, results, scheduling, documents and charges. Customer interface teams configure and schedule these connections. Vendors provide specifications, engine channels and testing support, coordinating closely with customer teams through testing and go-live activities.
Ready to Plan Your Oracle Health Integration?
Our integration engineers are ready to help. Free consultation, no obligation.