ESBD_File_350871_HHS0014057_HHSC Response to Solicitation Questions.pdf

RFO No. HHS0014057 Page 1 of 8

Solicitation Title: Patient Assistance Program Navigation Software

Solicitation Number: HHS0014057

HHSC Response to Solicitation Questions

Question # Reference Vendor Question Response

1. RFO, Page 7

Section 1.1 (Executive Summary)

"Prior to award of the Contract, Respondent must obtain TX- RAMP Level 2 certification or TX-RAMP Provisional Certification."

Does StateRAMP Authorization satisfy this requirement?

Refer to RFO Section 1.2 (Definitions), Texas Risk and Authorization Management Program (TX-RAMP) | Texas Department of Information Resources https://dir.texas.gov/information-security/texas-risk-and-authorization-management-program-tx-ramp https://dir.texas.gov/information-security/texas-risk-and-authorization-management-program-tx-ramp https://dir.texas.gov/information-security/texas-risk-and-authorization-management-program-tx-ramp https://dir.texas.gov/information-security/texas-risk-and-authorization-management-program-tx-ramp https://dir.texas.gov/information-security/texas-risk-and-authorization-management-program-tx-ramp

RFO No. HHS0014057 Page 2 of 8

Question # Reference Vendor Question Response

2. RFO, Page 16

Section 2.3.1 (Functional Requirements)

Item "h. Be available in both English and Spanish; and ensure questionnaire availability in both English and Spanish."

Does this mean that the entire solution must be available in English and Spanish? Or does this only refer to the questionnaire?

Refer to Addendum No. 3 to the Solicitation.

3. General Question Do we need to comply with HIPAA Compliance as the requirement is related to the healthcare industry?

Yes, refer to RFO Section 2.3 (Solution Requirements) and Exhibit L, HHS Information Security and Privacy Requirements.

4. General Question Do we need to use third-party APIs for SSN verification?

No, it’s not a requirement that SSNs are verified by third-party APIs.

5. General Question Do we need to use a third-party API for Insurance verification?

No, since eligibility varies by prescription assistance application, it is not a requirement that insurance is verified by third-party APIs.

RFO No. HHS0014057 Page 3 of 8

6. General Question System will have a list of Advocates, other partners as well? If yes, what will be the role of these users?

The system will house all user types. Roles are defined in RFO Section 2.2.2 (User Base). It’s expected that there will be four general types of users – HHSC, Organizations, Site Managers, and Navigators. Advocate can be used synonymously with Navigator.

Refer to Addendum No. 3 to the Solicitation.

RFO No. HHS0014057 Page 4 of 8

7. General Question Will PAP org be able to create multiple Users with different roles & access under its portal?

Question answered with assumption that “PAP org” is referring to “Organization User” as described in RFO Section 2.2.2 (User Base). Yes, application should be able to manage user roles and access.

Vendor must build user access and permissions, see RFO Section 2.3(e) (Solution Requirements) and RFO Section 2.4.3 (Security and Compliance), Table 4, COM-18.

RFO No. HHS0014057 Page 5 of 8

8. General Question Will the Navigator be created by the client (Super Admin) and then will be assigned to one or more PAP organisations?

Yes, Navigator can be created and assigned to one (1) or more PAP Organizations by Client (Super Admin). Question answered with assumption that “PAP organizations” is referring to “Organization User” as described in RFO Sec 2.2.2 (User Base).

Application should be able to manage user roles and access.

Vendor must build user access and permissions, see RFO Section 2.3(e) (Solution Requirements) and RFO Section 2.4.3 (Security and Compliance), Table 4, COM-18.

RFO No. HHS0014057 Page 6 of 8

9. General Question How will the Navigators be managed by the organisations if they will be created by the Super Admin?

Per RFO Section 2.3(e) (Solution Requirements), the solution will provide role-based security provisioning that conditions the levels of access available to different categories of Users.

Vendor must build user access and permissions, see RFO Section 2.3(e) (Solution Requirements) and RFO Section 2.4.3 (Security and Compliance), Table 4, COM-18.

10. General Question Do you need the whole solution in both English and Spanish or only the Review questionnaire should be in both English and Spanish?

Refer to Addendum No. 3 to the Solicitation.

11. General Question Whether companies from Outside USA can apply for this? (like,from India or Canada)

Please refer to Exhibit A, HHS Solicitation Affirmations, v2.4 (#50).

RFO No. HHS0014057 Page 7 of 8

12. General Question Whether we need to come over there for meetings?

Refer to Addendum No. 3 to the Solicitation.

13. General Question Can we perform the tasks (related to RFP) outside USA? (like, from India or Canada)

Refer to Article VI of Exhibit B, HHS Uniform Terms and Conditions – Vendor, v3.4, prohibit removal of State Property from the continental United States and use of any computing device to access System Agency’s network or e- mail while outside of the continental United States.

Refer to Exhibit C, HHS Data Use Agreement, v8.5.

14. General Question Can we submit the proposals via email? No, please refer to RFO Section

3.6.2 (Submission Options).

RFO No. HHS0014057 Page 8 of 8

15. General Question I took a look at the RFP and was wondering whether Texas Health and Human Services has an existing database of these 350+ existing manufacturer Patient Assistance Programs (PAPs) that we can use to setup this SaaS solution or is it our responsibility to find and identify these programs in addition of creating the SaaS solution

HHS does not have a database of all existing PAPs.

As described in RFO Section 1.1 (Executive Summary), the system should contain a central repository or library of available drug manufacturer and third-party prescription assistance programs.

The expectation is that the solution already has the information repository and experience in prescription assistance program navigation created and maintained by the vendor.