Behavioral Health Treatment and Referral Platform Software RFR QUESTIONS AND ANSWERS.docx

Commonwealth of Massachusetts Executive Office of Health and Human Services (EOHHS)

QUESTIONS AND ANSWERS

regarding the

Request for Responses for a Behavioral Health Treatment and Referral Platform

Document Number: 22EHSBHTRPSRFR

COMMBUYS Bid Number: BD-22-1039-EHS01-EHS01-74235

Q&A Issue Date: June 15, 2022

This document contains responses to questions received regarding the Request for Responses for a Behavioral Health Treatment and Referral Platform issued on May 24, 2022, by the Executive Office of Health and Human Services (EOHHS). Answers have been provided to those questions which are of general interest and relevant to the preparation of a response to the RFR.

Q1. What legacy platforms, if any, is the Commonwealth using today to support behavioral health referrals from the emergency department (ED) to inpatient psychiatric treatment and / or community based acute treatment? What agency operates the legacy platforms? What Vendors support the legacy platforms?

A1. Emergency Services Program (ESP) providers are required to register all members seen into MABHAccess.com. This is a program run by Massachusetts Behavioral Health Partnership (MBHP), that tracks all patients residing in the ED and helps Managed Care Entities (MCEs) advocate for patients boarding.

In addition, there are state mandated protocols under the Expedited Psychiatric Inpatient Admissions Policy (EPIA) that are manual today but EOHHS is looking to automate through this initiative.

Q2. Does EOHHS have any key milestones that it is operating towards within the initial two-year term for the RFR?

A2. As set forth in Section 3 of the RFR, the initial two-year term includes all implementation, management, and operations activities. Specific dates and timelines will be made part of any executed Statement of Work. Of note, key milestones within the implementation phase include:

i. Provision, customization, and configuration of the Application to implement the functionality required to implement the statewide Behavioral Health Treatment and Referral Platform;

ii. Implementation services at the Participant Organizations (including Commonwealth Participant Organizations) including technical integration, training, and support; and

iii. Hosting and Operations of that application on a SaaS basis, including provision of a 24x7 helpdesk to address user questions and to enable emergency user authorization.

Q3. Under RFR Section 4.3.2.4, – when the RFR says “required elements” in the first item, is that referring to “Program scope & capability requirements” found in RFR Section 3.1.1?

A3. Yes, the “required elements” in the first item of RFR Section 4.3.2.4 refers to the Program scope & capability requirements found in RFR Section 3.1.1.

Q4. Under RFR Section 4.3.2.4, when the RFR says “system requirements” in the second item, is that referring to “Technical Requirements” in RFR Section 3.1.2?

A4. Yes, the “system requirements” in the second item of RFR Section 4.3.2.4 refers to the Technical Requirements in RFR Section 3.1.2.

Q5. Under RFR Section 3.2.2, is EOHHS requesting with the RFR submission that Bidders provide a system security and risk management plan be included in the response, or indication that one will be provided if the RFR is awarded?

A5. As set out in RFR Attachment 4, EOHHS Technology Office Secretariat Application Reference Manual, the Selected Bidder, once awarded, shall provide a system security and risk management plan consistent with the EOHHS application guideline.

Q6. Related to the Question #5 above, if a system security and risk management plan is to be included, does EOHHS require all forms indicated in RFR Attachment 4, EOHHS Technology Office Secretariat Application Reference Manual, also be completed and submitted by the RFR Response due date?

A6. The Selected Bidder, once awarded, will be required to submit all forms indicated in Attachment 4. No forms in RFR Attachment 4 are required at RFR Response due date.

Q7. Will EOHHS consider Bidders, including non-domiciled entities, who do not have existing interfaces or connectivity in Massachusetts?

A7. Yes, EOHHS will consider all Bidders, including non-domiciled entities. However, as set forth in RFR Section 4.3.2.4, Bidders will be evaluated based on their current state connectivity with the identified participant organizations in Massachusetts. In addition, and in order to have access to, view, and/or receive any Health Insurance Exchange/Integrated Eligibility System (HIX/IES) Program related data, Contractor Personnel must be physically located within the jurisdiction of the United States.

Q8. RFR Attachment 6 Cloud Terms Table, Data Privacy and Security Category row 1 specifies, “Cloud Solution Provider must obtain FedRAMP certification for the Solution…” Can the Commonwealth clarify if FedRAMP is required of the solution itself (e.g. a web application) or instead of the cloud provider (e.g., Amazon Web Services FedRAMP-certified environment)?

A8. No, FedRAMP certification is not required for the solution itself. The hosting facility (AWS or equivalent) must be FedRAMP certified. There are ongoing processes (monitoring/scanning for vulnerabilities, encryption at rest and in motion, etc) that are required at the application level to ensure ongoing secure operations. See https://www.fedramp.gov/ for additional information.

Q9. Will the Commonwealth be providing any internal or level 1 or level 2 (i.e., for accepting requests, routing tickets, and supporting less technical issues) help desk services as part of this project? Or is it assumed the Vendor is required to staff these help desk services?

A9. As part of the activities described in RFR Section 3.2, it is expected that the Vendor will provide these services.

Q10. What components, if any, of existing Commonwealth systems are desired for inclusion in a final solution?

A10. The Vendor key objective is for the Vendor to support the automation of the current manual EPIA process, including the features of ED behavioral health referral screening, evaluation, and referral process, enable the electronic transmission of standardized admissions information (“Admissions Packet”).

Q11. Per RFR Attachment 3, Expedited Psychiatric Inpatient Admission Protocol 3.0,, does the EOHHS desire Admission Packets be sent to inpatient providers as secure email or eFax? Or can the solution offer the admission packet data in a viewable patient record on the platform?

A11. Admission packets must be sent securely through the platform and made available for access by hospitals EDs, inpatient psychiatric hospitals, community-based crisis intervention teams, carriers, MassHealth and its MCEs, PACE organizations and DMH within a portal.

Q12. Will EOHHS provide additional time for Bidders to draft Responses to the RFR?

A12. Further to Amendment 1 to the RFR, the timetable was extended, and Responses to the RFR are now due on July 1st, 2022. Please see Amendment 1 to the RFR on COMMBUYS for additional information on the revised procurement timetable. Further to RFR Section 4.2.1, Bidders are responsible for checking COMMBUYS for amendments to this RFR. EOHHS may adjust this schedule, as it deems necessary. Further to RFR Section 4.2, any Response submitted after the deadline will not be evaluated and considered.