Oracle Health Millennium FHIR APIs
/dstu2/* version retirement
Stopped workingSubscribe to Oracle Health Millennium FHIR APIsShare
Calls to /dstu2/* on Oracle Health Millennium FHIR APIs stopped working on December 1, 2025.
Calls it hits
/dstu2/*
What to use instead of these calls
Call the FHIR R4 APIs under /r4/{tenant}/ instead of /dstu2/{tenant}/. Migrating requires updating your resources to R4 rather than only changing the endpoint path.
In Oracle Health Millennium FHIR APIs's words
As of December, 2025, Oracle will no longer support DSTU 2 FHIR APIs. For more information, see the FHIR DSTU2 End of Support announcement on the Oracle Health Developer Forums. This functionality is replaced by the R4 version. Update your applications to use R4 before December to prevent interruptions to service.
Facts
- API
- Oracle Health Millennium FHIR APIs
fhir-ehr.cerner.com - Kind
- Version retirement
- Takes effect
- December 1, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Oracle Health Millennium FHIR APIs's own pages
Questions
When does this change take effect?
Calls to /dstu2/* on Oracle Health Millennium FHIR APIs stopped working on December 1, 2025.
What happens to calls after December 1, 2025?
They have failed since December 1, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.