There are a some milestones you could call out here:
-
Come up with query to detect new/changed patients. I think this will have to be generic. In a really fancy version, we would detect only changes in attributes used by the strategy, but I think that level of fanciness is out of scope for now.
-
Refactor module so, by default, it just runs matching on patients who are new/changed since strategy last run.
-
Validating our approach (using small set of demo patients)
This is be a relatively small change (i.e., just exposing an option to ignore date of last run), so hopefully won’t take too long to implement.
In test-driven development (what we should be striving for), tests should be written before code.
Hopefully we’ll be getting in some code review along the way. 