Stream: implementers
Topic: Provenance Creation
Vanitha (Nov 29 2018 at 09:41):
Hi All,
What is the best way to implement provenance at server side. Can any one suggest me.
John Moehrke (Nov 29 2018 at 15:22):
The core specification has many possible ways to do Provenance. This because it is a core specification. I have seen some implementation guides that constrain Provenance for their specific use-case (e.g. IHE mXDE and QEDm profiles).
John Moehrke (Nov 29 2018 at 15:23):
There is a possibility that the FHIR server can take the security token on the "create" or "update" and put that data into a server side created Provenance. This is useful, but can't fill in details not communicated in the security token. Such as what data was used to create this new resource (Provenance.entity)
John Moehrke (Nov 29 2018 at 15:24):
That said... that is more useful than having no Provenance... and it would not conflict with a more descriptive proveannce provided by the client.
John Moehrke (Nov 29 2018 at 15:26):
But it seems that auto creation of a Provenance on the server is not really provenance, it is an AuditEvent. I think what you are proposing would be an AuditEvent.
Last updated: Apr 12 2022 at 19:14 UTC
