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

Signature requirements clarification in 3.2.6 and 4

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CDex (FHIR)
    • 1.1.0-ballot [deprecated]
    • Patient Care
    • STU
    • Direct Query
      Signatures

    Description

      Overall it is unclear how signatures are to be support with queries where the intent is to automate gathering and responding data rather than having human involvement.  The descriptions allow for absence of a signature (in the absence of an agreement or an agreement that does not require that), but if the query is direct it seems that this would unduly burden the data source/responder to have the response signed by a person as Section 4.0.3 seems to imply.  In a task based approach, where a human being is participating in the flow already (not an automated task based approach), this could fit in the workflow where a user reviews and signs.  Suggest that the descriptions clarify more clearly who's signature is actually expected at the system level of an organization that actually has value and meaning considering that that person would not review every response manually.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbuitendijk Hans Buitendijk
            Hans Buitendijk
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: