Suggest to name a single submission option instead of multiple so that everyone implements the same thing…

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US CARIN Real-time Pharmacy Benefit Check (RTPBC) (FHIR)
    • Pharmacy
    • Submission method [deprecated]
    • Hide

      This and other feedback suggests limiting to a single submission method. Resolve by supporting only $process-message. A benefit of FHIR messaging is that the MessageHeader can contain metadata to support multi-hop routing, which is common in this domain, while still supporting synchronous processing.

      On Submission_method.html:

      • remove the note about eliciting comments on messaging vs. $submit options
      • Remove entire $submit section incl. example references
      • remove "(Option)" from $process-message section
      • add the following text:
        The response in the RTPBC exchange is expected to be synchronous, with real-time response times to support use in interactive patient-facing applications.

      On the Examples page (other.html), remove the examples:

      • Bundled RTPBC request to payer/PBM. Using $submit operation
      • Bundled RTPBC response from payer/PBM. Using $submit operation
      Show
      This and other feedback suggests limiting to a single submission method. Resolve by supporting only $process-message. A benefit of FHIR messaging is that the MessageHeader can contain metadata to support multi-hop routing, which is common in this domain, while still supporting synchronous processing. On Submission_method.html: remove the note about eliciting comments on messaging vs. $submit options Remove entire $submit section incl. example references remove "(Option)" from $process-message section add the following text: The response in the RTPBC exchange is expected to be synchronous, with real-time response times to support use in interactive patient-facing applications. On the Examples page (other.html), remove the examples: Bundled RTPBC request to payer/PBM. Using $submit operation Bundled RTPBC response from payer/PBM. Using $submit operation
    • Scott Robertson / Frank McKinney : 15-0-0
    • Clarification
    • Compatible, substantive
    • 0.1.0

      Suggest to name a single submission option instead of multiple so that everyone implements the same thing. Optionality decreases the chances of two systems being interoperable.

      Existing Wording:

      Two submission options are listed

            Assignee:
            Unassigned
            Reporter:
            Daniel Zhang
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: