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

How does an app notify the payer system

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Execution of CQL [deprecated]
    • Hide

      We will define an operation that SHOULD be supported by payers and DTR application and allows submission of issues encountered when working with DTR-provided artifacts.  The operation will pass the Questionnaire and an OperationOutcome detailing the issue(s) including where the error occurred.  The OperationOutcome SHALL NOT contain information about the response or information retrieved from FHIR APIs that could potentially include PHI.  The OperationOutcome SHOULD include information on the DTR application identity and version, date-time with time-zone offset, as well as the provider endpoint during which the error occurred. 

      Show
      We will define an operation that SHOULD be supported by payers and DTR application and allows submission of issues encountered when working with DTR-provided artifacts.  The operation will pass the Questionnaire and an OperationOutcome detailing the issue(s) including where the error occurred.  The OperationOutcome SHALL NOT contain information about the response or information retrieved from FHIR APIs that could potentially include PHI.  The OperationOutcome SHOULD include information on the DTR application identity and version, date-time with time-zone offset, as well as the provider endpoint during which the error occurred. 
    • Bob Dieterle / Greg White: 18-0-0
    • Enhancement
    • Compatible, substantive

    Description

      "The app SHOULD log failures and ensure the maintainer of the CQL/Questionnaire package is notified."

      How, exactly, is an app to do this? 

      You can't POST an OperationOutcome (as the spec proposes).  OperationOutcome isn't a persistable resource.

      Do we expect the app's CapabilityStatement expose a contact email and the app to automatically send to it?  Every time it hits the error?  (The app won't have state, necessarily, so it'd be hard to avoid.)  If we set an expectation, we need to explain how it'll be done - and it has to be one supported by the FHIR spec, or at least enabled by it.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: