Notice of Intent - Sole Source to MHS GENESIS Solution providers
Archived on July 2, 2026. Original response deadline: . Full description on SAM.gov.
Overview
- Response deadline
- 11:59 PM EDT
- Posted
- June 15, 2026
- Notice type
- Sources Sought
- NAICS
- 541512: Computer Systems Design Services
- Agency
- Department of WarDEFENSE HEALTH AGENCY (DHA)
Notice details
- Office
- DEFENSE HEALTH AGENCY
- Place of performance
- Virginia, 22209
- Last updated
- Oct 28, 2026
- First published
- Last updated on SAM.gov
Identifiers
- Solicitation number
- HT003826CEXXX1
- Notice ID
- 8eab9996b3eb4632ace81014f963c351
Description
This is a notice of intent to award five sole source contracts and is not a request for competitive quotes. A sole source justification in accordance with FAR Part 6 is being processed for this requirement and will be posted when the approval process is accomplished.
The forthcoming Class Justification and Approval (J&A) authorizes the Defense Health Agency (DHA) to award multiple sole-source contracts, on an other than full and open competition basis, to the following proprietary platform vendors:
Cerner Corporation (Oracle Health)
8779 Hillcrest RD Kansas City, Missouri, 64138-2700
Cage: 1JCJ0
UEID: DMHXTXRARC74
Philips North America LLC (Philips Healthcare)
222 Jacobs ST, East Cambridge, Massachusetts, 02141-2296
Cage: 0ZBJ4
UEID: PWFVQLA9SX78
American Well Corporation (Amwell)
75 State ST FL 26, Boston, Massachusetts, 02109-1827
Cage: 64FM6
UEID: DJC6XVXQMV15
Henry Schein, Inc.
135 Duryea RD, Melville, New York, 11747-3834
Cage: 0NUS8
UEID: D6MTSKS115L9
Solventum Health Information Systems, Inc. (Solventum)
575 W Murray BLVD, Murray, Utah, 84123-4611
Cage: 3L5X5
UEID: LUYEUMH42L88
These contracts will provide critical system components, software licensing, and specialized services that form the foundational architecture of the Military Health System (MHS) GENESIS environment, which are currently being delivered through a legacy solution provider integrator. The Government's target timing is to transition the Philips and Amwell relationships to direct contracts prior to the end of July 2026, Oracle Health by November 2026, and Henry Schein and Solventum by July 2027. Note: Additional direct relationships may be established over time based on the operational and financial benefit to the Government. If additional proprietary solutions can be broken out are identified, the J&A will be updated to support the direct procurement of those systems.
This action represents a deliberate and strategic shift in the Government's acquisition approach, moving away from a monolithic solution provider integrator model toward a competitive, modular, direct-vendor contracting strategy. Under the new model, DHA will contract directly with the proprietary solution providers for core system capabilities, rather than procuring these services and paying pass-through overhead through an intermediary.
This shift is driven by both operational experience and Department-level policy direction. Historically, the use of a single solution provider integrator—tasked with integrating the efforts of multiple vendors—enabled the rapid deployment and initial stabilization of the MHS GENESIS system-of-systems. However, as the system has reached full deployment and transitioned into the sustainment and optimization phase, this intermediary model has introduced:
- Reduced cost transparency
- Duplicative layers of vendor management and administration
- Limited Government visibility into underlying pricing structures
- Constraints on the Government’s ability to directly manage vendor performance and enforce Service Level Agreements (SLAs)
Consistent with Department of Defense policy, DHA is now transitioning to a model that emphasizes direct acquisition from core solution providers, systematically reducing reliance on integrators and improving overall acquisition efficiency.
This sole-source action directly supports those Federal mandates by:
- Eliminating integrator pass-through costs and duplicative overhead
- Establishing direct contractual relationships with foundational solution providers
- Improving pricing transparency and Government cost control
- Stabilizing the core architecture to enable future competition at the modular component level (e.g., integration of efforts, ancillary services)
While this transition introduces near-term integration and execution complexities, DHA has determined that such risks are manageable and entirely warranted to align with Department policy direction and achieve long-term improvements in cost efficiency. This phased transition ensures uninterrupted continuity of operations and a controlled assumption of integration responsibilities by the Government.
Because the required capabilities are proprietary, deeply embedded, and available only from the original vendors currently providing them, DHA has determined that award on an other than full and open competition basis is required. Securing these direct vendor relationships is absolutely critical because the MHS GENESIS platform operates as the anchor of a unified Federal health IT ecosystem. In 2018, the Department of Veterans Affairs (VA) and the United States Coast Guard (USCG) determined that alignment with the DoD’s Electronic Health Record (EHR) system was in the Government's best interest to enable total interoperability. Today, this shared baseline supports not only DoD operations, but also the United States Coast Guard (USCG), National Oceanic and Atmospheric Administration (NOAA), and other organizations using MHS GENESIS to document the delivery of healthcare. It is also a shared baseline with the VA who is actively deploying its solutions, slated for completion in 2031. Transitioning to direct vendor contracts ensures interagency continuum of care remains stable and undisrupted.
In preparation for conducting a fair and open competition at the completion of the incumbent current contract (N003915D0044), the Defense Healthcare Management System Modernization (DHMSM) Program Management Office (PMO) engaged industry and conducted extensive market research looking to inform its acquisition strategy starting in early 2023 through early 2026. The Government determined that the most responsible and effective path to expanding competition is a phased, deliberate approach. By establishing direct, sole-source contractual relationships with the current proprietary solution providers now, the Government stabilizes the core platform, preserves the unified Federal baseline, and eliminates the legacy solution provider integrator's pass-through costs. This critical stabilization serves as the prerequisite foundation that will enable the Government to progressively introduce full and open competition for discrete capability areas such as the integration of efforts, product management, and ancillary support services once delivery dependencies are mitigated and modularization objectives are fully realized.
Even though alternative commercial systems possess similar functional capabilities, no alternative sources were identified that could replace the currently selected and deployed proprietary platforms without substantial disruption to interagency operations. Crucially, during the market research process, no industry respondents or participating vendors recommended changing out or replacing any of these core solution components. Industry consensus acknowledged that attempting to swap the selected foundational platforms at this stage would trigger immense interagency operational risk, severe schedule delays, and duplication of cost.
Based on the above, the DHMSM PMO decided that the above proprietary platform vendors are the only sources available to meet these agencies’ needs to sustain the unified Federal EHR baseline within the required timeframe and without introducing unacceptable risk.
Services:
The Government will establish direct contractual relationships with select Best of Suite (BoS) and Best of Breed (BoB) proprietary solution providers supporting the MHS GENESIS ecosystem. These direct contracts will transition essential capabilities, services, licensing, and support functions—previously obtained through the incumbent solution provider integrator under a bundled delivery model—into a modular, transparent acquisition structure.
Not all contractors identified in this J&A will perform all categories of work listed below. The specific scope will vary based on the solution, capability area, and operational requirements associated with each respective vendor’s proprietary products. Broadly, the services authorized under this J&A include:
Software Licensing, Maintenance, and Subscription Services
Provision of commercial software licenses, software maintenance, subscription services, updates, patches, fixes, upgrades, enhancements, and associated vendor technical support necessary to sustain and operate the contractor’s proprietary solutions within the MHS GENESIS environment.
Hosting and Infrastructure Support
Provision of hosting services and associated infrastructure necessary to ensure the continuous operation, availability, interoperability, security, and performance of the contractor’s solution within the MHS GENESIS ecosystem. This includes cloud-based hosting, on-premises hosting, hybrid hosting models, storage, networking, compute resources, hardware, backup and recovery capabilities, disaster recovery support, cybersecurity compliance, and environment management.
- Interagency Coordination: Hosting services will require deep coordination with other DoD contractors, commercial cloud providers, Government-furnished infrastructure, and third-party technology providers to support interoperability across the MHS GENESIS ecosystem, DHA infrastructure, DoD Information Technology (IT) networks, and Military Medical Treatment Facilities (MTFs) worldwide.
- Cloud Transition: The contractor is responsible for providing all hosting services unless specifically agreed to be provided by the Government. As the program continues its strategic transition to a cloud-based architecture, hosting responsibilities will increasingly shift toward commercial cloud infrastructure in strict accordance with DoD cloud policies and vendor-supported deployment models.
Sustainment and Operational Support
Provision of sustainment, continuous operational support, advanced troubleshooting, technical assistance, enable efficient resolution of Tier 1 and Tier 2 incidents, Tier 3 vendor help desk support, and lifecycle management services necessary to maintain uninterrupted continuity of interagency healthcare operations.
Enabling New Capabilities
The contractor shall be responsible for activating and enabling new capabilities that align with functional requirements approved by the Configuration Steering Board (CSB) and the Milestone Decision Authority (MDA). These new capabilities must be native to the vendor's existing Commercial Off-The-Shelf (COTS) solution and must provide functionality that is not otherwise available via another product within the MHS GENESIS ecosystem or available via a standalone BoB product.
Optimization
Provision of optimization, configuration, workflow enhancement, and performance improvement services explicitly intended to improve functionality, usability, interoperability, operational efficiency, and clinical user experience within the existing MHS GENESIS environment.
Coordination with Program Office Support Contractors
Active interfacing with the Program Management Office (PMO) and supporting functions to coordinate activities, API enablement, interface management, ensure clinical requirements are met, product roadmaps are clearly understood, and capability enhancements are prioritized based on mission value and interagency needs.
Specific Solution Provider Capabilities
Each of the solutions detailed below shares common foundational requirements: they all provide the essential software licensing, maintenance, subscription services, hosting, and sustainment support necessary to operate MHS GENESIS ecosystem, working in concert to ensure seamless interoperability, support complex clinical and operational workflows, and maintain the continuity of care across the unified Federal EHR baseline.
Oracle Health (Best of Suite)
Oracle Health will be engaged as the Best of Suite provider supporting the core MHS GENESIS EHR platform. Oracle Health (formerly Cerner Corporation) provides the foundational enterprise EHR architecture, including the Millennium platform and associated hardware and infrastructure components. Additionally, Oracle Health may provide access to certain third-party capabilities that are pre-integrated, certified, or optimized within the Oracle Health ecosystem. Utilizing these pre-integrated capabilities enables the Government to significantly reduce integration complexity, implementation timelines, operational risk, and duplicative integration costs.
Philips (Best of Breed)
Philips Healthcare will be engaged as a Best of Breed provider supporting tele-critical care capabilities. Philips provides specialized tele-critical care software, remote patient monitoring infrastructure, and associated proprietary hardware components (including cameras and related specialized equipment) required to sustain high-acuity remote clinical observation and intervention workflows that are not natively delivered within the core enterprise EHR platform.
Amwell (Best of Breed)
Amwell will be engaged as a Best of Breed provider supporting virtual care and telehealth capabilities. Amwell provides telehealth platform access enabling secure, remote patient-provider interactions and virtual care delivery. This specialized solution complements the core MHS GENESIS environment by supporting expanded patient access and digital health modernization initiatives across the interagency footprint.
Solventum (Best of Breed)
Solventum (formerly 3M Health Information Systems) will be engaged as a Best of Breed provider supporting clinical documentation, coding, workflow optimization, and related healthcare administration capabilities. Solventum provides proprietary software intended to improve clinical documentation workflows, coding efficiency, and operational performance, directly supporting complex revenue cycle functions and evolving federal healthcare administration compliance requirements.
Henry Schein / Dentrix (Best of Breed)
Henry Schein will be engaged as a Best of Breed provider supporting dental EHR capabilities through its proprietary Dentrix platform. The Dentrix platform provides dedicated, highly specialized dental care delivery functionality and workflows that are not natively provided within the core enterprise EHR platform.
The Government anticipates awarding firm-fixed-price, outcome-based contracts for these requirements. The period of performance across all solutions is anticipated to begin no later than July 2027, with a maximum duration of five (5) years per contract.
Be advised that the aforementioned information is anticipatory in nature and is not binding. This notice is not a request for competitive proposals; however, any firm believing it can fulfill the requirement of providing these services may be considered by the Agency. Interested parties shall identify their interest and capabilities in response to this synopsis within 8 calendar days of publication.
The response must clearly demonstrate an ability to successfully fulfill the above requirements without duplicating the investment already made. Specifically address as part of the response the following:
- System Replacement & Interoperability: The Government has determined that replacing the incumbent proprietary platforms (Oracle Health, Philips, Amwell, Solventum, Henry Schein) would cause immense interagency operational risk, severe schedule delays, and duplication of cost. If your company believes it can provide an alternative solution, please detail how your approach would replace any of these core components without disrupting the unified DoD, VA, and USCG Electronic Health Record (EHR) baseline.
- Scale and Capacity: MHS GENESIS processes at least 20 million messages daily, encompasses 12 major subsystems, and supports 191,000 users globally. If proposing an alternative to the proprietary solutions, detail your firm’s experience successfully deploying and hosting a clinical solution of this scale/ complexity within an Impact Level 4/5 (IL4/IL5) or equivalent secure environment.
- Data Migration Risk: MHS GENESIS currently holds 255 TB of Millennium data, growing at 100 TB annually. If proposing an alternative system, how would your firm execute the necessary data migration without degrading clinical performance or extending the July 2026/2027 transition timelines?
- This contracting approach relies on direct-vendor contracts to eliminate overhead, maximize transparency, and stabilize architecture. If you are recommending an indirect or intermediary approach, how will your company replicate these specific advantages and prove the Government will not incur duplicative costs or lose direct visibility into the foundational solution?
The Government’s assessment is that responses must elaborate on all four enumerated paragraphs above. If a company disagrees with that assessment, please respond by explaining how the Government may otherwise meet the requirements listed in this notice. While there is no maximum page limit, the Government is only interested in responses relevant to this notice. The Government will not review individual resumes or general marketing materials. While there is no mandatory format for responses, the Government requests that responses in excess of four pages include a table of contents, page numbers and corresponding headers.
The Government reserves the right not to respond to any expression of interest received. Any comments, questions, or concerns regarding this notice may be submitted IN WRITING via email to Sonya Edom (sonya.m.edom.civ@health.mil) and Gabriela Hurte (gabriela.y.hurte.civ@health.mil). No telephone responses will be accepted.
Submissions will NOT be reimbursed by the Government and the entire cost of any submission will be at the sole expense of the source submitting the information. A determination by the Government not to compete this proposed contract action based upon responses to this notice is solely within the discretion of the Government.
Information received will be considered solely for the purpose to determining whether to conduct a competitive procurement. This synopsis is for informational purposes only. Any Justification and Approval resulting from a decision to award the proposed sole source action will be posted on this website.
All information received in response to this notice that is marked Proprietary will be handled accordingly. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Submissions will not be returned, nor will the Government confirm receipt of submissions.
Award Overview
Mentioned in the description
From description, unverifiednd open competition at the completion of the incumbent current contract (N003915D0044), the Defense
We searched the solicitation description for the word “incumbent” and surfaced the surrounding text. This is not a confirmed match.
Contacts
Contracting Officer
Primary Contact
Secondary Contact
Documents
No documents available.
Lifecycle
- 1Version 1Sources SoughtArchived
Notice of Intent - Sole Source to MHS GENESIS Solution providers
- 3Version 3Sources SoughtArchivedCurrent
Notice of Intent - Sole Source to MHS GENESIS Solution providers
Similar Opportunities
Title | Match | Phase | Deadline |
|---|---|---|---|
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. | 74% | Special Notice | 07/22/2026 |
Updated as of 24 June 2026 – Amendment 02: This amendment posts additional Industry Event materials and Question/Answers associated with LOGFIN26‑CFS‑001. The following documents have been added: • Industry Day Registered Companies List (DISTRIBUTION A) • Industry Day Questions & Answers (DISTRIBUTION A) The Submission deadline remains 30 June 2026 at 12:00 PM Central Standard Time. ___________________________________________________________________________ Updated as of 6/18/26 Amendment 01: The U.S. Army is issuing this Call for Solutions (CFS) under CSO procedures to solicit innovative Low‑Code/No‑Code (LCNC) and software modernization technologies supporting modernization of the Army’s five SAP‑based Defense Business Systems. Proposed solutions must include both non‑transactional and transactional capabilities that integrate with existing ERP systems. The Army accepts solutions built on platforms listed in Appendix C and may also consider alternative platforms that provide a truly transformative capability with a compelling business case and a realistic plan for approval. Solutions must securely operate at IL4/IL5/IL6 and support degraded or disconnected operations for forward‑deployed units. Questions & Answers will be posted at the beginning of next week. NOTE: To ensure you receive timely notifications of all amendments and updates to this posting, we strongly encourage all interested parties to use the "Follow" feature within SAM.gov. To do so: Log in to your SAM.gov account. Navigate to this notice page. In the upper-right corner of the page, click the "..." (three dots) button. From the dropdown menu, select "Follow". Why this is important: Notification: Once you follow this notice, SAM.gov will automatically send an email to your account whenever it is amended or updated. Correct Links: Each update to a SAM.gov posting generates a new, unique web link. Bookmarking a page or using an old link will take you to an outdated version. The email notification you receive from following the notice will always contain a direct link to the latest version. Verification: The upper right corner of a posting shows a "Version" box, however it always displays "Current Record" regardless of what version you are viewing. You must manually check the version dates using the dropdown. Following a posting and using the emailed link ensures you are viewing the latest version, and avoids having to manually verify. | 69% | Combined Synopsis | 06/30/2026 |
This Open and Continuous Call for Solutions (CFS), Notice ID LOGFIN26, is issued under the Army Open Solicitation (AOS) W9128Z‑25‑S‑A002 for the U.S. Army Contracting Command – Rock Island (ACC‑RI). The CFS seeks innovative commercial Low‑Code/No‑Code (LCNC) and modernization solutions to support the Army Logistics and Finance communities through rapid, iterative prototyping aligned to nine Areas of Interest (AOI) representing PM LOG‑FIN Value Chains. This CFS remains open in perpetuity until canceled. The Government will publish separate Targeted Calls for Solutions (TCFS) under this CFS, each with specific requirements and deadlines. Industry may also submit AOI White Papers at any time identifying capability gaps within the AOIs. Submissions must address LCNC and modernization capabilities supporting non‑transactional and transactional functions integrating with five current Army ERP systems. Solutions affecting financial transactions must meet DoD auditability, internal controls (ICOFR/ITGC), traceability, and segregation of duties requirements. All solutions must comply with Army cybersecurity, governance, and interoperability standards and be deployable in cArmy 2.0. The nine Areas of Interest (AOIs) include: • AOI 01: Mission Operations Support • AOI 02: Asset Acquisition • AOI 03: Real Estate • AOI 04: Supply • AOI 05: Fulfillment • AOI 06: Transportation • AOI 07: Maintenance • AOI 08: Manufacturing / Remanufacturing • AOI 09: Resource Allocation Approved LCNC platforms include Appian, Army Vantage, Palantir, PowerApps, Salesforce, SAP, and ServiceNow. Submissions must follow all instructions in this announcement. Questions and submissions must be sent to usarmy.ria.acc.mbx.pmlogfin-cso@army.mil. The Army Open Solicitation (AOS) that this Call for Solution is associated with can be found at: https://sam.gov/workspace/contract/opp/09ab570a35484c6cb5c6eba05cad19b3/view Please review the AOS posting and associated attachments, in addition to the attachment to this call, for further information on how the AOS is structured. To ensure you receive timely notifications of all amendments and updates to this posting, we strongly encourage all interested parties to use the "Follow" feature within SAM.gov. To do so: Log in to your SAM.gov account. Navigate to this notice page. In the upper-right corner of the page, click the "..." (three dots) button. From the dropdown menu, select "Follow". Why this is important: Notification: Once you follow this notice, SAM.gov will automatically send an email to your account whenever it is amended or updated. Correct Links: Each update to a SAM.gov posting generates a new, unique web link. Bookmarking a page or using an old link will take you to an outdated version. The email notification you receive from following the notice will always contain a direct link to the latest version. Verification: The upper right corner of a posting shows a "Version" box, however it always displays "Current Record" regardless of what version you are viewing. You must manually check the version dates using the dropdown. Following a posting and using the emailed link ensures you are viewing the latest version, and avoids having to manually verify. | 68% | Solicitation | 06/02/2031 |
Please see attached RFI titled, RFI_36C10B27Q0109 . | 67% | Market Research | 11/20/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 | 67% | Combined Synopsis | 04/21/2026 |
Additional Details
Solicitation Number
HT003826CEXXX1
Archive Date
Jul 2, 2026
Office Address
ROSSLYN, VA, 22209