Patients not receiving coverage restriction information. This information needs to be shared with patients.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • US CARIN Real-time Pharmacy Benefit Check (RTPBC) (FHIR)
    • Pharmacy
    • Consumer vs provider RTPBC [deprecated]
    • Consumer vs provider RTPBC
    • Hide

      Include the following clarification that coverage information is as-of the request date/time. (Per workgroup discussion of this comment) 

      [To be included in a new Implementation Guidance page]
      RTPBC response information is "point in time"
      The information contained in the RTPBC response must reflect patient cost and coverage as of the date and time the request is received. The implementation guide expects that all responses are calculated using the patient's current insurance coverage and current cost information; it doesn't enable requests for information related to future or past events.

      Show
      Include the following clarification that coverage information is as-of the request date/time. (Per workgroup discussion of this comment)  [To be included in a new Implementation Guidance page] RTPBC response information is "point in time" The information contained in the RTPBC response must reflect patient cost and coverage as of the date and time the request is received. The implementation guide expects that all responses are calculated using the patient's current insurance coverage and current cost information; it doesn't enable requests for information related to future or past events.
    • Scott Robertson / Frank McKinney : 15-0-0
    • Clarification
    • Non-substantive
    • 0.1.0

      [Not sure this is the right place to put this.] There does not appear to be any intention to inform consumers of coverage restrictions (prior authorization, step therapy, quantity limits) that may impact their ability to access a particular medication. Also, it seems that other issues that will be communicated via the prescriber-facing RTPB (locked-in prescriber, DUR edits, etc.) will not be shown to patients. This is a huge issue, as patients need to know if they will face barriers accessing a medication. It is critical that information about coverage restrictions and other issues that would prevent a patient from filling a prescription be conveyed in a consumer-facing RTPBC transaction.

      Existing Wording:

      The consumer Real-time Prescription Benefit Check (RTPBC) profile is an adaptation of an existing NCPDP standard which was designed for use in provider systems. That specification includes content such as drug utilization review (DUR) alerts and detailed adjudication information to inform a provider’s prescribing process.

      In contrast, this patient-focused version of RTPBC aims to include only the coverage and cost information that is useful and meaningful to patients.

      The table below summarizes the structure and content of the NCPDP real-time pharmacy benefit check transactions, on which consumer RTPBC is based, and which of those are pertinent in the consumer version.

      The element names, optionality and notes refer to the NCPDP transactions

      The Consumer Facing column indicates the content carried over to the consumer version described in this implementation guide.

            Assignee:
            Unassigned
            Reporter:
            Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: