Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC for skip values #215

Open
1 task
ericbuckley opened this issue Feb 12, 2025 · 0 comments · May be fixed by #218
Open
1 task

RFC for skip values #215

ericbuckley opened this issue Feb 12, 2025 · 0 comments · May be fixed by #218
Assignees
Labels
spike Research or investigation into a technical issue

Comments

@ericbuckley
Copy link
Collaborator

ericbuckley commented Feb 12, 2025

Summary

Develop an RFC that proposes a system for user-defined skip values. The proposal should address a range of situations, starting from simple "string values to ignore" to more complex "ignore when the context indicates so".

Acceptance Criteria

  • A new RFC with a proposal for implementing user-defined skip values

Details / Tasks

Largely speaking, there are two phases in the system in which we can achieve this.

  • Data validation, the process in which incoming data is cleansed and normalized.
  • Linkage matching, the process in which records are compared to one another.
    It should be strongly considered that the latter is preferable from a flexibility perspective. As it gives our users options to adjust the values over time.

Common skip values to consider.

Background / Context

Healthcare organizations often use placeholder values in documents to indicate missing information, such as the name “John Doe” or an address of “unknown.” When these values appear in incoming data, they should be excluded from comparisons. In other words, two patients should not be considered a match solely because both are named “John Doe.” Additionally, we want this functionality to be customizable, allowing organizations to extend or modify the default values provided by Record Linker to fit their specific needs.

@ericbuckley ericbuckley added the spike Research or investigation into a technical issue label Feb 12, 2025
@ericbuckley ericbuckley self-assigned this Feb 12, 2025
@ericbuckley ericbuckley changed the title [Title] RFC for skip values Feb 12, 2025
@ericbuckley ericbuckley linked a pull request Feb 14, 2025 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spike Research or investigation into a technical issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant