2023-07-27 5:00pm ET – PRODUCTION and VALIDATION
The legacy Participant directories will be retired on July 27 and will no longer be updated after July 27. To facilitate the migration to the new FHIR R4 HAPI-based directories, the eHealth Exchange will begin forwarding UDDI and FHIR requests from the legacy directories to the new HAPI directories in the coming weeks. The eHealth Exchange is aware of several participants which need to migrate to the HAPI directories, but please inform administator@ehealthexchange.org that you need to migrate if not sure. The HAPI directories have been available to all participants since April 12, 2023. For additional information, the July all-participant call discussed the directory migration, and the July slide deck has been uploaded to https://ehealthexchange.org/wp-content/uploads/2023/07/All-Participant-Call-July-2023-Final-Draft.pdf. The April all-participant call provided technical details on accessing the directory and the April slide deck has been uploaded to https://ehealthexchange.org/wp-content/uploads/2023/04/All-Participant-Call-April-2023-FINAL.pdf . If your organization needs to track deleted directory entries, please email administator@ehealthexchange.org for an update to the April slide deck.
2023-07-27 5:00pm ET – PRODUCTION
Updates to the Hub Directory Sync task with fixes and support for the new R4 directories.
Scope:
These changes will be applied to the eHealth Exchange Hub PRODUCTION and VALIDATION environments as outlined above.
Impact:
We do not anticipate any other service interruptions during the Thursday maintenance event; Real-time routing of messages through the Hub will be unaffected.
Support:
eHealth Exchange staff will monitor administrator@ehealthexchange.org during the upgrade window to address any questions or concerns.
ADDITIONAL INFORMATION AND REMINDERS:
The eHealth Exchange Hub team has implemented a recurring weekly scheduled maintenance window each Thursday evening at 5:00pm ET for all non-urgent events. The duration of each maintenance event will be determined by the respective changes for each event, and details will be communicated out to all Participants at least 48 hours prior to the event. If there are no changes for any given week, then the maintenance event will not occur, and no notice will be sent. Also please note that Operating System and similar updates that do not require a service outage, and do not require changes to the application layer, will be performed during this scheduled maintenance window without specific notice due to their frequent and routine nature.
