Description of changes:
1. [PRODUCTION] Update to internal Hub directory synchronization processing.
A patch will be applied to the Hub’s directory synchronization process to resolve an issue whereby a small number of Carequality directory entries were not being imported. Please note that this change only affects organizations exchanging with Carequality using the eHealth Exchange Hub Carequality Bridge.
Effective Date/Time: 2020-06-25 09:00pm ET. We do not expect this update to require a service outage.
2. [PRODUCTION] New Hub-based endpoint URLs will be implemented within the Carequality directory for Connection entries underneath the eHealth Exchange Implementer node. Please note that this change only affects organizations exchanging with Carequality using the eHealth Exchange Hub Carequality Bridge.
Carequality Implementers/Connections will subsequently use the new Hub-based endpoint URLs to initiate requests to eHealth Exchange Participants via the Hub. This change removes IP address inbound firewall allow-listing as is required by current Carequality policies (documented in the Carequality Technical Trust Policy Document). The eHealth Exchange has requested that Carequality change their policy to allow IP address firewall allow- and deny-listing as we feel it increases security significantly. But as of now, Carequality policy forbids inbound IP address allow-listing.
Effective Date/Time: 2020-06-25 09:00pm ET. We do not expect this update to require a service outage.
3. [VALIDATION] Enhancement to transaction log processing.
An enhancement will be applied to the Hub’s transaction log processing to optimize storage requirements.
Effective Date/Time: 2020-06-25 09:00pm ET. We do not expect this update to require a service outage.
4. [REMINDER] The eHealth Exchange will be decommissioning legacy Participant directory servers on June 30th.
** ACTION NEEDED **
If your eHealth Exchange Gateway is using one of the 4 listed directories, then your gateway needs change its configuration prior to June 30th at 8:00pm ET or connectivity will likely be broken to the directory and hence your gateway may also have connectivity broken with key Exchange Participants.
As previously communicated, this is a reminder that the following directories will no longer be available as of June 30th at 8:00pm ET:
https://registry.nhinonline.net
https://registry-vs.nhinonline.net
https://val-ehex-uddi-02.sequoiaproject.org
https://prod-ehex-uddi-02.sequoiaproject.org
The following directories will continue to be available and should be used by Participants.
Hub-Aware Directories
PRODUCTION: https://prodhubawaredir001.ehealthexchange.org
VALIDATION: https://ehex-Hub-Aware-01.ehealthexchange.org
(soon to be renamed https://valhubawaredir001.ehealthexchange.org)
(New) Legacy Directories
PRODUCTION: https://prodlegacydir001.ehealthexchange.org
VALIDATION: https://vallegacydir001.ehealthexchange.org
Note that related communication was previously sent out on May 8th and during several eHealth Exchange Technical Work Group web meetings.
Effective Date/Time: 2020-06-30 08:00pm ET.
Scope:
These changes will be applied to the eHealth Exchange Hub VALIDATION and PRODUCTION environments as noted above.
Impact:
1. [PRODUCTION] Thursday 6/25 at 9:00pm ET, the directory synchronization issue will be resolved.
2. [PRODUCTION] Thursday 6/25 at 9:00pm ET, new Hub-based endpoint URLs will be enabled for use by Carequality Implementers/Connections.
3. [VALIDATION] Thursday 6/25 at 9:00pm ET, enhanced transaction logging will be deployed.
4. [VALIDATION and PRODUCTION] Tuesday 6/30 8:00pm ET the old legacy directories will be decommissioned.
Support:
eHealth Exchange staff will be closely monitoring administrator@ehealthexchange.org for 60 minutes after the updates are applied.
REMINDER:
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. Please note that when contacting techsupport@sequoiaproject.org or hubservicedesk@ehealthexchange.org you should receive an automated response. If you do not receive an automated response, it means that the ticket system likely did not receive your message, thus we ask that you please notify administrator@ehealthexchange.org so we can follow up.