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

Open Issue 7: search parameters #94

Open
lukeaduncan opened this issue May 2, 2022 · 2 comments
Open

Open Issue 7: search parameters #94

lukeaduncan opened this issue May 2, 2022 · 2 comments
Labels
open issue Open Issue mentioned in Implementation Guide

Comments

@lukeaduncan
Copy link
Contributor

Should there be additional required search parameters? Should
we also require any reverse chaining (_has) options for the search?
Should we require any reverse includes (_revinclude)? These would add
complexity to the server and most will have similar options through
include and normal chaining.

@lukeaduncan lukeaduncan added the open issue Open Issue mentioned in Implementation Guide label May 2, 2022
@JohnMoehrke
Copy link
Contributor

it is not forbidden, and a server can advertise support in their CapabilityStatement... so what would be the use-case to mandate it in mCSD?

@lukeaduncan
Copy link
Contributor Author

Combined from now closed issue 22: In ITI-90, we've added a number of required search parameters to support
queries for OrganizationAffiliation and Endpoint. Is it sustainable to require this many
search parameters? Should we move some to SHOULDs or MAYs? Note that the main use case
is locating an Organization based on its business, not network, attributes (already
covered elsewhere in mCSD), then checking its Endpoints. Further, recursively searching
parents and affiliations for Endpoints is likely an edge case, not one we need to try to do
in a single request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open issue Open Issue mentioned in Implementation Guide
Projects
None yet
Development

No branches or pull requests

2 participants