This problem affects the following products:
- HealthShare Unified Care Record® versions:
- 2022.2
- 2023.1
- 2023.2
- 2024.1
- 2024.2
- 2025.1
- 2025.2
Requirements:
- Unified Care Record 2022.2 or later
- A HealthShare namespace that has been deleted
Each namespace in a HealthShare federation is registered with the federation registry on the Registry instance.
When a new namespace is configured on a client instance, it registers itself with the federation on startup. The information for that namespace is sent to the Registry using secure HTTPS.
When a registered namespace is deleted on a client instance, a message is sent to the Registry to de-register the namespace. If an error occurs during the de-registration process, the overall deletion process will not complete and some undesirable metadata about the namespace might remain in federation globals.
The old metadata can cause future problems including:
- issues registering newly configured HealthShare namespaces
- broken object synchronization in HSSYS
To determine whether your systems are affected by this issue is to check the message.log for errors similar to the errors listed below:
=======================
2024-08-14 12:27:57.152 [ERROR] HS.Util.Installer.ConfigItem:UnInstall ERROR #5001: Failed to register namespace with Federation Registry. Details logged in application error log.
2024-08-14 12:27:57.152 [ERROR] HS.UI.Installer.Delete:Delete ERROR #5001: Failed to register namespace with Federation Registry. Details logged in application error log.
========================
An additional sign of the issue is that after deleting the namespace, its configuration item still shows up on the list of configurations in the Installer Wizard. Subsequent deletion attempts will then also have no effect.
The correction for this defect is identified as HSIEO-11349, which will be included in version 2026.1 of HealthShare and all future product releases. This correction is also available as an ad hoc patch for older versions.
The correction will prevent the issue from recurring, but if you find that you have already encountered the issue, contact the Worldwide Response Center (WRC). They can help you manually review the federation globals and make any appropriate edits.