Cerner DSTU2 to FHIR R4 Migration: What Changes, How to Plan
Cerner DSTU2 to FHIR R4 Migration: What Changes, How to Plan - Mindbowser
Summary
Due to Oracle Health ending DSTU2 support in December 2025, migration to FHIR R4 is mandatory. Developers must address technical changes including API updates, resource name revisions, and the mandatory implementation of OAuth 2.0.
Details
This article details the technical changes and planning required for migrating from Cerner's DSTU2 to FHIR R4. Since Oracle Health ended DSTU2 support for its Millennium FHIR APIs in December 2025, R4 is now mandatory for all related APIs. Specific changes include the renaming of over 14 resources (e.g., MedicationOrder to MedicationRequest). Furthermore, SMART on FHIR now requires OAuth 2.0, necessitating a rebuild for applications that previously relied on looser DSTU2 authentication. The migration is also driven by regulatory pressure, as CMS-0057-F sets a January 2027 compliance deadline for provider-to-payer data exchange. Developers must focus on the specific API changes and the order of remediation, rather than general FHIR overviews.
Original content copyright by respective publishers