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.

Sign up for GitHub

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

Jump to bottom

Provide guidance on which Provenance resources to return #67

Closed
gotdan opened this issue Apr 27, 2020 · 1 comment
Closed

Provide guidance on which Provenance resources to return #67

gotdan opened this issue Apr 27, 2020 · 1 comment
Labels
Argo2020 Argonaut 2020 Issues

Comments

@gotdan
Copy link
Collaborator

gotdan commented Apr 27, 2020

Potential behaviors for a patient level or group level bulk export request:

  • All Provenance resources associated with any resource in the patient compartment. Parallels behavior of other resources.
  • Most recent Provenance resource associated with any resource in the patient compartment.
  • All Provenance resources associated with any resource being returned. If _type is used to restrict the response set, a subset of Provenance resources would be returned. If _type is set to only Provenance, then no resources would be returned. This seems like it would align with the many common bulk data export use cases.
  • Most recent Provenance resource associated with any resource being returned. If _type is used to restrict the response set, a subset of Provenance resources would be returned. If _type is set to only Provenance, then no resources would be returned.

Potential behaviors for a system level bulk export request:

  • All Provenance resources associated with any resource in the system. Parallels behavior of other resources. This seems like it would align with the most common full system export use cases.
  • Most recent Provenance resource associated with any resource in the system.
  • All Provenance resources associated with any resource being returned. If _type is used to restrict the response set, a subset of Provenance resources would be returned. If _type is set to only Provenance, then no resources would be returned. John Moehrke pointed out on Zulip that this would not work for an export of legal medical records audit for safety and records retention compliance.
  • Most recent Provenance resource associated with any resource being returned. If _type is used to restrict the response set, a subset of Provenance resources would be returned. If _type is set to only Provenance, then no resources would be returned.

Open questions:

  • Should patient level queries have a different default than system level queries?
  • Should we define this behavior by data set (eg. servers returning USCDI would have one standard behavior and servers returning Blue Button could have another)?
  • Do we need an additional request parameter to indicate which of the above behaviors is desired or are the use cases common enough to have a single approach? In USCDI REST queries, _revinclude syntax is used for this.
@gotdan gotdan added the Argo2020 Argonaut 2020 Issues label Apr 27, 2020
@gotdan
Copy link
Collaborator Author

gotdan commented Aug 13, 2020

Addressed in #76

@gotdan gotdan closed this as completed Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Argo2020 Argonaut 2020 Issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gotdan