All EHR integrations
Native FHIR + write-back

Oracle Health (Cerner Millennium) integration

MedScrub integrates with Oracle Health (formerly Cerner Millennium) using FHIR R4 endpoints registered through the Oracle Health developer program. Patient records flow into the MedScrub clinical data repository, and reviewed clinical content writes back to the Oracle Health chart as a FHIR DocumentReference.

Oracle Health developer program
Oracle Health Developer Documentation

Integration model

How Oracle Health and MedScrub connect

OAuth 2.0 with Oracle Health’s authorization server. MedScrub configures the FHIR base URL per tenant and uses Oracle-issued client credentials. PHI flows into the customer-hosted proxy and is de-identified before any request reaches a large language model.

Capabilities

What MedScrub does with Oracle Health

Pre-visit planning

MedScrub pulls the patient record from the EHR before the appointment and surfaces care gaps, screening recommendations, and overdue chronic-disease milestones for the loaded patient.

SOAP note generation with write-back

Drafts a structured SOAP note from the patient chart, with ICD-10 coding and E/M level analysis. After physician review and sign-off, the note writes back to the EHR as a FHIR DocumentReference.

Population screening gap analysis

Runs HEDIS / USPSTF / MIPS quality-measure gap analysis across patient panels — breast, cervical, colorectal, diabetes, blood pressure, and depression screening.

Daily Briefing across the schedule

Batch pre-visit intelligence for the full clinic day, run overnight against the CDR, with delivery to mobile.

HEDIS season medical-record review

Automates payer chart-request response by searching the longitudinal record for measure-specific evidence.

Prior authorization drafting and appeals

Drafts prior-auth requests and denial appeals grounded in the patient chart, including evidence pulled from prior diagnostic reports and procedures.

CCM documentation

Monthly chronic care management documentation for CPT 99490 / 99491 billing, generated from the longitudinal record.

Coding optimization

2021-AMA MDM framework analysis flags under-coding opportunities with revenue-at-risk surfaced in the UI.

Data scope

FHIR R4 resources retrieved

  • Patient
  • Condition
  • MedicationRequest
  • Observation
  • AllergyIntolerance
  • Procedure
  • DiagnosticReport
  • DocumentReference
  • Encounter
  • Immunization
  • CarePlan
  • FamilyMemberHistory

Setup

How a Oracle Health customer onboards

01

App registration on the Oracle Health developer program

Register MedScrub on the Oracle Health developer portal and obtain client credentials for the customer tenant.

02

Configuration

Customer IT provides the FHIR base URL and configures MedScrub’s ORACLE_FHIR_BASE_URL environment variable along with the issued OAuth credentials.

03

Scope approval

Required FHIR R4 read scopes plus DocumentReference write scopes are approved by Oracle Health for the production tenant.

Ready to connect Oracle Health?

MedScrub onboards Oracle Health customers sales-led, with deployment engineering, EHR registration, and compliance review running in parallel. Most deployments are live in four to eight weeks.