Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Release 4.3.2

  • Added the ability to export and import all the configuration information about an entity. This makes it easy to transfer the configuration settings of an entity from one instance to another.

  • Added a new transformation function for custom fields that standardizes the values of the telephone number to be in adherence to International Telecommunications Union Recommendation E.123.

  • Added a new transformation function for custom fields that standardizes the last name field based on the recommendations of the CAQH standard.

  • Added a new transformation function for custom fields that standardizes the date of birth field.

  • Added a configurable filtering capability to the blocking algorithm configuration that can improve considerably the performance of add and update requests.

  • Added an option to the export records feature that will also export the single best records from an entity if the single best record capability has been enabled.

  • Based on popular request, made the custom field values visible when viewing records from an entity in the UI.

  • Added more information to the log about the effectiveness of the blocking algorithm configuration that can assist in adjusting the configuration in order to improve its effectiveness.

  • Fixed an issue where changing the custom field configuration of an entity was not immediately updated throughout the system.

  • Fixed an issue with the ability to regenerate the indexes of a single blocking round where it was not working for the very first round.

  • Updated many library dependencies to eliminate security vulnerabilities that had been reported in those dependencies.

Release 4.3.1

  • Upgraded the version of various libraries to eliminate security vulnerabilities that were recently reported

  • Added a framework for evaluating the performance of the blocking algorithm against a ground-truth dataset where the set of duplicate records is known

  • Added a framework for evaluating the performance of the matching algorithm against a ground-truth dataset where the set of duplicate records is known

  • Reduced the startup time of the server especially for sites with millions of records in the repository

  • Fixed an issue with the operation to start and stop the listener service for the HL7v2 PIX/PDQ protocol support

  • Fixed an issue where after adding a new entity using an import statement, you are unable to create a custom field against it.

  • Fixed an issue where after switching to the probabilistic matching algorithm, you are unable to use a custom field as one of the matching fields until after restarting the server

  • Fixed an issue with the cache manager resetting the connection to the configuration database

  • Fixed an issue where after deleting an entity, the configuration of the blocking and matching algorithms associated with that entity were not being deleted

  • Added support for quickly loading the configuration of an entity from a JSON backup to help support customers that need assistance with the configuration of their instances

Release 4.3.0

  • Modified the architecture of OpenEMPI to solely rely on the graph database and to no longer use a relational database to store configuration information.

  • Added a new machine learning-based algorithm that allows the user to determine the best similarity metric (comparator) and threshold to use for a specific matching field specifically for their dataset.

  • Added a data standardization feature that allows the user to identify issues in their dataset and resolve them across the entire dataset

  • Added the ability to switch matching algorithms for a particular entity through the UI

  • Added a dashboard of performance related metrics to the home page of the web manager application to assist users identify resource related issues early and resolve them before they become critical

  • Added a scheduled task that deletes logged links from the database so that they don’t accumulate and cause resource issues after a while.

  • Modified the reports to not use fonts that require additional packages to be installed on some Linux distributions

  • Added more validation of the parameters that are used to configure transformation functions for custom fields

  • Upgraded numerous libraries and packages to recent versions to eliminated any security vulnerabilities that have been identified

  • Added the ability to rebuild individual blocking rounds instead of having to rebuild all blocking rounds at once

  • Added the ability to copy the blocking and matching configuration from one entity to another through the UI

  • Made various changes that improved the performance of the system

...