The system should support configurable entity matching, a service to assist in identifying duplicate patients.
a. The rules for determining whether two records match each other should be configurable (e.g., ability to use both statistical and/or rules based, etc.).
b. The blocking strategy for loading potential matches before the matching rules are applied should be configurable.
c. Any configurable component should have an interface so that advanced users can write their own implementation from scratch if desired.
d. Any interface should have at least one default implementation.
e. The default implementation should be flexible and configurable so that non-programmers can adjust it to meet their needs.
f. To the extent possible, CR system configuration information should be managed using consistent and easy to access methods, such as a database, properties files, or XML files).
g. It should allow “wizard-based” or “guided” setup of matching rules.