QA HT001521R0016 Secure Messaging.xlsx
XLSX spreadsheet 17 KB Posted
- Attached to
- DHA - Secure Messaging Federal contract opportunity
- Solicitation number
- HT0015-21-R-0016
- Issued by
- Defense Health Agency
About this file
This document contains questions from potential offerors regarding a solicitation for a Secure Messaging Software as a Service. The Defense Health Agency is seeking proposals to acquire a HIPAA-compliant secure messaging solution as a subscription service to allow patients and care teams to communicate asynchronously within the TRICARE Online Patient Portal. Key capabilities must include real-time messaging, file sharing, and video/voice sessions. The solution must integrate with the Defense Manpower Data Center for single sign-on and be deployed in a DoD Risk Management Framework compliant environment. Subscriptions will decrease over time as capabilities transition to the MHS GENESIS electronic health record system. Clearances are required for personnel with access to DoD protected health information performed within the United States. Offerors should propose a solution meeting all requirements and address costs for obtaining necessary clearances.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| HT0015-21-R-0016 Amendment 3.pdf | ||
| SM SaaS PWS- 23 Feb 2021v2.3.docx | DOCX document | |
| HT0015-21-R-0016 Solicitation.docx | DOCX document | |
| HT0015-21-R-0016 Amendment 1.docx | DOCX document | |
| HT0015-21-R-0016 Amendment 2.docx | DOCX document | |
| HT0015-21-R-0016 Secure Messaging Conformed Solicitation.docx | DOCX document | |
| Secure Messaging Price Proposal Pricing Sheet - 09 March 2021.xlsx | XLSX spreadsheet | |
| SaaS Past Perf Questionnaire HT0015-21-R-0016.doc | DOC document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| VENDOR QUESTIONS | CUSTOMER RESPONSE | |
| 1 | Could you provide additional requirements/use cases for the Secure Messaging SaaS features and capabilities. A few examples below: |
i. Real-time send/receive 2-way messages between the users and the health providers;
ii. Download/upload and share files/charts/documents; and
| iii. Real-time live video and voice sessions | Government Intent to acquire Secure Messaging Software as a Service (SaaS) product. Accordingly, Offerors are requested to describe their product's features and capabilities to be evaluated by Government. | ||
| 2 | Could you share reasons for the significant change of licenses/subscriptions, from 8600 (BaseFY21) to 1000 licenses (Option7-FY24)? | ||
| Also, are they total licenses for each of the Option period? | "TOL PP SM SaaS capabilities will be incrementally assumed by the MHS GENESIS Patient Portal. As MTFs adopt this new capability, the use of TOL PP SM SaaS will be discontinued at those sites." [PWS Section 1.3] "The Government intends to decrease the SM SaaS subscriptions as MHS GENESIS goes live at a MTF" [PWS Section 5.1.2] | ||
| 3 | Section C.PWS 5.1.3 – Our understanding is that the proposed SaaS Secure Messaging will need to be integrated with Sign on (SSO) using the Defense Manpower Data Center (DMDC) DS Logon Methodology. We support integration with 3rd party SSO via standard APIs. Are you able to share relevant specification of the DMDC SSO to allow us to review and scope integration technical efforts? | "The contractor shall establish and maintain a sign on (SSO) link for SM SaaS using the Defense Manpower Data Center (DMDC) DS Logon authentication methodology" [PWS Sec 5.1.5] DS Logon managed by DMDC. Refer to DMDC website for additional information: https://www.dmdc.osd.mil/ | |
| 4 | Section D. PWS 5.1.11 – Could your provide clarification for the following “Contractor shall support MHS GENENSIS Patient Portalfielding by disabling the SM SaaS capability by the DHMSMS go-live schedule”? | "TOL PP SM SaaS capabilities will be incrementally assumed by the MHS GENESIS Patient Portal. As MTFs adopt this new capability, the use of TOL PP SM SaaS will be discontinued at those sites." [PWS Section 1.3] | |
| 5 | Section A. PWS1.11 – Do key personals MUST possess requisite security clearance? Our HIPAA compliant Secure Messaging solution is completely cloud SaaS based and will need no physical entry to setup, implement and to go-live. Travel to any physical location only required for in-person training. | Yes, Automated Data Processor/Information Technology (ADP/IT) security clearances are required to ensure contractor personnel are designated as ADP/IT-I, ADP/IT-II, or ADP/IT-III where their duties meet the criteria of the position sensitivity designations. Ref PWS Sections 2.3 and 5.3.3. | |
| 6 | Page 2 Addendum 2 : 52.212-1 (a) – It looks to us that the definition of a small business size standard for this solicitation is a company that has less than 500 employees. We appreciate additional clarification on the definition of the small business size for this solicitation. We are US-based with global presence and has less than 250 employees. Do you classify us as a small business size company? | 500 is a typo. For NAICS Code 541519, "Information Technology Value Added Resellers," the Small Business standard is 150 employees per the SBA. This will be corrected though a modification. | |
| 7 | The Tricare Online Patient Portal (TOL PP) Secure Messaging (SM) is a Software-as-a-Service (SaaS), and a commercial subscription product that cannot be separated into a traditional prime/subcontract role. Would the DHA consider revising the small business participation commitment to reflect 30.06% of labor, rather than 30.06% of Total Contract Value? (2.4 Part 4 Small Business Participation Commitment) | 30.6% of total is the lowest level of small business participation the Small Business Administration will accept. | |
| 8 | Can the DHA provide more information about the number of MTFs expected to be supported and the countries and time zones in which they operate? (PWS 1.4 Scope) | PWS Sec 1.3. MHS currently includes 55 military hospitals and 373 military medical clinics. Supported facilities (MTFs) are located around the world in multiple time zones. Additional info can be located at https://www.health.mil/. This Secure Messaging SaaS acquisition does not include support at MHS GENESIS Sites. | |
| 9 | PWS 1.11 states that key personnel must possess requisite security clearances and that Offerors must address the entire team. Does this mean that all engineers and administrators, with elevated system privileges to the system (containing DoD PHI data) are required to obtain or possess security clearances? (PWS 1.11 Key Personnel (Contractor)) | Ref PWS Sections 2.3 and 5.3.3. | |
| 10 | In regards to personnel identified as requiring a clearance, will the DHA provide agency funding to facilitate the DoD clearance process including any necessary field interviews and background checks? (PWS 1.11 Key Personnel (Contractor)) | No. Offeror costs to acquire the required Automated Data Processor/Information Technology (ADP/IT) security clearances should be addressed within their pricing. | |
| 11 | PWS 5.1.1 describes that the infrastructure with DoD/MHS data, must be segmented from commercial/non-MHS data. Does this mean that commercial and DoD data and infrastructure must be physically segregated? (PWS 5.1.1 Core Tasking) | Yes, DoD/MHS data must be segmented from commercial/non-MHS data in accordance with the DoD Risk Management Framework (RMF) guidelines. | |
| 12 | PWS 5.1.2 with regards to help desk and call center related work access to DoD patient PII, is there a requirement that such activities must be performed by U.S. Citizens and within the United States? (PWS 5.1.2 Core Tasking) | Yes, such activities must be performed by U.S. Citizens within the United States. | |
| 13 | PWS 5.1.3 defines SSO support with potential development work which is not scoped out with regard to time and resources. Will the DHA consider a future modification to fund this effort separately at additional cost or should the development work be estimated and included as part of the proposal? (PWS 5.1.3 Core Tasking) | SSO is required to be included as part of the Offeror's proposal. | |
| 14 | PWS 5.1.3 defines SSO connectivity with the TOL website as a requirement. Is an ATO required prior to commencing SSO? (PWS 5.1.3 Core Tasking) | "The contractor shall provide a secure HIPAA-compliant, DoD RMF approved, web-based SaaS infrastructure with DoD/MHS data segmented from commercial/non-MHS data." [PWS Sec 5.1.1] | |
| 15 | PWS 6.4.2 states that the solution shall not access DoD data or connect to DoD systems before undergoing the C&A process. How is a full performance start of 30 July 2021 possible if certification and accreditation is required before processing DoD data? Will the system be permitted to hold and collect DoD PHI data before undergoing this process? (PWS 6.4.2 Privileged User Requirements (Electronic Security)) | Offeror to propose solution meeting PWS requirements in section 6.4.2/Electronic Security and other Risk Management Framework (RMF) compliant DoD environment requirements. | |
| 16 | Section 1.3 states that the TOL PP SM SaaS capabilities will be incrementally assumed by the MHS GENESIS Patient Portal. As MTFs adopt this new capability, the use of TOL PP SM SaaS will be discontinued at those sites. The MHS Genesis implementation schedule is managed by the Defense Healthcare Management System Modernization (DHMSM) Program Office, and subject to change. Does this mean that the MHS Genesis Solution already has a HIPAA- compliant asynchronous messaging capability of its own and that what ever solution that is chosen via this solicitation will be abandoned when the Genesis solution is ready? Or does this mean that only the portal for accessing the HIPAA- compliant asynchronous messaging capability will change/ transition from the TOL Patient Portal to the MHS Genesis Portal? | "TOL PP SM SaaS capabilities will be incrementally assumed by the MHS GENESIS Patient Portal. As MTFs adopt this new capability, the use of TOL PP SM SaaS will be discontinued at those sites." [PWS Section 1.3] "The Government intends to decrease the SM SaaS subscriptions as MHS GENESIS goes live at a MTF" [PWS Section 5.1.2] |
File details come from the government source that posted it. Updated .