Skip to content

Releases: CDCgov/RecordLinker

v25.10.0

18 Jul 19:51
922b53b

Choose a tag to compare

What's Changed

Full Changelog: v25.9.0...v25.10.0

v25.9.0

09 Jul 20:47
62b2a15

Choose a tag to compare

What's Changed

Full Changelog: v25.8.0...v25.9.0

v25.8.0

11 Jun 22:33
cc89832

Choose a tag to compare

Summary

v25.8.0 focused on expanding our algorithm testing suite and performance upgrades to the database queries.

  • The expansion of the algorithm test suite, vastly improved upon our algorithm performance metrics, mostly through the addition of more meaningful tests along with larger person cluster sizes. See the README for more information on the different algorithm tests provided.
  • When testing the /api/link endpoint using a large database (~1 million person clusters) significant performance issues we're measured. By reworking an existing index, we were able to improve performance by ~25x. Our new indices, now allow us to run /api/link requests on a database with 1 million person clusters, just as fast as an empty database.

Bugfixes

  • bugfix: delete patient with keys by @ericbuckley in #418
    • previously using the DELETE /api/patient/{patient_reference_id} would raise a 500 if the patient record in question had blocking values associated with it. This has been fixed.

What's Changed

New Contributors

Full Changelog: v25.7.0...v25.8.0

v25.7.0

09 May 19:09
de8e8a0

Choose a tag to compare

Summary

v25.7.0 focuses on removing kwargs. Compared to the previous release, v25.6.0, this version's removal of "kwargs" has had no noticeable changes in performance or results. The major changes to highlight were:

  • The kwargs field has been removed from the algorithm configuration. All necessary parameters are now explicitly defined (e.g., log_odds, fuzzy_match_measure, fuzzy_match_threshold). See the API documentation for full details.
  • Linkage results now include a mapping of the evaluated features to the median log-odds points they contributed. This provides greater transparency into which features most influenced the scoring process.

What's Changed

Full Changelog: v25.6.0...v25.7.0

v25.6.0

30 Apr 20:34
952a4da

Choose a tag to compare

Summary

v25.6.0 focuses on adding skip values. Compared to the previous release, v25.5.0, this version's addition of skip values has:

  • Made the algorithm more conservative and more able to filter out non-matching data, which can enhance match confidence
  • Surfaced that name fields are particularly important to DIBBs algorithm—conducting some follow-up research to examine this effect
    • One experiment shows early promise in adding a third pass that splits up first and last name, but it’s on synthetic data
    • We don’t want to over-index or jump to conclusions too early, because it’s unlikely that Montana’s data looks precisely like this synthetic information

What's Changed

Full Changelog: v25.5.0...v25.6.0

v25.5.0

17 Apr 18:36
c5b0589

Choose a tag to compare

Summary

v25.5.0 focuses on replacing the belongingness ratio score with a relative match score. Compared to the previous release, v25.4.0, this version achieves the same quality and performance as the previous version. Before upgrading, you should reset your database schema.

What's Changed

Full Changelog: v25.4.0...v25.5.0

v25.4.0

03 Apr 14:25
e2f9c50

Choose a tag to compare

Summary

v25.4.0 is a performance-focused update aimed at enhancing linkage through field normalization and improved handling of records with missing values. Compared to the previous release, v25.3.0, this version achieves an 18% (15 tests) increase in correctly matched NBS algorithm test cases. In terms of speed, performance remains consistent with the prior build. A speed test linking 200 person clusters with 764 records averaged 67.11s, compared to 66.70s in the previous version.

What's Changed

Full Changelog: v25.3.0...v25.4.0

v25.3.0

28 Feb 18:58
a2798c1

Choose a tag to compare

Breaking Changes

The deprecated endpoints POST /patient/<patient_reference_id>/person and PATCH /patient/<patient_reference_id>/person have been removed. Please use their replacements added in v25.2.0 going forward.

The IDENTIFIER blocking key has updated its format to exclude authority data. This results in a new value of {value[-4:]}:{type} for all new IDENTIFIER blocking keys. We recommend resetting your database before upgrading to this release.

  • Removed first 2 chars of authority from IDENTIFIER blocking key by @ericbuckley in #227

What's Changed

Full Changelog: v25.2.0...v25.3.0

v25.2.0

13 Feb 22:16
v25.2.0
c7aa14d

Choose a tag to compare

Breaking Changes

The dibbs-basic algorithm and all non-probabilistic matching functions have been removed from the codebase. Before upgrading to this release, you should truncate your algorithm and algorithm_pass tables to allow for the new default algorithms to load.

Deprecations

The existing /patient/<id>/person API endpoints have been deprecated and are scheduled to be removed in v25.3.0. Please see the API documentation for replacement endpoint information.

What's Changed

New Contributors

Full Changelog: v25.1.2...v25.2.0

v25.1.2

31 Jan 21:39
d76f725

Choose a tag to compare

What's Changed

Full Changelog: v25.1.1...v25.1.2