Notice of Operational Change
Description of changes: Updated routing logic on the eHealth Exchange Hub to expand the scenarios in which messages are routed through the Hub (specific to those Participants who subscribe to […]
Notice of Operational Change
Description of changes: Updated pragmatic routing logic on the eHealth Exchange Hub to expand the scenarios in which messages are routed through the Hub. Administrative utility to better support FHIR […]
Notice of Operational Change
Description of changes: Update to how the Directory Sync task handles parent-child Participant relationships. Scope: These changes will be applied to the eHealth Exchange Hub PRODUCTION environments as outlined above. […]
Notice of Operational Change
Description of changes: Updates to the recurring task that purges clinical documents from the PRODUCTION Hub logs. The message trace will still be retained for seven days for troubleshooting purposes, […]
Notice of Operational Change
Description of changes: The Hub task that pulls updated RSAKey information from Participants is being updated to improve performance. Scope: These changes will be applied to the eHealth Exchange Hub […]
Notice of Operational Change
Description of changes: There are two message auditing changes being deployed to the PRODUCTION Hub to address issues found on the Hub Dashboard. An update to how the Hub lists […]
30 Day Notice and Objection Period
Notice of Operational Change
Description of changes: Updates to the recurring task that purges clinical documents from the PRODUCTION Hub logs. The message trace will still be retained for seven days for troubleshooting purposes, […]
Notice of Operational Change
Description of changes: The existing PROD Hub certificates will be updated before their upcoming expiration date. All existing, valid certificates used by Participants will continue to work for exchange across […]
Notice of Operational Change
Description of changes: Updates to the recurring task that purges clinical documents from the PRODUCTION Hub logs. The message trace will still be retained for seven days for troubleshooting purposes, […]
