Attachment 24 Clarification on Questions and Answers (34. 112. 186. 203 and 282).xlsx

XLSX spreadsheet 18 KB Posted

Attached to
GLOBAL NURSE ADVICE LINE - NEXT GENERATION (GNAL-NG)
Solicitation number
HT0011-25-R-0044
Issued by

About this file

This document is a Q&A Clarification spreadsheet for the Global Nurse Advice Line - Next Generation (GNAL-NG) solicitation, addressing technical integration and system requirements for a telehealth nursing service. Key clarifications include confirmation that URAC accreditation is required at proposal submittal, integration expectations with the Military Health System (MHS) GENESIS electronic health record system, and data transfer security protocols. The government emphasized that the nursing triage capability must connect with MHS GENESIS through APIs, maintain patient data integrity, and adhere to Department of Defense security protocols, with a focus on a vendor proposal that can implement all requirements within the contract's forecasted cost and schedule.

The Q&A document provides specific insights into the contract's technical requirements, such as real-time documentation of patient encounters, connectivity with existing military health systems, and comprehensive data protection measures. The government clarified that no new patient portal is needed, and the contractor will work with the existing MHS GENESIS system. The service will provide 24/7 telehealth registered nurse triage services, customer support, care coordination, and specific administrative functions like provider locator support and Active-Duty Service Member urgent care referral submissions for eligible Military Health System beneficiaries.

View the file

Other files

File Type Posted
HT0011-25-R-0044_GNAL-NG_0017Final.pdf PDF
HT0011-25-R-0044_GNAL-NG_0017Final.pdf PDF
HT0011-25-R-0044_GNAL-NG_0016.pdf PDF
HT0011-25-R-0044_GNAL-NG_0016 Conformed Copy.pdf PDF
HT0011-25-R-0044_GNAL-NG_0015.pdf PDF
Attachment 1 Performance Work Statement (PWS) A0015.docx DOCX document
Attachment 27 Clarification on Questions and Answers (No. 34).xlsx XLSX spreadsheet
HT0011-25-R-0044_GNAL-NG_0015 Conformed Copy.pdf PDF
Attachment 21 CDRL A022 - URAC Accreditation Version 3.pdf PDF
HT0011-25-R-0044_GNAL-NG_0014.pdf PDF
Attachment 1 Performance Work Statement (PWS) A0014.docx DOCX document
HT0011-25-R-0044_GNAL-NG_0014 Conformed Copy.pdf PDF
HT0011-25-R-0044_GNAL-NG_0013 Conformed Copy.pdf PDF
Attachment 5 - GNAL Price Sheet_A0013.xlsx XLSX spreadsheet
HT0011-25-R-0044_GNAL-NG_0013.pdf PDF
Attachment 26 Questions and Answers (360 - 365).xlsx XLSX spreadsheet
HT0011-25-R-0044_GNAL-NG_0012 Conformed Copy.pdf PDF
HT0011-25-R-0044_GNAL-NG_0012.pdf PDF
Attachment 23 Monthly Calls Encounter Data (Version 2) - 28JUL25.xlsx XLSX spreadsheet
HT0011-25-R-0044_GNAL-NG_0011 Conformed Copy.pdf PDF
HT0011-25-R-0044_GNAL-NG_0011.pdf PDF
Attachment 25 Clarification on Call Data_Integration_API_and_Workflow.xlsx XLSX spreadsheet
Attachment 1 Performance Work Statement (PWS) A0011.docx DOCX document
HT0011-25-R-0044_GNAL-NG_0010 Conformed Copy.pdf PDF
Attachment 21 CDRL A022 - URAC Accreditation Version 2.pdf PDF
HT0011-25-R-0044_GNAL-NG_0010.pdf PDF
Attachment 1 Performance Work Statement (PWS) A0010.docx DOCX document
Attachment 23 Monthly Calls Encounter Data.xlsx XLSX spreadsheet
HT0011-25-R-0044_GNAL-NG_0009.pdf PDF
HT0011-25-R-0044_GNAL-NG_0009 Conformed Copy.pdf PDF
Attachment 22 Revised Responses to URAC Accreditation Questions.xlsx XLSX spreadsheet
Attachment 1 Performance Work Statement (PWS)A0009.docx DOCX document
Attachment 21 CDRL A022 - URAC Accreditation.pdf PDF
HT0011-25-R-0044_GNAL-NG_0008.pdf PDF
HT0011-25-R-0044_GNAL-NG_0007.pdf PDF
HT0011-25-R-0044_GNAL-NG_0007 Conformed Copy.pdf PDF
Attachment 20 Clarification on Call Data (Question No. 354).xlsx XLSX spreadsheet
HT0011-25-R-0044_GNAL-NG_0006 Conformed Copy.pdf PDF
HT0011-25-R-0044_GNAL-NG_0006.pdf PDF
HT0011-25-R-0044_GNAL-NG_0005 Conformed Copy.pdf PDF
HT0011-25-R-0044_GNAL-NG_0005.pdf PDF
HT0011-25-R-0044_GNAL-NG_0005 Conformed Copy.pdf PDF
Attachment 1 Performance Work Statement (PWS)A0005.docx DOCX document
HT0011-25-R-0044_GNAL-NG_0004.pdf PDF
HT0011-25-R-0044_GNAL-NG_0004_Conformed Copy.pdf PDF
Attachment 19 Clarification on Previous Answers.xlsx XLSX spreadsheet
Attachment 18 Monthly Volume and AHT V2.xlsx XLSX spreadsheet
HT0011-25-R-0044_GNAL-NG_0003 Conformed Copy.pdf PDF
Attachment 17 Additional Questions_ Answers (345 - 352).xlsx XLSX spreadsheet
Attachment 1 Performance Work Statement (PWS)A0003.docx DOCX document
Show 40 more

Latest 50 of 80 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Q&A Clarification

Question No.Document (e.g. PWS)Page No.Paragraph No.Section No.QuestionsClarification/Revision to Responses Issued in Previous Amendments
34RFP2952.212-2 EvaluationPlease confirm that the prime contractor must have the URAC accreditations at the time of proposal submittal to receive an acceptable rating.The Offeror is required to submit the URAC accreditation at the time of proposal submittal or prior to award upon request from the Government. Acceptable rating for URAC accreditation is required to be eligible for this award.
112PWS595.25.5With which "Patient Portals" does the Government expect the contractor to integrate with, which vendors own those portals (if from industry), and doe these portals have APIs available for reading/writing patient record information?There will be no integration with any DoD Systems. MHS GENESIS Portal access will be provided.

For clarity, this solicitation is not a request for a new patient portal. The Military Health System (MHS) patient portal is already provided through the existing electronic health record (EHR), MHS Genesis. Consequently, no integration with a new portal is needed. We anticipate, however, that the proposed nursing triage capability will require connectivity with MHS Genesis, likely through the use of Application Programming Interfaces (APIs).

186 RFP 3rd bullet under "Sub-Factor 2e- First Contact Resolution (FCR)" Sub-Factor 2e- First Contact Resolution (FCR) The RFP evaluation for First Contact Resolution last bullet states " The solution must be interoperable with MHS GENESIS to support real-time documentation and clinical continuity."

Can the government clarify if real time indicates sending documentation at the end of a finalized encounter?Yes, real-time documentation and clinical continuity absolutely includes documenting patient care at the end of a finalized encounter. While real-time documentation involves capturing information throughout the encounter, the end-of-encounter summary is a critical element for tying everything together and ensuring clinical continuity. It's the final piece that completes the picture of the patient's care.
203PWS7all1.6Can the government clearly outline which systems (e.g. DEERS, MHS Genesis, MHS Patient Portal, Government Enterprise System) require integration to be completed by Transition In completion, and which ones are only required for Option 1 Government Enterprise System or Option 2 COTS System.The government anticipates that the proposed nursing triage capability will require connectivity with MHS GENESIS, likely through Application Programming Interfaces (APIs). The government's priority is receiving a viable vendor proposal that includes an implementation timeline addressing all requirements within the forecasted cost and schedule outlined in the PWS (contract length), regardless of whether this integration can be achieved during the transition-in period or within the optional CLIN delivery timeframe.
282PWS59105.25.2.2Please clarify which specific data transfers are contemplated where the contractor is responsible for adhering to security protocols and maintaining patient record integrity? Specifically, please confirm whether this refers solely to eligibility verification interactions with DEERS, or if additional data transfers (e.g., between MHS GENESIS, administrative management systems, patient portals, reporting systems, or telephony systems) are also expected under this requirement.Within the Military Health System (MHS), the contractor is obligated to protect sensitive patient data during all data transfers, ensuring alignment with clinical workflows and use cases, irrespective of the specific systems utilized. This requires adherence to established DoD security protocols (including encryption, access controls, authentication, and compliance with regulations like HIPAA) and maintaining the integrity of patient records by ensuring data accuracy, completeness, consistency, validity, and protection from unauthorized modification.

File details come from the government source that posted it. Updated .