Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Patient Compartment - resource aggregation (TestID12) #16

Open
nir-r opened this issue May 30, 2024 · 1 comment
Open

Test Patient Compartment - resource aggregation (TestID12) #16

nir-r opened this issue May 30, 2024 · 1 comment
Assignees
Labels
help wanted Extra attention is needed

Comments

@nir-r
Copy link
Collaborator

nir-r commented May 30, 2024

Test12If a patient compartment is declared (CapabilityStatement.rest.compartment) - check it aggregates resources correctly

@nir-r nir-r changed the title Test Patient Compartment - TestID12 Test Patient Compartment - resource aggregation (TestID12) Jun 5, 2024
@nir-r nir-r self-assigned this Jun 5, 2024
@nir-r nir-r added the help wanted Extra attention is needed label Jun 10, 2024
@nir-r
Copy link
Collaborator Author

nir-r commented Jun 16, 2024

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:

https://hl7.org/fhir/R4/compartmentdefinition.html#use
"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant