Compatibility Mode - Inbound ePrescrbing Clearing House Transaction Services - Draft.docx

Request for Information Pharmacy Re-engineering Inbound ePrescrbing Clearing House Transaction Services

1. Introduction:

The purpose is to implement the application Inbound ePrescribing (eRx) component that provides the ability to receive inbound, electronic prescriptions (e-prescriptions) from an external provider with the ability to process, fill and dispense scripts in the Veterans Health Information Systems & Technology Architecture (VistA), and Veterans Affairs (VA) Electronic Health Records Modernization (EHRM) (Cerner Millennium), Outpatient Pharmacy (OP) modules. The contractor shall provide a certified and secure transaction service and ensure the eRx application maintains necessary and required Surescripts certification with a health care clearing house and is compliant for all message types as required by the National Council for Prescription Drug Programs (NCPDP).

This Request for Information (RFI) is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government does not intend to pay for the information submitted in response to this RFI.

2. Submittal Information:

All responsible sources may submit a response in accordance with the below information.

There is a page limitation for this RFI of 10 pages. The Government will not review any other information or attachments included, that are in excess of the 10-page limit. NO MARKETING MATERIALS ARE ALLOWED AS PART OF THIS RFI. Generic capability statements will not be accepted or reviewed. Your response must address capabilities specific to the services required in the attached PWS and must include the following:

a. Interested Vendors shall at a minimum, provide the following information in the initial paragraph of the submission:

Name of Company Address Point of Contact Phone Number Fax Number Email address Company Business Size and Status For VOSB and SDVOSBs, proof of verification in VIP.

NAICS code(s) Socioeconomic data Unique Entity ID (SAM) Data Universal Numbering System (DUNS) Number Existing Contractual Vehicles

b. Provide a summary of your capability to meet the requirements contained within the draft PWS for the following areas:

a. Does the draft PWS have enough information to submit a proposal for this work? If no, please provide your technical comments/recommendations on elements of the draft PWS that may contribute to a more accurate proposal submission.

b. Has the draft PWS provided sufficient detail to describe the technical requirements that encompass the software development and production operations support services to be performed under this effort.

c. Does this requirement support the ability to propose an innovative solution? Yes/No. Please explain.

c. The VA currently has a Memorandum of Understanding (MOU) / Interconnection Security Agreement (MOU/ISA) between VA Data Access Services (DAS) and Change Healthcare that is required to operate the Inbound eRx application. The current contractor subcontracts a third-party clearing house to transmit incoming messages into VA via VA DAS. If this clearing house is not Change Healthcare, contractor must convince VA how another potential clearing house will work with the existing Inbound eRx application.

a. This MOU/ISA is between the Contractor, the requisite subcontractor, third party clearing house, and VA DAS. The MOU documents the terms and conditions for sharing data and information resources in a secure manner. The ISA provides technical details on how the interconnection is established or maintained.

b. The Contractor shall be required to coordinate the MOU/ISA between VA DAS and subcontract, third party clearinghouse necessary to maintain the certification of connection with Surescripts. The Contractor shall work with VA DAS to ensure connectivity between Inbound eRx and the requisite clearing house.

Responses are due no later than 11:00 AM EST, June (tbd), 2024 via email to Amber Davis, Contract Specialist at amber.quivers-davis@va.gov@va.gov. Please note “Pharmacy Re-engineering Inbound ePrescrbing Clearing House Transaction Services” in the subject line of your response. Mark your response as “Proprietary Information” if the information is considered business sensitive.

See attached documents: Draft PWS RFI Pharmacy Re-engineering Inbound ePrescrbing Clearing House Transaction Services