2015May core #98 - More documentation for "cert"

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Structured Documents
    • Composition
    • 6.9.14.1
    • Hide

      Remove this and leave a note that signature generation is an open issue for DSTU 2

      Show
      Remove this and leave a note that signature generation is an open issue for DSTU 2
    • Calvin Beebe / Brett Marquard: 29-0-2
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Comment:

      The "cert" parameter requires more documentation to indicate that it is a keychain (containing a private key). Further, an identifier for the specific Private Key may be required.

      Keychains such as this are not typically available at accessible URLs. Rather, they are embedded in devices (or operating system user profiles for us). I therefore disagree that this is a common enough item of functionality to include in the FHIR Core

      I recommend stating that if a signature is required, the client should generate it and upload it to the server and perhaps put the Private Keychain/Passphrase option in a seprate extension/profile.

            Assignee:
            Unassigned
            Reporter:
            gonatf
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: