Jan 2015 Ballot Comment #215

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered - No action required
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Security
    • (NA)
    • Hide

      Provenance is sufficient for signatures accross one or more resources. The signature element in Provenance is now a 0..*, and has exposed some of the signature elements. One of these elements exposed is the purpose for the signature (aka the role the signer played when the signature occured). This allows one to search for signatures of a specific type. Together this provides the solution requested.

      March 17, 2015; Diana Motion to close this item without further change due to the changes already on Provenance with the datatype Signature; Suzannne Seconds; Pass 5/0/0

      Show
      Provenance is sufficient for signatures accross one or more resources. The signature element in Provenance is now a 0..*, and has exposed some of the signature elements. One of these elements exposed is the purpose for the signature (aka the role the signer played when the signature occured). This allows one to search for signatures of a specific type. Together this provides the solution requested. March 17, 2015; Diana Motion to close this item without further change due to the changes already on Provenance with the datatype Signature; Suzannne Seconds; Pass 5/0/0
    • Enhancement

      Comments
      2) Add generic Signature resource that may be bound to one or more resource instances and allowing various signature roles. See proposal as inset below.

      Grahame's Comments
      How is this different to Provenance? Why not use Provenance? +see source for detailed proposal

            Assignee:
            Unassigned
            Reporter:
            Gary Dickinson
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: