GovChime
Notice ID: 4636674ef7914706801b2a4cd8f9c890Special Notice

MHS GENESIS Support

Archived. Original response deadline: . Full description on SAM.gov.

Overview

Response deadline
4:00 PM UTC−04:00
Posted
April 6, 2023
Notice type
Special Notice
NAICS
541512: Computer Systems Design Services
Agency
Department of WarDEFENSE HEALTH AGENCY (DHA)

Notice details

Office
DEFENSE HEALTH AGENCY
Last updated
Dec 4, 2025

Identifiers

Solicitation number
HT003823R0003
Notice ID
4636674ef7914706801b2a4cd8f9c890

Description

REQUEST FOR INFORMATION The Department of Defense (DoD) Healthcare Management System Modernization (DMHSM) Program oversees the acquisition and deployment of the DoDs new Electronic Health Record (EHR), MHS GENESIS. MHS GENESIS is an automated medical information system that supports health care administration and delivery at Department of Defense (DOD) Military Treatment Facilities (MTFs) and Theater Medicine. These MTFs include hospitals, outlying medical clinics and outlying dental clinics. Theater Medicine includes (but is not limited to) ships, submarines, hospital ships, forward resuscitative sites, theater hospitals, aeromedical staging facilities, and aeromedical evacuation teams. It provides access to authoritative sources of data to enable improved population health, patient safety, and quality of care. It supports an enhanced patient care experience and serves as a tool to maximize medical readiness for our military. MHS GENESIS unifies and increases accessibility of integrated, evidenced-based healthcare delivery and decision-making.? For the purposes of this request for information (RFI), DHMSM is assessing best business practices for (1) system and software engineering; (2) system integration; (3) installation, testing, and deployment; (4) lifecycle logistics support to include user training; (5) software release management; (6) operations and maintenance (O&M) support; and (7) business intelligence and research. Visit the interactive Genesis of MHS GENESIS timeline?to learn more about the development of MHS GENESIS and its deployment across the MHS. The hyperlink is listed below. Questions for RFI Respondents The Government seeks responses to the following questions. What are commercial best practices for EHR end user optimization? ? In your experience, what level of integration work is required for sustaining and optimizing a COTS system in a large-scale DoD enterprise? ? What are commercial best practices for operating health related system of systems in a cloud-based environment?? What scale of integration efforts has your company supported for a Major Automated information System in the Defense Department?? What are commercial best practices/standard service level agreements?for an EHR such as MHS GENESIS?incidents? ? Tell us about your technical capability to perform within the construct of a multi-billion dollars requirements like MHS GENESIS, in whole or in part. At a minimum, demonstrate your management and technical capabilities for attracting, recruiting, and retaining top-quality employees with the technical skills, and expertise and experience needed to meet such effort. Please share your technical capability as well as the supporting material that demonstrates a full understanding of the methodology and approach.? Share your knowledge of contracting vehicles that may be aligned with the governments RFI and that may provide the best value for this requirement. List the contract vehicle(s) by name, Period of Performance, Agency, Ceiling, relevant North American Industry Classification System (NAICS), and if a Prime or Subcontractor.? List any successful strategies/methodologies used to manage interoperability of data across EHR systems.?? What are commercial best practices for training and adoption of new EHR capabilities for current users? ? What is an effective commercial approach to training capabilities that require an interface with the main EHR system? For example, capabilities that require new equipment (e.g. supply chain scan gun, EHR on a tablet, signature pads, etc.) or interfaces with 3rd party systems (e.g. DEERS, external billing systems, etc.)? In this environment, what types of profit incentives are effective relating to performance?? Instructions for Submission RFI respondents are encouraged to provide responses and comments to the questions above. Responses and comments may be utilized in the development of additions or modification to future DHMSM Draft RFPs. DHMSM requests that responses to the RFI be submitted to the POC identified below by 21 April 2023. Please keep responses for the above questions to no more than 15 pages. If you choose to provide a capability statement, ensure it is within 5-10 pages. For your questions, please continue a dialogue with the DHMSM PMO and other industry partners, by creating an account at https://connect.bidscale.com/hive-hub. ? No verbal responses will be accepted. Proprietary information may be submitted; however, RFI respondents are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. All submissions will be protected from disclosure outside of the DHMSM Program Office. In addition, RFI respondents should be aware that the DHMSM Program Office may utilize contractor support personnel from the below listed companies (under existing contracts) to review responses and information submitted. These 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 respondents proprietary data. RFI responses MUST clearly state whether permission is granted allowing the program office support contractors identified below access to any proprietary information. Boston Consulting Group ZYGOS Consulting Trex Solutions LLC 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, DHMSM 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 partys expense. Participation is not mandatory or required; participation or response to this RFI is not a prerequisite for any future procurement activities.

Full description on SAM.gov

Award Overview

No prior contract identified

No prior award matched this notice's agency, NAICS, place of performance and PSC within 18 months. It may be a new requirement.

Contacts

Documents

No documents available.

Lifecycle

Solicitation:HT003823R0003
  1. Special NoticeCurrentApr 6, 2023

    MHS GENESIS Support

    Notice 4636674ef7914706801b2a4cd8f9c890 on SAM.gov

Similar Opportunities

Title
Match
Phase
Deadline
Amendment 03 10/27/2026: Reposting the attachments due to system issue. Amendment 02 10/26/2026: Revised the AOI, no other changes. Amendment 01 10/22/2026: Revised the AOI, the draft SOO, and posted the questions and answers from 14OCT. Area of Interest (AOI) #02: Data Exchange Services Operations, Modernization, and Development PAE MDS is interested in solutions that satisfy the Government’s need for Data Exchange Services operations, modernization, and development in support of the Enterprise Intelligence and Data Solutions (EIDS) Program Management Office (PMO). This AOI #02 is published under the authority of the Defense Health Agency (DHA) Commercial Solutions Opening (CSO), HT003826SC005, available at: https://sam.gov/workspace/contract/opp/cd16b90540b7407fb4de1e028cea74d4/view Consistent with the maturity and nature of the selected commercial solution and applicable law, the Government may use any applicable award authority identified in the CSO. The DHA Portfolio Acquisition Executive for Medical Defense Solutions (PAE MDS), EIDS PMO, seeks commercial solutions to support Data Exchange Platform (DxP) operations, sustainment, modernization, and development. The DxP supports mission-essential MHS Information Platform (MIP) functions by processing real-time clinical and operational data exchanged with more than 15 external systems and partners. It enables secure, standards-based interoperability among DHA, the Department of Veterans Affairs (VA), and other Federal healthcare partners in support of military health readiness and patient-care delivery. The Government seeks commercial solutions that sustain reliable, secure, and continuously available legacy services while modernizing the platform toward scalable, cloud-native, API-driven, standards-based, and AI/ML-ready capabilities. Solutions may be commercially available or capable of configuration, integration, testing, demonstration, or modification to meet Government objectives. Responses will inform the Government’s assessment of solution maturity, technical feasibility, commercial viability, and potential acquisition pathways. Proprietary Information and Non-Government Advisors Respondents may submit proprietary information. Respondents are responsible for adequately marking all proprietary, restricted, or competition-sensitive information contained in their submissions. Marked information will be protected from disclosure outside Government personnel unless the respondent grants permission for Government support contractors to review the material. The following companies and individual employees are contractually bound by Organizational Conflict of Interest and disclosure clauses regarding proprietary information. They will take all reasonable action necessary to preclude unauthorized use or disclosure of respondent proprietary data: Boston Consulting Group (BCG) Andrew Morgan, LLC Submission under this AOI constitutes the submitting company’s authorization for the Government to use non-Government advisors during all phases of the AOI review. Companies with concerns regarding support-contractor access to proprietary information should contact the points of contact (POCs) before submission. Submission Method and Due Dates Vendors must submit Phase I responses electronically to Lacey Lockard at lacey.n.lockard.civ@health.mil no later than 28 October 2026, 1400 Eastern Time. The Government will not consider late submissions. Vendors must submit technical and administrative questions to Lacey Lockard at lacey.n.lockard.civ@health.mil no later than 14 October 2026, 1400 Eastern Time. As appropriate, the Government may post responses to questions or otherwise provide clarifications to all potential vendors. Per the CSO terms, the Government is not liable for costs associated with preparing materials submitted in response to this AOI. Interested parties are strongly encouraged to review all attached documents in their entirety for complete information regarding this opportunity, including submission requirements and other specific instructions.
-Solicitation10/28/2026
The Defense Counterintelligence and Security Agency (DCSA) Innovation Gateway is a competitive solicitation that will result in the award of prototype projects under Other Transaction Agreements (OTA). It is our commercially-focused front door for innovators. Our goal is simple: to partner with creative companies to solve our most critical mission challenges. Innovation Gateway Process The Innovation Gateway is a general announcement of DCSA’s general areas of interest (Digital Transformation Enablement, Data Integration and Advanced Analytics, Cyber and Industrial Security, Digital Workforce and Governance). The general soliciation includes criteria for selecting Solution Concept Papers and soliciting the participation of all proposers capable of satisfying the Government’s needs. Proposal requests will be issued via ‘Innovation Calls’ that are published separately under the DCSA Innovation Gateway at various times during the open period of this solicitation. Innovation Calls will be published via Sam.gov through separate solicitation postings referencing the DCSA Innovation Gateway. Proposers are required to use the Solution Concept Paper Template (DCSA Innovation Gateway Attachment 1) to submit their solutions. The Government will only accept proposals in response to Innovation Calls. Unsolicited proposals that are not in response to an Innovation Call will not be reviewed by the Government. Additionally, industry representatives wishing to submit general capability statements or schedule capability briefings should direct their inquiries to the DCSA Small Business Office at dcsa.small-business@mail.mil Innovation Call Publications: Innovation Call #01 - Unified Application Access and Integration Prototype Notice ID: DCSAInnovationCall01 Publication Date: 09/10/2026 https://sam.gov/workspace/contract/opp/8edbc404f99d46caa7f41a9bb760f4a9/view
-Solicitation06/23/2031
An Integrated Workforce and Readiness Platform for the Defense Health Agency NAICS Code(s): 541511, 541512, and 541519 1.0 Disclaimer THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is being issued solely for information and planning purposes. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Defense Health Agency (DHA) is not at this time seeking proposals and will not accept unsolicited proposals. Respondents are advised that the U.S. 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 interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. 2.0 Background The Defense Health Agency (DHA) is responsible for managing a complex, global healthcare enterprise. A primary challenge is the fragmentation of critical workforce data across distinct, standalone platforms. Manpower systems track billet assignments, credentialing systems manage clinical privileging, and separate databases monitor medical clearances, operational skillsets (JKSAs), and other position specific training. Because these systems lack native interoperability, leadership must manually reconcile who is assigned with what they are authorized, medically cleared, and operationally ready to perform. This architectural disconnect introduces unacceptable risk, severely restricting our capacity to dynamically assess or model the downstream effects of operational deployments on our garrison healthcare mission. The goal of this initiative is to acquire a comprehensive solution that natively links these critical domains, providing a single, integrated view to meet the dynamic demands of both garrison healthcare and the operational environment. DHA envisions an integrated workforce and readiness platform which will eliminate manual reconciliation and unlock transformative capabilities such as automated clinical scheduling and predictive impact analysis, empowering leaders to dynamically balance all mission requirements. This RFI is intended to gather information on industry best practices and innovative commercial technologies that could enable DHA to achieve this vision. To illustrate our specific needs and desired outcomes, DHA has included high-level use cases that describe how we envision leveraging data across our organization. Please be advised that these use cases are illustrative and subject to further refinement based on the information received from this RFI. 3.0 RFI Responses Submission Deadline: 22 July 2026 5:00 PM EST, submitted electronically via e-mail to Louise Lewis (louise.b.lewis.civ@health.mil) (Contracting Officer) and Rachael Bealer (rachael.n.bealer.civ@health.mil) (Contract Specialist) Interested vendors are invited to submit a capability statement addressing the five high-level use cases outlined in Section 5: Integrated Workforce and Readiness Use Cases. The capability statement should demonstrate your understanding of DHA's challenges and your ability to provide effective solutions to ALL use cases outlined. 3.1 Capability Statement Format: Length: Maximum 10 pages (excluding cover page). No more than the first 10 pages (excluding cover) will be reviewed, if submitted. Format: 8.5x11 inches, single spaced, 12pt font, in MS Word document or PDF format. Focus: Clearly and concisely address how your technical capabilities could address each of the five use cases. Considerations: Responses must address ALL five use cases in order to be considered as complete and be assessed. Late or non-compliant submissions will not be assessed or considered. 3.2.1 Name, mailing address, phone number, and e-mail of designated point of contact. 3.2.2. In order for the Government to assess the market capability of your company or organization as to one or more aspects of the Professional and Administrative Services, please provide the following company information: Company Name; Unique Entity ID; CAGE; Applicable NAICS Codes; Business size status and date of last certification; Applicable GSA SINs [to include description of SIN product/service classification/description]; All Applicable Contract Numbers [i.e. GSA OASIS+, GSA Multiple Award Schedules, DoW CDAO Tradewinds, etc.] (This information is for Market Research only and does not preclude your company from responding to this notice.) 3.3 Vendors will be required to be registered through the System for Award Management (SAM) at https://www.sam.gov/portal/SAM/#1 to be eligible for award of any possible future Government contract opportunities. 3.4 Questions and Answers: There will be no formal question period for this RFI. Please ensure your capability statement is comprehensive and addresses all relevant aspects of each of the use cases. 3.5 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) Andrew Morgan Consulting, LLC Monterey Consultants, INC 4.0 Integrated Workforce and Readiness Use Cases The below proposed use cases are designed to describe the types of capabilities we desire. This is not an exhaustive list but is intended to communicate our core capability objectives to interested industry partners. USE CASE 1: Total Force Visibility: Manpower vs. Personnel Reconciliation Problem: In any large-scale enterprise, tracking authorized positions (the "spaces") versus the actual personnel assigned (the "faces") is a significant challenge. Manpower systems track the authorized billets for an organization but often have a data lag or incomplete fidelity regarding the specific individuals filling those roles, especially when dealing with contractors or personnel on temporary assignment from other departments. This can create "ghost" vacancies or hidden over-manning, preventing leadership from knowing their true assigned strength and skill mix at any given moment. Data Sources: Service MILPER Systems (e.g., IPPS-A, NSIPS), DCPDS (for civilians), and DHMRSi (for manually entered contractor//local national/volunteer data). Desired Capability: The platform must be capable of natively ingesting and reconciling data from disparate HR and manpower systems to create a single, authoritative "Total Force Profile." The system must automatically link the specific individual (the person) to their authorized position (the billet), clearly distinguishing their personnel category (e.g., Military, Civilian, Contractor, Local National, or Volunteer), and instantly alerting leadership to critical mismatches between authorized strength and actual assigned personnel. USE CASE 2: The Joint Staff & Assured Operational Readiness (Clinical) Problem: When sourcing personnel for high-stakes operational assignments (e.g., a forward surgical team, a disaster response unit), a planner may see that a provider is assigned to an operational platform but lack immediate, real-time visibility into whether that provider has the required clinical repetitions ("sets and reps") to perform complex procedures in an austere environment. Relying on manually updated spreadsheets or separate training dashboards to verify this "procedural currency" introduces delays and risk into the operational planning cycle. Data Sources: Service Personnel Systems (for operational assignment), MHS GENESIS (for clinical case logs/CPT codes), and the operational currency hub (JKSA trackers). Desired Capability: The platform must natively link the person, their operational billet, their credentials, and their live clinical currency. The system must be capable of ingesting clinical activity data from the EHR to automatically update a provider’s readiness dashboard without manual entry. This ensures that deployed medical personnel are not just credentialed but are also certified as clinically current and ready for their specific operational mission. USE CASE 3: Enterprise Visibility for Non-Clinical & Support Personnel Problem: While many systems focus on tracking the credentials of privileged medical providers, large healthcare organizations often lack enterprise visibility into the compliance and certification status of the wider workforce. This includes non-privileged clinical staff (e.g., surgical techs, respiratory therapists) and critical non-clinical support staff (e.g., medical logisticians, sterile processing technicians, administrative personnel). If these personnel lack specific, mandatory certifications (e.g., HIPAA, Basic Life Support, Hazmat), the facility cannot operate safely or in compliance with regulatory standards. Tracking these certifications in localized spreadsheets creates risk and administrative overhead. Data Sources: Localized MTF Excel trackers, Service-specific training databases (JKO, Relias), and CCQAS. Desired Capability: The platform must provide a comprehensive competency tracking module that expands beyond privileged providers. The system must allow leadership to define, assign, and track position-specific training requirements and certifications for all personnel categories (clinical, non-clinical, and support staff). The system must proactively alert supervisors of expiring certifications that would render a staff member non-deployable or ineligible to work in a specific garrison role. USE CASE 4: Intelligent, Automated Workforce Scheduling & Compliance Problem: In complex healthcare environments, manually constructing clinical rosters and facility support schedules is highly inefficient and creates risk. Schedulers must often cross-reference a provider’s daily availability against their clinical privileges in separate systems. Simultaneously, they must check disparate local trackers to verify that non-privileged support staff and administrative personnel have completed mandatory compliance training (e.g., ACLS, HIPAA, Sterile Processing). Furthermore, schedulers must verify Occupational Health data to ensure no staff member is placed on a schedule that violates a temporary limiting physical profile. Relying on manual, multi-system reconciliation increases the risk of placing non-compliant or unprivileged staff on the schedule or causing vital facility functions to fail due to lapsed certifications. Data Sources: CCQAS (for privileged provider credentials and risk status), DHMRSI (for daily availability, leave, and assigned positions), Occupational Health Systems of Record (e.g., ASIMS, MEDPROS, MRRS) for physical limiting profiles and deployability flags, and Various Compliance/Training Portals (e.g., Relias, JKO) for non-privileged certifications and administrative compliance. Desired Capability: DHA seeks a scheduling engine that functions as an intelligent rules-based system for the entire MTF workforce. When a manager attempts to schedule a staff member – whether a surgeon, a clinic nurse, or an administrative contractor – the system must automatically verify their baseline identity, current availability, required credentials, and current physical/occupational health profile in real-time. If a staff member’s privileges are suspended, a critical certification has expired, or the assigned shift violates an active Occupational Health limiting profile, the system must enforce a "hard stop," preventing them from being scheduled for that specific duty and immediately notifying the supervisor. USE CASE 5: The MTF Commander & Predictive Capacity Modeling Problem: Healthcare enterprise leadership requires the ability to instantly ascertain the true clinical capacity of a facility at any given moment. Without an integrated system, staff must manually aggregate data across separate HR, clinical, and facility trackers to determine how staffing changes impact bed availability. This lack of integration prevents leadership from maintaining real-time visibility into specialized bed availability (e.g., ICU, Burn, Trauma) and the specific provider coverage required to keep those physical beds operational. It makes it difficult to model how shifting personnel resources will simultaneously degrade home-station care capabilities while reducing the capacity to receive incoming patients during a surge event. Data Sources: MHS GENESIS, Facility Management systems/MEPRS (for baseline physical bed capacity and square footage), DHMRSi, CCQAS, Local hospital surge/expansion plans. Desired Capability: DHA seeks an orchestration layer capable of providing a real-time "Net Assessment" of MTF capacity. The system must ingest facility data (physical beds) and instantly cross-reference it against personnel data (staff available and credentialed to work those beds). When a staffing change is proposed (e.g., a deployment tasking or a surge event), the system must be able to automatically model the downstream impact: e.g., "If 5 ICU nurses are reassigned, Facility 'X' will lose 10 staffed ICU beds for patient care." The solution must automatically alert leadership when staffed bed capacity drops below established readiness thresholds.
-Special Notice07/22/2026
Update 17 April 2026: Amendment 0003 is hereby released. All other terms and conditions remain unchanged. Update 16 April 2026: Attached Q&A (RFP_DeploymentSolutions_Amendments_Q&A_2026.04.16). As of this post, all Q&As regarding Amendments 0001 and 0002 have been answered. On 15 April 2025, the Government removed verbiage from the SAM.Gov Description that was inadvertently included in the combined synopsis/solicitation posted on 06 April 2026, and did not provide a written update in the SAM.Gov Description. All other terms and conditions remain unchanged. Update 13 April 2026: Amendment 0002 is hereby released. Amendment 0001 extended the deadline for proposals to April 21, 2026 at 4:00 PM Eastern Time. The SAM.gov post has been updated to reflect this due date and time. Attached Q&A (RFP_DeploymentSolutions_Q&A_2026.04.13). As of this post, all Q&As have been answered. All other terms and conditions remain unchanged. Update 10 April 2026: Attached Q&A 1-52 (RFP_DeploymentSolutions_Q&A_2026.04.10). Q&A's will continue to be posted in phases based on the number of questions submitted. Update 08 April 2026: Amendment 0001 is hereby issued. This amendment clarifies provision 52.212-1 as detailed in the SF 30, Box 14; provides Attachment 19: PEO DHMS Deployment Ordering Guide; and extends the closing date and time to April 21, 2026 at 4:00 PM Eastern Time. All other terms and conditions remain unchanged. This update also provides Q&A (RFP_DeploymentSolutions_Q&A_2026.04.08). Q&A's, will be posted in phases based on the number of questions submitted. The deadline to submit questions, remains unchanged. Update 06 April 2026 : Attached Q&A (RFP_DeploymentSolutions_QA_2026.04.06). Q&A's, will be posted in phases based on the number of questions submitted. The deadline to submit questions, remains unchanged. The Defense Health Agency Contracting Activity (DHACA), on behalf of the Program Executive Office (PEO) Defense Healthcare Management Systems (DHMS), intends to issue a multiple award, Indefinite Delivery Indefinite Quantity (IDIQ) contract for Deployment Solutions. Deployment Solutions is a non-personal services requirement to provide all services and materials necessary to support and execute the on-demand deployment of DHMS products, and related or supporting components, including site preparation, deployment, training, user adoption, change management, and post-installation support to ensure seamless integration and minimal disruption to existing healthcare systems. This is a combined synopsis/solicitation for commercial products or commercial services prepared in accordance with part 12. This announcement constitutes the only solicitation. Offers are being requested and a separate written solicitation will not be issued. Solicitation number HT003826RE001 is issued as a request for proposal (RFP) for Deployment Solutions. This acquisition is not set-aside for small business concerns. This solicitation incorporates provisions and clauses by reference. The full text of provisions and clauses may be accessed electronically at www.acquisition.gov. See the solicitation for a description of Contract Line Item Numbers (CLINs), option periods in support of the Performance Work Statement (PWS), and a list of provisions and contract clauses that apply to the acquisition. Instructions for Responding Solicitation questions must be submitted no later than April 9, 2026 at 12:00 PM Eastern Time to the Contract Specialist listed below. Include in the Subject Line the following: Company name and Deployment Solutions. Proposals must be submitted electronically via a secure online submission portal by April 15, 2026 at 12:00 PM Eastern Time. See 52.212-1 Instructions to Offerors – Commercial Items for specific instructions. Proprietary information may be submitted; however, 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. Points of Contact: Contracting Officer: Joyce Elaine Pace-Reed, joyce.e.pace-reed.civ@health.mil Contract Specialist: Samantha DeLuca, dha.ncr.co.mbx.cd-dhms-contracting@health.mil
-Combined Synopsis04/21/2026
24 March 2026 All questions have been answered and the updated Q&A is attached (DraftRFP_Q&A_DeploymentSolutions_2026.03.24). 19 March 2026 The Government received several hundred questions in response to the draft solicitation. Provided are the first 100 questions and responses. The remaining will be provided at a future date. 04 March 2026 1) Posting was updated to replace Attachment "DRAFT_52.212-1&2_DeploymentSolutions_2026.03.03.pdf" with Attachment "DRAFT_52.212-1&2_DeploymentSolutions_2026.03.04.pdf" 2) Added link to Related Notice 03 March 2026 Related Notice ID: HT003826RFIE001 The Defense Health Agency Contracting Activity (DHACA), on behalf of the Program Executive Office, Defense Healthcare Management Systems (PEO DHMS), intends to issue a solicitation for Deployment Solutions. Deployment Solutions is a non-personal services requirement to provide all services and materials necessary to support and execute the on-demand deployment of DHMS products, and related or supporting components, including site preparation, deployment, training, user adoption, change management, and post-installation support to ensure seamless integration and minimal disruption to existing healthcare systems. This announcement constitutes a draft Request for Proposal (RFP) for industry review and comment and includes the below artifacts. Draft Performance Work Statement (PWS) Draft 52.212-1 and 52.212-2 Draft Exhibit A003 Deployment Approach CDRL Draft Attachment 16, OCI Declaration and Disclosure, Notice of Organizational Conflict of Interest Draft RFP Deployment Solutions Feedback We are not soliciting proposals at this time, and none will be accepted. A separate formal solicitation is expected to be issued at a later date. Instructions for Responding Submit feedback no later than March 11, 2026 at 12:00 PM Eastern Time to the Contract Specialist listed below. Include in the Subject Line the following: Company name and Deployment Solutions. Use the attached workbook “Draft RFP Deployment Solutions Feedback to provide your feedback. Name the workbook as follows “Company name_Deployment Solutions”. For each comment, select the name of the document, provide the page number, relevant section, and paragraph or line number so it is clear what your feedback is referring to. Proprietary information may be submitted; however, 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 a respondent’s proprietary data. 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 notice is for informational and market research purposes only. It does not constitute a formal Request for Proposal (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or award a contract. The Government will not pay for any information or administrative costs incurred in response to this notice. All information submitted in response to this notice is voluntary, and the Government may or may not use the information to develop its acquisition strategy and final solicitation. Points of Contact: Contracting Officer: Joyce Elaine Pace-Reed, joyce.e.pace-reed.civ@health.mil Contract Specialist: Samantha DeLuca, dha.ncr.co.mbx.cd-dhms-contracting@health.mil
-Pre-Solicitation03/11/2026

Additional Details

Solicitation Number

HT003823R0003

Archive Date

Not specified

Office Address

FALLS CHURCH, VA, 22042