Description

Adding the ability to compare on address line and also create blocking keys on it. Also making a few testing changes and fixing bugs to make the code ready for #24.

Related Issues

#24

Additional Notes

Mypy fixes

• Updated type annotations in compare function to use models.Feature instead of models.FEATURE. (src/recordlinker/linking/link.py)
• Changed the comparison result type from bool to float to allow for more granular matching results. (src/recordlinker/linking/link.py)

Improvements to Patient class:

• Introduced a setter for the data property to update the internal state and clear the cached record. (src/recordlinker/models/mpi.py)
• Modified the record property and its setter to use model_construct for creating PIIRecord objects, enhancing data handling and validation. (src/recordlinker/models/mpi.py)

New features:

• Added ADDRESS as a new BlockingKey to support blocking based on the first four characters of the address. (src/recordlinker/models/mpi.py)
• Implemented logic for the ADDRESS blocking key in the to_value method. (src/recordlinker/models/mpi.py)

<--------------------- REMOVE THE LINES BELOW BEFORE MERGING --------------------->

Checklist

Please review and complete the following checklist before submitting your pull request:

• I have ensured that the pull request is of a manageable size, allowing it to be reviewed within a single session.
• I have reviewed my changes to ensure they are clear, concise, and well-documented.
• I have updated the documentation, if applicable.
• I have added or updated test cases to cover my changes, if applicable.
• I have minimized the number of reviewers to include only those essential for the review.
• I have notified teammates in the review thread to build awareness.

Checklist for Reviewers

Please review and complete the following checklist during the review process:

• The code follows best practices and conventions.
• The changes implement the desired functionality or fix the reported issue.
• The tests cover the new changes and pass successfully.
• Any potential edge cases or error scenarios have been considered.