Stream: implementers
Topic: Signatures on prescriptions
Hamed Rezaei (Dec 15 2021 at 06:35):
Hi
I don't know is it the right place to ask this question.
Is it possible to have multiple Digital Signature on a prescription?
Lee Surprenant (Dec 15 2021 at 12:15):
Hi Hamed. Right stream (#implementers ), wrong topic (R4B questions / issues). Maybe try starting a new one?
Lloyd McKenzie (Dec 15 2021 at 20:15):
I used admin powers to change the topic
Lloyd McKenzie (Dec 15 2021 at 20:19):
Signatures can appear in Bundle, Provenance and Extension. At the moment, Bundle limits signature to 0..1. The other two methods allow 0..*. In principle, you could shove an extension in Bundle.signature that conveyed additional signatures.
One of the questions you'll need to answer is "what is a prescription?". In most of FHIR, it just refers to the MedicationRequest resource (or DeviceRequest if you're talking about glasses). However, in some environments it refers to a document that encompasses the MedicationRequest and a bunch of other stuff. The document approach comes with a price and makes interoperability and RESTful manipulation of the prescription harder, but it fits better with some system designs.
John Moehrke (Dec 15 2021 at 20:36):
The signature would not need to be limited to Bundle.signature. Provenance.signature can sign anything, anytime, for any reason, by anyone. There can be multiple signatures in each Provenance (e.g. prescriber signature, and overseer counter signature). There can be multiple Provenance instances (e.g. same use-case, just done a different times).
Last updated: Apr 12 2022 at 19:14 UTC
