Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-16519

Bundle -- move signatures to Meta

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • MetadataResource
      Bundle
      Provenance
    • 2.34.3
    • Hide

      This has been open for two years without a clear use case or way for us to make a decision. We're going to close, but please feel free to re-open an issue with details on supporting use cases if this is a still a concern.

      Show
      This has been open for two years without a clear use case or way for us to make a decision. We're going to close, but please feel free to re-open an issue with details on supporting use cases if this is a still a concern.
    • Rick Geimer / Jeff Brown: 12-0-1

    Description

      Normative Ballot.

      I suggest that Bundle.signature (and Provenance.signature) are removed and added to Meta – so they would become Bundle.meta.signature and Provenance.meta.signature, respectively.

      This would allow for the signing of any resource type in the future, and puts metadata where it belongs (in meta).

      I would also suggest adding a new common search parameter called _signature which would target Resource.meta.signature.who[x] and Resource.meta.signature.onBehalfOf[x].

      Attachments

        Activity

          People

            Unassigned Unassigned
            jwalonoski Jason Walonoski
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: