VALIDATION
- Enhancement to the audit message content that is sent from the Hub to the Hub Dashboard. Audit messages will include the Hub’s router instance where request was processed.
- Enhancement to Hub event logging to generate more detailed error messages to facilitate troubleshooting.
We expect that this week’s maintenance in VALIDATION will require up to 15 minutes of service interruption at some point between 9:00pm and 10:00pm ET.
PRODUCTION
- Promotion of wsa:To enhancement
An enhancement is being deployed to the eHealth Exchange PRODUCTION environment to optionally modify the WS-Addressing To (wsa:To) element within the SOAP header to set the value to the ultimate receiver, and then re-sign the message if necessary. This change has been developed to mitigate an existing issue whereby some Participant responders are unable to successfully validate the “wsa:To” value when the Hub passes through the request from the initiator. Please note that this message transformation logic is configurable and will only be used on a case-by-case basis when needed to establish interoperability. Furthermore, the transformation will only occur with the awareness and approval of the eHealth Exchange Participant that is the recipient of the message.
We do not anticipate any service interruption in the PRODUCTION environment.
Scope:
These enhancements will be applied to the eHealth Exchange Hub VALIDATION and PRODUCTION environments as outlined above.
Impact:
The eHealth Exchange anticipates up to 15 minutes of service interruption in VALIDATION, and no service interruption in the PRODUCTION environment.
Support:
eHealth Exchange staff will monitor administrator@ehealthexchange.org for 30 minutes after the Thursday evening maintenance is completed.
ADDITIONAL INFORMATION AND REMINDERS:
The eHealth Exchange will be testing disaster recovery processes in July thru September 2020. The initial phase of testing is not expected to introduce any Hub service outages. Subsequent testing phases are expected to require service interruptions, and additional communication will be provided as the testing progresses. Specifically, the Aug/Sep phase will include an actual production fail-over to the disaster recovery site.
The eHealth Exchange Hub team has implemented a recurring weekly scheduled maintenance window each Thursday evening at 9: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.
