Inactive

07 Nov 2025 Revised to answer additional industry questions. 05 Nov 2025 Revised to answer industry questions and extend submission due date to Thursday, November 13, 2025, at 12:00 PM EST. 04 Nov 202... 07 Nov 2025 Revised to answer additional industry questions. 05 Nov 2025 Revised to answer industry questions and extend submission due date to Thursday, November 13, 2025, at 12:00 PM EST. 04 Nov 2025 Defense Health Agency (DHA), Contracting Activity (DHACA) – Defense Healthcare Management Systems Contracting Division (DHMS-CD) in support of the Program Executive Office – Defense Healthcare Management Systems (PEO DHMS), Defense Healthcare Management System Modernization (DHMSM) Program Management Office (PMO), is seeking industry feedback on the below request. Background The Department of Defense (DoD) Healthcare Management System Modernization (DHMSM) program was established to acquire and field a configurable and scalable modernized Electronic Health Record (EHR) System to replace DoD legacy healthcare systems with an Off-the-Shelf (OTS) EHR system that enables improved sustainability, flexibility, interoperability, and improved continuity of care. In support of this mission, the DHMSM Program acquired an integrated inpatient/outpatient EHR solution known as Military Health Systems (MHS) GENESIS® that allows for access to and sharing of common data, common user interfaces, common workflows, and common business rules to the greatest extent possible.?? DHMSM’s responsibilities have expanded significantly since it was established in 2013. As MHS GENESIS has identified other areas of transformation, the department chartered DHMSM to support an expanded portfolio of products, and it now manages several clinical applications to support MHS GENESIS patients through the full continuum of care. MHS GENESIS functions as a system of systems by integrating commercially available, off-the-shelf (COTS) EHR components from multiple vendors (e.g., Oracle Health, Henry Schein). This integration, combined with its enormous scale, creates a high level of complexity. The solution is comprised of 12 major subsystems, utilizes 81 interfaces across more than 1,000 end points, and processes at least 20 million messages daily. MHS GENESIS has more than 975 workflows and more than 200 user roles, and it serves 194,000 users and 9.6 million beneficiaries across 137 commands globally. MHS GENESIS is also used by additional federal partners beyond DoD. Currently, the United States Coast Guard (USCG), the Reserve Components (RCs), the United States Military Entrance Processing Command (US MEPCOM), and National Oceanic and Atmospheric Agency (NOAA) use MHS GENESIS to document health care. The full deployment of MHS GENESIS was completed in March 2024, but there remains interest in expanding its use to other federal agencies. To facilitate this broader adoption and ensure successful "go-live" transitions, a proven "white-glove" (meticulous) deployment methodology, such as the one developed by Leidos, is essential. This approach offers comprehensive, on-demand support, including site preparation, deployment, training, change management, and post-installation assistance, minimizing disruption to existing healthcare operations. The Government is seeking industry feedback to address the following: Describe your “white-glove” deployment approach for MHS GENESIS that minimizes disruption to existing healthcare operations. For organizations without prior MHS GENESIS deployment experience, detail your proposed methodology for acquiring the necessary knowledge and skills to effectively support your deployment approach. Specifically address how your organization would minimize reliance on government resources while ensuring a rapid and comprehensive understanding of the MHS GENESIS environment. Include anticipated challenges and corresponding mitigation strategies. Describe your strategy for rapidly assembling and training a dedicated team to execute your “white-glove” MHS GENESIS deployment methodology, considering that deployments may not occur on a consistent basis and may be OCONUS. Describe your methods for maintaining team proficiency during periods of inactivity and for addressing unique challenges associated with international deployments, ensuring consistent performance across all deployments. Identify potential risks associated with the implementation of your on-demand 'white-glove' MHS GENESIS deployment solution, and detail mitigation strategies to address these risks. Instructions for Submission Submit responses no later than Thursday, November 6, 2025 at 4:00 PM EST to: dha-dhms-cd@health.mil. Include in the Subject Line the following: Company name and Deployment Solutions. In the submission please include: Cover page: Company name, Cage Code, Sam Unique Entity ID (UEI), point of contact, small business concern (if applicable), document names of any additional documents as part of this submission, and permission/ rejection of release or proprietary information to identified subcontractors (see below) RFI Response: For each question, limit response to no more than three (3) pages in Word or 8 slides in PowerPoint. Font should be no smaller than 12-point font. Submissions should clearly articulate the question being addressed. For ease of navigation a one (1) page table of contents may be added and will not count towards the page limitation. Submissions may be converted into a *.pdf but the same restrictions apply. Proprietary information may be submitted; however, RFI respondents are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response.? If a submission is marked, it will be protected from disclosure outside of Government personnel, unless permission is granted for Government support contractors to view the material. The following companies and individual employees are bound contractually by Organizational Conflict of Interest and disclosure clauses with respect to proprietary information, and they will take all reasonable action necessary to preclude unauthorized use or disclosure of an RFI respondent’s proprietary data.? RFI responses?MUST?clearly state whether permission is granted allowing the support contractors identified below access to any proprietary information. Boston Consulting Group (BCG) Swing Tide Andrew Morgan Consulting, LLC? Greenlight Analytic, LLC Monterey Consultants, INC This RFI is not a solicitation.??This RFI is for planning purposes only.? It does not constitute an RFP or a promise to issue an RFP in the future.? This RFI does not commit the Government to contract for any supply or service whatsoever.? Further, the Government is not seeking proposals at this time and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in response to this RFI. ?All costs associated with responding to this RFI will be solely at the responding party’s expense.? Participation is not mandatory or required; participation or response to this RFI is not a prerequisite for any future procurement activities.?