You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is based on the below from HL7.
This can only be tested on resource types that are included based on more than a single element, I.e, Procedure where a patient can be both the "patient" and \ or the "performer".
Do we need to actively find such an example to test that the patient compartment behaves exactly as the discreet calls below?
"
However, there is a key difference in functionality between compartment based searches and direct searches with parameters. Consider this search:
GET [base]/Patient/[id]/Communication
Because the definition of the patient compartment for Communication says that a Communication resource is in the patient compartment if the subject, sender, or recipient is the patient, the compartment search is actually the same as the union of these 3 searches:
GET [base]/Communication?subject=[id]
GET [base]/Communication?sender=[id]
GET [base]/Communication?recipient=[id]
There is no way to do this as a single search, except by using the _filter:
Test12If a patient compartment is declared (CapabilityStatement.rest.compartment) - check it aggregates resources correctly
The text was updated successfully, but these errors were encountered: