FHIR Chat · Provenance · Da Vinci PDex

Stream: Da Vinci PDex

Topic: Provenance


view this post on Zulip Anusha (Feb 23 2021 at 21:45):

Hi everyone. I'm trying to parse the PDEX SHALL requirements related to Provenance (as a payer implementing the IG).

  • In addition to the searchRevInclude interaction, is the expectation that a client application should be able to query a bundle/resource and then return to the FHIR server n days later and get the provenance for that bundle/resource using the bundle/resource reference?
  • The timestamp that's captured in the recorded field should always be the Date/Time that the payer received the information or created the bundle -- is that correct?

view this post on Zulip Anusha (Mar 11 2021 at 15:56):

@Mark Scrimshire Any chance you're able to help with this question? :point_up:

view this post on Zulip John Moehrke (Mar 11 2021 at 16:11):

typically the Provenance.occured[x] would be when the activity the Provenance describes happened. The Provenance.recorded is when the Provenance record was created. Most of the time they are the same, but there is no requirement they are the same.

view this post on Zulip Anusha (Mar 11 2021 at 16:21):

@John Moehrke So when we're dealing with a transmitter provenance record, would Provenance.recorded still be when the record was received/created by the payer? (As opposed to the timestamp of the response to a specific app's API call?)

view this post on Zulip John Moehrke (Mar 11 2021 at 16:28):

I think you are now asking a question that only a developed and deployed system could answer. My answer is about the intent of the Provenance resource core FHIR resource definition.

view this post on Zulip Anusha (Mar 11 2021 at 17:43):

Hmm, okay. So in the context of the Patient Access API, is the intent of the "transmitter" Provenance scenario to
1) create effectively an audit log in the FHIR server of each time an app requested and received a resource?
OR
2) capture that the payer is acting as a transmitter for a resource that they received at x time, and be able to pass that context on to any app that requests that resource?

view this post on Zulip Anusha (Mar 16 2021 at 20:06):

Anusha said:

Hmm, okay. So in the context of the Patient Access API, is the intent of the "transmitter" Provenance scenario to
1) create effectively an audit log in the FHIR server of each time an app requested and received a resource?
OR
2) capture that the payer is acting as a transmitter for a resource that they received at x time, and be able to pass that context on to any app that requests that resource?

@John Moehrke following up. Thank you!

view this post on Zulip Anusha (Jul 30 2021 at 17:44):

Hi folks. We're reviewing the Provenance requirements, and we were thrown off by the cardinality for author and transmitter here. Wouldn't we want Author to be 0..1 and Transmitter to be 0..*? I would expect a record to have one author but multiple transmitters over time. image.png


Last updated: Apr 12 2022 at 19:14 UTC