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

Liability and Privacy Concerns with Digital Signature

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • Signatures
    • Hide

      The requirement for signatures does not come from CDex, it comes from payers. CDex defines how the technical requirements are met.  The issues surrounding whether signatures are necessary/appropriate/useful are out of scope.

       

      Show
      The requirement for signatures does not come from CDex, it comes from payers. CDex defines how the technical requirements are met.  The issues surrounding whether signatures are necessary/appropriate/useful are out of scope.  

    • Change Request FHIR-38188 spec should be clarified that prior auth doesn't require signatures

      I'm concerned with the lack of liability and privacy information regarding digital signatures. I think we need to more carefully balance the convenience of digital signatures with their downsides (privacy, liability, enforceability, etc.). 

      I greatly appreciate the note to "*Consult with your Payer and your legal team for questions regarding legal liability associated with sharing and signing data." I'm only wondering if we can perhaps strengthen this language.

            Unassigned Unassigned
            apreisler Andrea Preisler
            Andrea Preisler
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: