Client → Source System → Implementation Plan
Riverbend Medical
Oracle Cerner
Riverbend Medical — Oracle Cerner
Client KeyEX-client-riverbend
Plan IDONB-2026-00003
Source System Keysrc-riverbend-cerner
Last UpdatedJun 19, 2026, 02:25 PM UTC
Gap Review Needed
HL7 v2 Interface
FHIR API
Provider / Health System
Risk: Medium
Workflow owner: Alex Morgan (assigned)Test patient: pending
Workflow Completion
65%
Implementation Readiness67
67
Complexity69 · High
8-16 weeks
Source Profile
Last updated Jun 19, 2026, 02:25 PM UTC
Client nameRiverbend Medical
Source systemOracle Cerner
Source owner typeProvider / Health System
Source categoryEhr
EHR / VendorCerner
Current environmentProduction
Available environmentsUAT / Test, Production
Integration patternsHL7 v2 Interface, FHIR API
Primary use caseAdmission / Discharge Tracking
Data controllerProvider / Health System
Current Status
Onboarding section progress
- Overview
- Data Control
- Use Cases
- Requirements
- Source Capabilities
- Gap Analysis
- Summary
Recommended Integration Pattern
HL7 ADT
- HL7 ADT is recommended for event-driven admission/discharge triggers; use event-driven FHIR subscriptions if available.
Recommendation is deterministic and rule-based for the MVP (no AI).