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

CDex documents require signature, but don't explain how used

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci CDex (FHIR)
    • 0.1 [deprecated]
    • Patient Care
    • Profiles [deprecated]
    • Hide

      1) Add Section on how to request and return signed data for all three method of CDEX data exchange (direct query, task-based requests, and new draft Push mechanism section -see FHIR-33139)

      2) Provide documentation on how to sign and verify signed FHIR artifacts.

      Show
      1) Add Section on how to request and return signed data for all three method of CDEX data exchange (direct query, task-based requests, and new draft Push mechanism section -see  FHIR-33139 ) 2) Provide documentation on how to sign and verify signed FHIR artifacts.
    • Eric Haas/Jay Lyle: 8-0-1
    • Enhancement
    • Compatible, substantive

    Description

      In the 'document' profile, we say that Bundle.signature is mustSupport, but we don't provide any guidance about what elements within signature must be present, whether support for digital signatures are required, etc.  If we're going to say that signatures must be supported, we need to be clear as to 'how'.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: