ESBD_File_341038_Addendum 2 - Vendor Questions Cont. - RFP 739-SL3551742.pdf

REQUEST FOR PROPOSALS

Remote Patient Monitoring Solution

Addendum No. 2

RFP 739-SL3551742

Addendum No. 2

Remote Patient Monitoring Solution

RESPONSE TO QUESTIONS CONTINUED

The following responses to participant questions are fully incorporated into the Request for Proposals 739-SL3551742.

Question TTUHSC Response

1. In section 5.4, pertaining to software and services specification, there is a section of web application development which have questions and guidelines related to web application development along providing the application source code. “Periodically, the Texas Tech University Health Sciences Center (TTUHSC) engages third party vendors….” Is this section applicable on the RFP for Remote Patient Monitoring solution and Digital front door solution?

• If an app or piece of equipment is to connect to a TTUHSC network, it must meet the requirements in this section

2. Proposer shall demonstrate evidence of certifications, permits, licenses and insurances as appropriate to provide the Software and Services as required. For this minimum qualification requirement what sort of permits, licenses and insurance information is being sought by TTUHSC?

• Proposer must meet IT requirements as required as well as TX-RAMP certification as required

3. For the following two minimum requirements: 1- Proposer is current with the State of Texas Comptroller of Public Accounts (if applicable) 2- Proposer can provide Certificate of Franchise Tax status. (if applicable) we are currently registered in Florida, will it be applicable to us?

• The RFP is open to parties inside and outside the State of Texas. Proposers need only ensure they carry no holds with the State of Texas as this will prevent TTUHSC from doing business with that entity.

4. As an option, can we have a cellular Gateway connecting the devices like BP, Weight Scale etc.? This would reduce the overall cost, connectivity issues, excellent patient experience

• As outlined in the RFP Section 5.4, page 14, devices must “have direct cloud connectivity without the need for additional hardware”

5. Please explain on the process to data for patients who do not have a smartphone

• As previously addressed in Addendum 1, question 11, “The patient will have an account they can log into via their smartphone, laptop, or other internet enabled device.”

6. Please expand upon “Nurse on demand integration” • We are open to creative solutions which may include vendor’s monitoring service/care team to make use of an escalation tree that provides a pathway for on-demand, clinical triage by a licensed professional.

7. Please expand upon “Full patient recruitment, enrollment, and onboarding”

• As previously addressed in Addendum 1 o Question 5, “Once the patients have been identified by TTUHSC and the list provided to the vendor, a process for contacting the patients will be agreed upon and may include a phone call, SMS, email, and mail. Identified patients will receive a letter from TTUHSC notifying of eligibility. The letter should be sent prior to the vendor contacting the patient.”

o Question 43, “The process will need to be flexible based on site location.”

o Question 53, the “specific timelines will be determined once the program foundations and process are built.”

8. Can we use FDA-approved devices? • FDA approved devices is preferred.

9. Are you looking for a SaaS solution or an on-premise solution?

• We would prefer a SaaS solution (cloud).

10. Does the tech stack need to be Microsoft-based solution? Can we adopt other suitable technology?

• We are open to creative and secure solutions so long as integration and SSO are still feasible without any additional barriers.

11. What are the TTUHSC IT policy definitions? • https://www.ttuhsc.edu/it/request-for-proposal/technical.aspx

12. If a SaaS-based solution is acceptable, should it be a dedicated hosted solution?

• For security reasons, it must be a dedicated hosted solution.

13. Student Education Records (FERPA): Is this a general guideline?

• Only required if applicable

14. Do we need all Compliance Certifications (, HIPAA, PCI DSS, FERPA, ISO 27001, NIST/FISMA) -- ?

• Only required if applicable

15. Is a version of Hitrust required? (e1, i1, r2) • Hitrust is preferred but not required

16. SOC 2: Can we have either one (SOC2 or Hitrust)? • Both certifications show the security maturity level of a vendor and will be relevant in our decision making.

17. Under Minimum requirements We are Delaware C- Corp. Do you want us to register with the State of Texas before we are awarded?

• See question 3

18. Is this RFP for all 5 cities/campuses systemwide? • The RFP pertains only TTUHSC and its locations (will not include the rest of the TTU System)

19. How many EMR platforms/names to be integrated? • As previously addressed in Addendum 1, question 6, “Cerner, “IDX (Lubbock and Odessa) and Allscripts (Amarillo),” Cerner, Epic and possibly others yet to be identified.

20. Can we do integration of EMR systems one by one? • This will be outlined in the project plan.

21. Please expand upon “Patient Eligibility Analytics” • We are open to all eligibility analytics that could be used to improve patient outcomes and address health disparities.

22. Please expand upon “AI Analytics”. What are you expecting to visualize?

• We are open to all AI analytics that could be used to improve patient outcomes and address health disparities.

23. Please expand upon “integration with digital health apps” Which apps?

24. Will we get support from the APP author if we run into a problem?

• We want to ensure that integration with digital health apps in the future, a specific app has yet to be identified.

• No relevant at this time

25. Please explain the HUB Subcontracting plan • HSP is not required, but is an option if a proposer will be subcontracting any work

26. Please explain the Form 1295, ethics commission • Previously addressed in Addendum 1, question 29, “In 2015, the Texas Legislature adopted House Bill 1295, which added section 2252.908 of the Government Code. The law states that a governmental entity or state agency may not enter into certain contracts with a business entity unless the business entity submits a disclosure of interested parties (Form 1295) to the governmental entity or state agency at the time the business entity submits the signed contract to the governmental entity or state agency. The Texas Ethics Commission has adopted rules requiring the business entity to file Form 1295 electronically with the Commission.”

More info:

https://www.ethics.state.tx.us/resources/FAQs/FAQ_Form1295.php https://www.ttuhsc.edu/it/request-for-proposal/technical.aspx https://www.ethics.state.tx.us/resources/FAQs/FAQ_Form1295.php

27. Please expand upon “Register with the State of Texas and be current”

• See question 3

28. Can we substitute noninstitutional references like clinic etc for the “3 references of current institutions as clients” requirement

• Please do your best to provide 3 relevant references.

29. Please expand upon “24/7 coverage” • See question 6

30. Please expand upon “Computer recycling program” • Included in RFP Appendix A, page 21

31. Please expand upon “TTUHSC prefers Single Sign On integration using Security Assertion Markup Language (SAML) 2.0 or Central Authentication Service (CAS)”

• As stated TTUHSC IT’s 5.4 Software and Services Specifications, “TTUHSC prefers Single Sign On integration using Security Assertion Markup Language (SAML) 2.0 or Central Authentication Service (CAS).”

• https://www.ttuhsc.edu/it/request-for-proposal/technical.aspx

32. Please expand upon “Any APIs or Web Services that are available”

• Only required if applicable

33. Which departments will implement the RPM? • This is not available at this time.

https://www.ttuhsc.edu/it/request-for-proposal/technical.aspx