As we move towards a concept of only have N number of blocking keys available to customers, we need to determine exactly what those keys should be.
Acceptance Criteria
[ ] A recommendation of ~10 blocking keys customers can pick from
Details / Tasks
We have 6 keys currently in use by the DIBBS_* algorithms, so at the very least we'll need these 6 going forward. There are likely a few more, which may provide good value for customers to optionally "block" with when retrieving from the database.
birthdate
sex
zipcode
last 4 of mrn
first 4 of first name
first 4 of last name
Background / Context
Having a universal set of blocking keys, rather than unlimited, has many advantages. a) its easier to drive a UI for users to configure their algorithm b) we can optimize the database up front for the appropriate blocking key indexes c) we can limit customers to keys we know are useful and not allow them to make too many inappropriate decisions.
Summary
As we move towards a concept of only have N number of blocking keys available to customers, we need to determine exactly what those keys should be.
Acceptance Criteria
Details / Tasks
We have 6 keys currently in use by the DIBBS_* algorithms, so at the very least we'll need these 6 going forward. There are likely a few more, which may provide good value for customers to optionally "block" with when retrieving from the database.
Background / Context
Having a universal set of blocking keys, rather than unlimited, has many advantages. a) its easier to drive a UI for users to configure their algorithm b) we can optimize the database up front for the appropriate blocking key indexes c) we can limit customers to keys we know are useful and not allow them to make too many inappropriate decisions.