Stream: argonaut
Topic: provenance roles
Jay Lyle (Jan 12 2019 at 20:22):
We have many fields to map to FHIR that involve signature, co-signature, entry, amendment, etc. I believe provenance is the way to do this, but we have a lot of roles that are not reflected in the codes - 'signed,' e.g., and 'co-signed.' We might assert that our 'signed' equals 'legally authenticated,' but then we have a problem with 'co-signed,' and others.
I think we need new values. The value sets (for activity and for agent.role) are extensible, so we can do that. But the obvious source systems (V3, SCT) don't seem to have what we want.
What are others doing about this?
Grahame Grieve (Jan 12 2019 at 20:42):
in general, argonaut are not using provenance. You might ask on the implementers channel
John Moehrke (Jan 13 2019 at 19:59):
sounds like you are talking about signature types. As can be seen in Signature.type vocabulary http://build.fhir.org/valueset-signature-type.html
Last updated: Apr 12 2022 at 19:14 UTC
