FI-3817: MedicationRequest Multiple_Or Search Fix

[esemple998]

Summary

The MedicationRequest resource has two optional search requirements on patient+intent+encounter and patient+intent+authoredon. Previously, when testing it with reference server with patient 355 only, both test failed with errors:

Could not find plan values from intent in any of the resources returned for Patient/355
or
Could not find order values from intent in any of the resources returned for Patient/355

These searches are not the first search, so the tests use the result from first search to compile search values. From the first search, there is one MedicationRequest with intent=order and encounter=Encounter/1, and also a MedicationRequest with intent=plan and no encounter reference. The multiple_or search test therefore expected that patient 355 had MedicationRequests with intent=order, plan and encounter=Encounter/1, but it was not able to recognize that the only MedicationRequest with intent=order did not have an encounter reference.

Added a fix for this problem by adding a filter to the list of existing values that the multiple_or search test compiles. This filter makes it so that a multiple_or parameter value will not be added to the list of existing values if the value comes from a resource that does not include all of the search parameters that are currently being searched by. So, in this example, it would not add order to the list of existing values for the intent search param, since the resource that containsintent with this value does not contain all of the search parameters for the patient+intent+encounter search (missing encounter).

Testing Guidance

Run the MedicationRequest test with patient 355 and ensure the patient+intent+encounter and patient+intent+authoredonsearch tests pass. Also, run the spec tests and ensure those pass.

[yunwwang]

This unit test is not working. If I commented out this line in search_test

.filter { |resource| contains_all_search_params(resource, search_params) }

This unit test still pass which should fail.

And we need another unit test for the use case when the medication_request_2 has a different encounter id.