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

re write section

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • 1.1.0-ballot [deprecated]
    • Patient Care
    • STU
    • Attachments
    • 3.4.5
    • Hide

      RE comment 1) Will address this with FHIR-37243

      RE comment 2)

      Remove capital case conformance Verbs ( SHALL, SHOULD ) and replace with declarative sentences  for business rules in attachments, direct-query and task-based approach signature sections :

       

      e.g.,

       

      Change

      The signature SHALL represent a human provider signature on resources attesting that the information is true and accurate.

      If the signature requirement is pre-negotiated, it SHALL be assumed that all attachments will be signed.

      Conversely, it SHOULD be assumed that no CDex Attachments transaction will be signed unless there exists a pre- negotiated agreement

       

      to 

      The signature represents a human provider signature on resources attesting that the information is true and accurate, to the best of their knowledge.(footnote)

      It is assumed that all attachments will be signed.

      Conversely, it is assumed that no CDex Attachments transaction will be signed unless there exists a pre-negotiated agreement

      add boilerplate footnote or note : "Consult with your payer and your legal team for questions reqarding legal liability associated with sharing and signing data."

      Show
      RE comment 1) Will address this with FHIR-37243 RE comment 2) Remove capital case conformance Verbs ( SHALL, SHOULD ) and replace with declarative sentences  for business rules in attachments, direct-query and task-based approach signature sections :   e.g.,   Change The signature SHALL represent a human provider signature on resources attesting that the information is true and accurate. If the signature requirement is pre-negotiated, it SHALL be assumed that all attachments will be signed. Conversely, it SHOULD be assumed that no CDex Attachments transaction will be signed unless there exists a pre- negotiated agreement   to  The signature represents a human provider signature on resources attesting that the information is true and accurate, to the best of their knowledge.(footnote) It is assumed that all attachments will be signed. Conversely, it is assumed that no CDex Attachments transaction will be signed unless there exists a pre-negotiated agreement add boilerplate footnote or note : "Consult with your payer and your legal team for questions reqarding legal liability associated with sharing and signing data."
    • Eric Haas/Jay Lyle:9-0-1
    • Clarification
    • Compatible, substantive

      Current content:

      The signature SHALL represent a human provider signature on resources attesting that the information is true and accurate.

      If the signature requirement is pre-negotiated, it SHALL be assumed that all attachments will be signed.

      Conversely, it SHOULD be assumed that no CDex Attachments transaction will be signed unless there exists a pre- negotiated agreement

      Comment:

      1) We want to make sure the human provider is not be held liable if they signed on to the information in good faith, and 2) the section on Data Requirements needs to be re-written, as these are not conformance verbs.

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: