Parameter for clients to indicate metadata resource requirements #76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmandel
reviewed
Jun 25, 2020
There was a problem hiding this comment.
Regarding AllProvenanceResources: If the server doesn't support includeAssociatedValue as an input parameter, then obviously a client can't pass in this value, and the server can't process it. So I'm not sure what "Default" means. Couldn't we instead note (outside of includeAssociatedValue definitions) that when servers maintain Provenance resources, these can be included in an export by default. I need help understanding why AllProvenanceResources needs to be defined here as an explicit value.
jmandel
approved these changes
Jul 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Provides ability for client to request all (a) provenance resources (default), (b) most recent provenance resources associated with other resources being returned, or (c) all provenance resources associated with other resources being returned.
In particular, seems like (b) could not be implemented using standard FHIR REST parameters. This approach could also be extended to support other metadata resources like AuditEvent by defining additional values.