Potential Ref App Blocker: Multiple search handlers for patients?

The PIH EMR patient search just started to fail with the release of registration core 1.7.0. (We automatically pick up new released versions of all modules).

The problem appears to be that a new Search Handler for patients was added to the Registration Core, and this is conflicting with a Search Handler defined int EMR-API.

It’s easy enough for us to roll back to an earlier version of Registration Core for now, which I’m going to do… For the record, a quick test on qa-refapp doesn’t seem to show the problem happening there.

I can investigate in the coming days what is going on, but probably won’t get to it immediately, but since the Ref App release seems to be imminent, I wanted to flag it here.

Ticket I created:

Take care, Mark

1 Like