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

DTR to payer security doesn't belong in CRD links section

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • CDS Hooks [deprecated]
    • Hide

      Content referenced by all three bullet will be moved to section 4.5 and adjusted appropriately.

      Show
      Content referenced by all three bullet will be moved to section 4.5 and adjusted appropriately.
    • Bob Dieterle / Isaac Vetter : 11-0-0
    • Correction
    • Non-compatible

    Description

      "A payer may secure endpoints from which the DTR process will retrieve additional artifacts to support execution"

      This has nothing to do with CDS Hooks links.  The expectations around security for retrieval of data from the payer should:

      1. Be in the section of the specification that talks about data retrieval from the payer (starting with the DTR Questionnaire operation)
      2. Be expressed as a SHALL (we need SMART app/EHR to payer communication to be secured all the time, so no reason to express this as a MAY
      3. To be precise about exactly what interfaces will be used - i.e. that we're using the operation to retrieve the Questionnaire and/or search, create and update against DocumentReference

      Please move this to the part of the spec that talks about EHR/app to payer communication and tighten the wording accordingly.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: