FHIR Chat · X-Provenance Header · implementers

Stream: implementers

Topic: X-Provenance Header


view this post on Zulip nicola (RIO/SS) (Feb 21 2019 at 07:50):

I don’t like a lot of idea to send resource in header. What to do if it is not valid? Should post/put fail? How to communicate an error details?

view this post on Zulip nicola (RIO/SS) (Feb 21 2019 at 07:59):

essentially this is resource metadata, why don’t put this info in meta?

view this post on Zulip John Moehrke (Feb 21 2019 at 14:05):

because it is a Provenance resource and it needs to be managed as a full Resource...
I would say that if the Provenance is invalid, YES it is a failure. The only way I could see it as not a failure is if the server is ignoring all x-provenance headers.

view this post on Zulip John Moehrke (Feb 21 2019 at 14:06):

And if you don't like it.. then don't use it.. the alternative is to do all Create using a Batch/Transaction with the Bundle holding the resource you want to create and the Provenance. This x-provenance header is just an alternative to the same thing.

view this post on Zulip nicola (RIO/SS) (Feb 21 2019 at 15:23):

Thx :)

view this post on Zulip Shovan Roy (Feb 12 2020 at 00:56):

Hi Team,

I was going through the https://www.hl7.org/fhir/provenance.html#header section and have a query about auditing (AuditEvent) a PUT/POST request which uses X-Provenance Header. Shall it be audited as another entry (AuditEvent.entity) along with the actual payload or it should be a different audit? any guidance?

looping in @John Moehrke

view this post on Zulip Shovan Roy (Feb 13 2020 at 02:49):

just following it up if there is any suggestion on this?

view this post on Zulip Lloyd McKenzie (Feb 13 2020 at 05:09):

Poking @John Moehrke again :)

view this post on Zulip John Moehrke (Feb 13 2020 at 15:58):

Sorry for the delay. I just got back from the HL7 meeting. When using the X-Header method, it would seem reasonable that a server generated AuditEvent would be just one log including both the creatino/update of the resource, and the creation of the x-header contained provenance. Thus there would be two AuditEvent.entity entries for the resource and Provenance. This likely should be noted in FHIR core, so please create a change request to add this clarification.

view this post on Zulip Shovan Roy (Feb 13 2020 at 21:22):

thanks @John Moehrke , I'll create a task on this.

view this post on Zulip Shovan Roy (Feb 17 2020 at 22:23):

Hi @John Moehrke I've created the change request as suggested : FHIR-26314: Auditing x-provenance header


Last updated: Apr 12 2022 at 19:14 UTC