This problem affects the following products:
- Unified Care Record 2021.1, 2021.2, 2022.1, 2022.2, if the customer received an adhoc for HSDD-356
- Unified Care Record 2023.1 and higher, all customers
Requirements:
- ODS
- ODS Autoload feature disabled (the default)
The Autoload setting on the ODS controls whether system events such as the arrival of new data or viewing of a patient record will result in a patient being loaded and cached in the ODS. There is also an API provided for customers to control this process manually using their own business logic.
In version 2022.2, a defect was corrected in ODS where MPI events such as MRN merges or MPIID links were not being properly processed by the ODS. This resulted in the user not seeing data they would expect because it was not properly merged into the record they were viewing. That correction, HSDD-356, was the subject of a previous advisory:
Advisory: ODS Autoload Settings Can Prevent Important Updates
The resolution for the previous defect introduced a new defect that can be described as the opposite problem. The logic for loading a patient into the ODS when an MPI event occurs now allows many, many more patients to be loaded than were originally intended. In some cases, like EMPI Linkage Definition rebuilds, nearly all patients might get loaded regardless of whether the ODS Autoload feature is enabled or disabled. This additional data might lead to an unexpected significant increase in storage footprint which could potentially lead to system downtime.
The correction for this defect is identified as HSDD-2364, which is included in version 2026.1 of HealthShare and all future product releases. It is also available for older versions via ad hoc change file (patch) or full kit distribution by contacting the Worldwide Response Center (WRC).