We are excited to announce we will be updating the hardware and EHR instance supporting our public sandbox environment on Monday August 17th, . As part of this upgrade our public sandbox environment will transition to a new Millennium domain which more closely aligns with Cerner’s recommended Model build and is on a more relevant code-level to present day general availability.
Migration InformationBecause we are moving to a new Cerner Millennium domain, we need to move registered applications from the current public sandbox environment to the new environment.
On Monday August 17th, around 11 a.m. central time, we will disable the ability to register new applications to access our current public sandbox environment. The code console will then be updated to interact with the new public sandbox environment.
We will migrate developers’ applications in their current state on Friday August 14th around 1 p.m. central time. Application details from the current sandbox environment will still be available to reference at a URL provided after the migration.
We are currently in the process of migrating system accounts for applications using system access or patient offline access. This may take several weeks so please have patience as your system accounts are migrated.
You can determine if your system account has been migrated by accessing
https://cernercentral.com/system-accounts. You will receive an email from
nor...@cernercentral.com about a “System Account Administrator Invitation” inviting you to become an administrator for the migrated system account. Please accept the invitation to continue your administrator access to the system account and retrieve the new secret. We recommend you add additional administrators to the account to avoid a single person having control of your system’s credentials.
If you own an application deployed to a Millennium production environment you will see your application is in a read-only state which prevents editing or deleting of your application. Please reach out to us if you need to make additional changes to your application (see below for communication channels).
In the next couple of weeks we will start removing functionality related to the current public sandbox environment. Please see the timeline below.
- Friday, August 14th
- Developers’ application definitions migrated to the new sandbox environment
- Monday, August 17th
- Cerner’s developer code console goes live on new sandbo
- Developers’ applications defined in the old public sandbox are available at an alternative URL
- Monday, August 24th
- Disable editing/deleting of applications for the old public sandbox environment via the alternative URL
- Disable open-endpoint access to old public sandbox environment
- Monday, August 31st
- Disable launching of applications from code console to old public sandbox environment
- Tuesday, September 8th
- Disable closed-endpoint access to old public sandbox environment
New Public Sandbox Environment DetailsThe new public sandbox environment service root URLs:
All service root URLs require your application support TLS SNI [1] and the
fhir-ehr-code.cerner.com URLs will no longer support TLS 1.1 or below.
If your application is launched using the SMART app launch framework, please use this opportunity to ensure your application uses the provided information on launch. The issuer parameter is provided on launch to query the metadata endpoint to discover the OAuth authorize and token endpoint URLs so your application should be able to seamlessly create tokens for the new public sandbox. In addition, if there is a patient in-context, it will be provided in the token response. If the application follows the “iss” parameter, this transition should be relatively easy (the application may need to update an allow list if used to determine trust of FHIR servers).
Documentation on
https://fhir.cerner.com will be updated to reflect reference the new sandbox environment on August 17th. Additionally, test patient information will be provided as well as a document highlighting which patients in the new domain match previous test patients.
Please reach out to us if you have any additional questions.
For Cerner Clients, please reach out via eService
For code program members, via your uCern collaboration group
For all others, via this Google group
[1]
https://www.cloudflare.com/learning/ssl/what-is-sni/