FHIR Chat · Provenance.read - required for g.10? · inferno

Stream: inferno

Topic: Provenance.read - required for g.10?


view this post on Zulip Cooper Thompson (Jul 05 2021 at 15:17):

We noticed recently that US Core still requires the read interaction for Provenance (US Core requirement link). There was some past discussion in #implementers on whether that was useful, and I think the consensus was that it wasn't (though that might be debatable).

view this post on Zulip Cooper Thompson (Jul 05 2021 at 15:19):

I think most folks would agree that _revInclude is really the main way to access Provenance. Do folks think Provenance.read is necessary? Are there options to scope that out of g.10 certification (and Inferno tests, though we need an industry / ONC decision before Inferno would address a github issue on the topic I expect).

view this post on Zulip Cooper Thompson (Jul 05 2021 at 15:20):

There is also some language in the g.10 CCG about Provenance that points to the US Core guidance section. Though it isn't clear if that is intended to override or clarify the CapabilityStatement section of US Core.

view this post on Zulip Cooper Thompson (Jul 05 2021 at 15:25):

Eh - maybe this came up already on #argonaut: https://chat.fhir.org/#narrow/stream/179175-argonaut/topic/US.20Core.20Provenance.20Profile


Last updated: Apr 12 2022 at 19:14 UTC