Program Executive Office (PEO) Defense Healthcare Management Systems (DHMS) Deployment Solutions

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the viewer. It suggests upgrading to the latest version of Adobe Reader and provides links for download and assistance.

This document is not relevant to bidders as it does not contain any information about the opportunity, requirements, or submission details. It is a technical display issue.

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the viewer. It suggests upgrading to the latest version of Adobe Reader and provides links for download and assistance.

This document is not relevant to bidders as it does not contain any information about the opportunity, requirements, or submission details. It appears to be a technical issue with the document display rather than substantive content.

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the viewer. It suggests upgrading to the latest version of Adobe Reader and provides links for download and assistance.

This document is not relevant to bidders as it does not contain any information about the opportunity, requirements, or submission details. It appears to be a technical issue with the document display.

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the viewer. It suggests upgrading to the latest version of Adobe Reader or visiting a provided link for assistance.

This document does not contain substantive information related to the opportunity. It is an administrative message related to PDF viewing capabilities and does not provide details on requirements, deliverables, or submission instructions.

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the viewer. It suggests upgrading to the latest version of Adobe Reader and provides links for download and assistance.

This document does not contain substantive information related to the SAM.gov opportunity. It is an administrative message related to PDF rendering and does not provide details on requirements, deliverables, or submission instructions for potential bidders.

Form / Attachment / Pricing Sheet

This document is a Contract Data Requirements List (CDRL) that specifies the "Cost and Hour Report (FlexFile)" (Data Item No. CDRL A008) as a required deliverable. It outlines the requirements for preparing and submitting this report.

• Data Item: CDRL A008, Cost and Hour Report (FlexFile)
• Authority: DI-FNCL-82162
• Subtitle: Contractor Cost Data Reporting (CCDR)
• Preparation: Reports are to be prepared in accordance with DI-FNCL-82162 and the OSD CAPE Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan. The DID is available at https://cade.osd.mil/csdrreportingguidance/dids.html.
• Tailoring: Data Group B - Item 4 - Additional Data Fields #1-#12 are not required.
• Submission Frequency: Based on "event fields" in the CAPE-approved CSDR plan, not "as of date." Government Program Office must be notified of event slips.
• Format: MS Excel (.xlsx), comma-separated values (.csv), or JavaScript Object Notation (JSON) as per FlexFile File Format Specification (FFS) and Data Exchange Instructions (DEI).
• Submission Method: Electronically via the CADE website. Requires registration, a DoD-approved ECA digital certificate or DoD-issued CAC, and a CSDR submitter user role.
• Distribution: In addition to CADE, the PEO DHMS Cost, Schedule, Performance Report shall be submitted electronically to the COR and dha.ncr.PEO-DHMS.list.csp-data-reporting-owners@health.mil.
• Subcontractor Reporting: Prime contractors must flow down CSDR requirements to subcontractors with anticipated eventual contract value greater than $20M, requiring electronic reporting to CAPE via the CSDR Submit-Review System.

This CDRL details a mandatory reporting requirement for contractors. Bidders must understand the specific format, submission process, frequency, and distribution requirements for the Cost and Hour Report (FlexFile) to ensure compliance if awarded the contract. It also highlights the need to manage subcontractor reporting requirements.

Other / Unclassified

This document is a placeholder page indicating that the PDF viewer may not be able to display the document's content. It suggests upgrading to the latest version of Adobe Reader or visiting a provided link for assistance.

This document does not contain substantive information related to the SAM.gov opportunity. It is a technical message related to PDF rendering and does not provide details on requirements, scope, or submission instructions for bidders.

Form / Attachment / Pricing Sheet

This document is a Cost and Software Data Reporting Plan (CSDR Plan) using DD Form 2794. It outlines the requirements for reporting cost and software data for the PEO DHMS - Defense Health Management System (DHMS) program. This plan is intended for the prime contractor to detail how costs will be tracked and reported throughout the contract lifecycle.

• Program Name: PEO DHMS - Defense Health Management System (DHMS)
• Prime Mission Products: MHS GENESIS, MHS GENESIS Theater, Operational Medicine (OpMed) Care Delivery Platform (CDP)
• Acquisition Category: Other
• Commodity Type: Information System/Defense Business System
• Plan Type: Initial Contract (Prime)
• Reporting Requirements: Includes Cost and Hour Reports (FlexFile) and Technical Data Reports (TDR).
• Work Breakdown Structure (WBS): Details specific WBS elements for both IS/Defense Business Systems (Investment) and Sustainment phases.
• Submission Events: Outlines initial, interim, and final reporting events with associated due dates relative to contract award.
• Remarks: Provides specific instructions for cost reporting, WBS element specification, submission event timing, and handling of specific contract types (e.g., FFP, cost-plus).
• Technical Parameter Requirements: Lists specific metrics and parameters to be tracked, including IT infrastructure maintenance, software release frequency, development methodology, and cybersecurity metrics.

This document is crucial for understanding the extensive cost and software data reporting obligations associated with the contract. Bidders must review the detailed WBS, reporting requirements, submission schedules, and technical parameters to accurately estimate the resources and processes needed for compliance. The plan specifies the use of FlexFile for cost reporting and outlines specific technical data requirements, which will impact project management and execution planning.

Other / Unclassified

This document is a visual infographic titled "How PEO DHMS Integrates Across the Federal Space." It illustrates the integration of the Program Executive Office for Defense Healthcare Management Systems (PEO DHMS) within the federal healthcare landscape.

This document provides a high-level overview of the PEO DHMS's role in managing state-of-the-market electronic health records (EHRs) and delivering information systems for operational medicine. It shows how data is enriched, moved, and analyzed across various entities, including external hospital systems, the Department of Defense Military Treatment Facilities (DOD MTF), Veterans Affairs (VA), and theater hospitals. It also highlights key stakeholders such as MHS staff, providers, and potential DOD beneficiaries. This visual may help potential bidders understand the ecosystem in which PEO DHMS operates and the scope of its integration efforts.

Form / Attachment / Pricing Sheet

This document is the Organizational Conflict of Interest (OCI) Declaration and Disclosure Statement required for solicitation HT003826RE001. Its purpose is to ensure that offerors do not have an OCI that would disqualify them from competing for this procurement, as per Revolutionary Federal Acquisition Regulation (FAR) Overhaul (RFO) 9.5.

• Offeror Declaration: Bidders must declare whether they have an OCI.
• No OCI: If no OCI exists, the offeror must confirm they have not had access to non-public information for this solicitation and have not provided services that could influence the competition.
• Potential OCI: If a potential OCI exists, the offeror must provide a separate disclosure statement detailing all relevant information for the government's assessment.
• Required Information: The form requires the name of the authorized representative, company name, and signature.

Completion of this form is mandatory. Failure to provide the statement, or omitting or misrepresenting information, may result in the offeror being deemed ineligible for award. Bidders must carefully review their company's activities and access to information related to solicitation HT003826RE001 to accurately complete this declaration.

Forms / Attachments / Pricing Sheets

This document, "DHA Common Federal Training List (CFT) Fiscal Year 2025," outlines the mandatory training requirements for personnel working within the Defense Health Agency (DHA) and its facilities. It serves as a comprehensive guide for identifying required courses, their frequency, delivery methods, and applicable audiences.

• Training Topics: Lists various mandatory training courses, including but not limited to Cyber Awareness, HIPAA, Security Awareness, Combating Trafficking in Persons, and specific healthcare-related training.
• Frequency and Time Requirements: Specifies how often each training must be completed (e.g., annually, one-time, every 3 years) and the estimated time commitment.
• Regulatory Guidance: Cites the specific DoD Instructions (DoDI), DHA Administrative Instructions (DHA-AI), and Public Laws that mandate each training.
• Applicable Audiences: Delineates which personnel groups are required to complete each training, categorized by DHA Civilian, DHA Contract Support, Service Members (Air Force, Army, Navy), Supervisors, Managers, Healthcare Providers, Senior Leaders, and others.
• Delivery Methods: Indicates how the training is delivered, primarily through Joint Knowledge Online (JKO) or other designated learning management systems.
• Alternative Training: Provides information on whether alternative or Service-required training can be substituted for DHA-specific courses.
• Frequently Asked Questions (FAQs): Addresses common queries regarding enrollment, audience definitions, healthcare provider definitions, tracking completion, and contact information for assistance.

This document is crucial for contractors supporting the DHA. It clearly defines the training obligations for personnel, including contractor support. Bidders must understand these requirements to accurately estimate labor costs, ensure compliance for their proposed staff, and demonstrate their understanding of DHA's operational and regulatory environment. It helps in assessing the full scope of personnel requirements for any contract involving DHA personnel.

Solicitation / RFP / RFQ

This solicitation (HT003826RE001) is for "Deployment Solutions" with a total contract ceiling of $300,000,000.00, inclusive of base and option years. The solicitation is released following a Revolutionary Federal Acquisition Regulation (FAR) Overhaul. The government is procuring services and materials necessary to execute deployment services, including site preparation, deployment, training, change management, and post-installation support.

This contract covers deployment services and materials for the Program Executive Office Defense Healthcare Management Systems (PEO DHMS) modernization of global healthcare capabilities. This includes:

• Federal EHR product modernization and deployment: Full implementation at established, high-capacity treatment facilities (e.g., OCONUS medical center, community hospitals, out-patient clinics) serving approximately 50,000 beneficiaries and 5,000 users. Services include inpatient, outpatient, acute, ambulatory, specialty, and dental care, as well as revenue cycle services. The technical environment requires integration with medical devices and IT systems.

• OpMed products modernization and deployment: Mobile and interoperable solutions for medical forces in deployed and tactical environments (CONUS and OCONUS). This includes theater hospitals, hospital ships, forward resuscitative sites, and submarines. The scope involves rapid global deployment to at least five sites/units simultaneously, with uncertain schedules and complex infrastructure. Services include ambulatory care, emergency trauma, surgical stabilization, enroute care, behavioral health, and blood inventory management. A critical requirement is seamless data transmission and Command and Control Situational Awareness (C2SA) reporting. The technical environment requires integration with Service-specific hardware and diverse Service networks for low-to-no-touch deployments in disconnected, intermittent, and low-bandwidth (DIL) environments.

• Contract Type: Firm Fixed Price (FFP), Multiple Award Contract (MAC).

• Period of Performance: Base and option years, with a total contract ceiling of $300,000,000.00.

• Estimated Value: Not explicitly stated, but the total contract ceiling is $300,000,000.00.

• Proposal Submission Deadline: April 15, 2026, at 12:00 PM Eastern Time, via the Bidscale portal.

• Evaluation: Proposals will be evaluated based on Factor 1: Challenge Scenario and Factor 2: Supply Chain Risk Management Plan. Price is not an evaluation factor. Award will be made to technically acceptable and responsible offerors.

• Challenge Scenario Evaluation: Offerors must receive an "Acceptable" rating in at least one of the two scenarios (1a or 1b) to be considered Acceptable for Factor 1. An "Unacceptable" rating in both scenarios results in ineligibility for award.

• Supply Chain Risk Management Plan: Proposals must meet minimum requirements for identifying, assessing, and mitigating supply chain risks.

• This solicitation seeks full and open competitive offers.

• The North American Industry Classification System (NAICS) code is 541512.

• Offerors must be registered in the System for Award Management (SAM).

• Cybersecurity Maturity Model Certification (CMMC) Level 2 (C3PAO) is required for all information systems processing, storing, or transmitting Federal Contract Information (FCI) or Controlled Unclassified Information (CUI).

• The solicitation includes numerous DFARS and FAR clauses, including those related to cybersecurity, intellectual property, organizational conflicts of interest, and contract administration.

• Attachments include Performance Work Statements (PWS), Quality Assurance Surveillance Plans (QASP), and various Contract Data Requirements Lists (CDRLs).

Statement of Work (SOW) / Performance Work Statement (PWS)

This document outlines the Quality Assurance Surveillance Plan (QASP) for the contract, detailing performance objectives, acceptable quality levels (AQLs), methods of surveillance, and remedies for non-compliance across various contract areas.

The QASP covers the following key performance areas:

• Timely and Accurate Program Management: Focuses on the submission and quality of deliverables such as the Quality Control Plan (QCP), Transition-In Plan, PEO DHMS Cost, Schedule, Performance (CSP) Report, Contractor Work Breakdown Structure (CWBS), Cost and Hour Report, Technical Data Report, Monthly Progress Report (MPR), and the Integrated Master Schedule (IMS).
• Comprehensive and Actionable Deployment Planning: Addresses the quality and timeliness of the Deployment Approach and Implementation Plan.
• Accurate Product Configuration Data Collection: Sets standards for the accuracy of product configuration data validation.
• Secure and Accurate Data Migration: Defines requirements for data accuracy and integrity during migration, with specific metrics for critical data elements and no permissible data loss for patient records.
• Safe and Timely Hardware Delivery: Covers the timeliness, condition (damage), and functionality of hardware deliveries, referencing DD Form 1149.
• Product Connectivity and Interface Validation: Ensures a high percentage of medical products function correctly upon validation.
• Quality of Training Program Development: Assesses the comprehensiveness and quality of the Training Curriculum and supporting Training Plan.
• User Training and Readiness: Measures the percentage of the total population trained for deployment readiness.
• Deployment Event Execution: Focuses on resolving 'Severity 1' (system-down) incidents and ensuring no patient safety issues during the post-deployment support period.
• Transition to Sustainment: Details requirements for the Transition-Out Plan, including the timely transfer of documentation and artifacts.

Each performance area includes specific Acceptable Quality Levels (AQLs) ranging from "Does Not Meet Most Contract Requirements" to "Meets & Exceeds Many Contract Requirements." These metrics include percentages for timeliness, accuracy, completeness, and functionality, with defined remedies for each level of non-compliance.

Not explicitly detailed in this document, but implied to cover the duration of the contract and associated task orders.

Surveillance methods include 100% inspection, random sampling, and review by the Contracting Officer's Representative (COR) and designated Government Subject Matter Experts (SMEs). Remedies range from rework until corrected with no change in price to PCO negotiation of "consideration" or contract termination for default.

Performance Work Statement (PWS)

This PWS outlines the requirements for a non-personal services contract to support the on-demand deployment of products within the Program Executive Office - Defense Healthcare Management Systems (PEO DHMS) portfolio. The goal is to ensure seamless and accurate data transmission across all roles of care, meeting mission needs for updating patient health records and aggregating data for Command and Control Situation Awareness (C2SA) reporting.

The contractor shall provide program management, deployment planning and execution, hardware delivery and connectivity, product connectivity and interface validation, user enablement services, and data management and migration. Services are applicable to Continental United States (CONUS) and Outside Continental United States (OCONUS) locations, covering various roles of care and facility types.

Key activities include:

• Program Management: Governance support, stakeholder engagement, risk and issue management, quality and change management, staffing, and contract reporting.
• Deployment Planning & Execution: Developing deployment approaches, readiness assessments, and detailed implementation plans.
• Product Configuration, Validation & Implementation: Configuring, validating, and implementing products, including network integration and hardware installation.
• Data Management & Migration: Securely managing, migrating, and validating clinical and administrative data.
• Cutover, Stabilization & Transition: Managing the transition to new products, providing post-deployment support, and handing off to sustainment teams.
• User Enablement Services: Providing training, adoption, and change management support, considering operational environments and a global user community.

Performance will be evaluated under a Quality Assurance Surveillance Plan (QASP). Specific performance standards and metrics will be defined in individual task orders. Deliverables include various plans (Deployment Approach, Implementation Plan, Transition-In/Out Plans), reports (Monthly Progress, CSP, Post-Deployment Stabilization), and data (Configuration Data, Training Certificates).

• Period of Performance (PoP): One (1) base year of 12 months and four (4) 12-month option years.

• Transition-in Period: 30 days from task order award.

• Place of Performance: To be identified in individual task orders.

• Security: Compliance with DoD cybersecurity requirements, including NIST SP 800-171, CMMC Level 2, and potential classified work. Personnel security screenings and background investigations are required.

• Data Rights: Government shall have unlimited rights to all data, documents, and materials produced.

• IT & Security: Specific ADP/IT levels and position sensitivity designations will be detailed in task orders. Compliance with DoD Directives and Manuals for cybersecurity workforce qualification and Information Assurance (IA) certification is mandatory.

• Contractor Furnished Items: The contractor shall furnish all supplies, materials, equipment, facilities, and services.

• Reporting: Includes Integrated Master Schedule (IMS), Cost, Schedule, Performance (CSP) Reports, Contractor Work Breakdown Structure (CWBS), and Cost and Software Data Reporting (CSDR) where applicable.

• Data Handling: Strict adherence to regulations regarding Personally Identifiable Information (PII), Protected Health Information (PHI), Controlled Unclassified Information (CUI), and breach response protocols.

• Training: Mandatory training for all personnel, including Privacy Act, HIPAA, and cybersecurity requirements.

Form / Attachment / Pricing Sheet

This document is a Contract Data Requirements List (CDRL) that specifies the requirements for submitting a Technical Data Report (TDR). It outlines the data item number, title, authority, and submission details for the TDR.

• Data Item Number: CDRL A009
• Title: Technical Data Report (TDR)
• Subtitle: Technical Data Reporting
• Authority: DI-MGMT-82165 (or most recently approved version) and the OSD Deputy Director, Cost Assessment (DDCA)-approved contract CSDR Plan.
• Format: The required file format is specified in the Data Item Description (DID), unless the DDCA-approved CSDR plan specifies another format. The DID is available at https://cade.osd.mil/csdrreportingguidance/dids.html.
• Submission: Technical Data Reports must be submitted electronically using the CADE CSDR Submit-Review System. Only unclassified technical data may be uploaded.
• Frequency: As specified in the OSD DDCA-approved CSDR plan and the contract. "As of Dates" and "Due Dates" are notional and subject to change, driven by submission event names.
• Distribution: Addressed to PEO DHMS Cost, Schedule, Performance Report, submitted electronically to the COR and the email box dha.ncr.PEO-DHMS.list.csp-data-reporting-owners@health.mil.

This CDRL details the specific requirements for preparing and submitting Technical Data Reports. Bidders must understand these requirements, including the use of the CADE system and the CSDR plan, to ensure compliance with contract obligations related to technical data submission. It also highlights the need for contractors to coordinate with the CWIPT and subcontractors for CSDR plan preparation and submission.

Form / Attachment / Pricing Sheet

This document is a DHA Contractor Non-Disclosure Agreement (NDA) that individuals performing under a contract with the Defense Health Agency (DHA) must sign. It outlines the terms and conditions for accessing, handling, and safeguarding sensitive or proprietary information belonging to the Government or other contractors.

• Defines "sensitive information" broadly, including but not limited to Protected Health Information (PHI) and For Official Use Only (FOUO) data.
• Requires individuals to agree not to discuss, divulge, or disclose such information to unauthorized persons.
• Acknowledges that unauthorized disclosure can cause irreparable injury.
• States that the Government may seek legal remedies to enforce the agreement.
• Outlines exceptions to the non-disclosure obligations (e.g., public domain information, prior written approval, independently developed information, court order).
• Requires individuals to inform prospective employers of their continuing obligations.
• Includes signature blocks for the employee/subcontractor employee, business entity, and a witness.

Bidders should be aware that personnel performing work under this contract will be required to sign this NDA. It signifies the importance of protecting sensitive government and contractor information and may have implications for personnel vetting and onboarding processes. Understanding these obligations is crucial for compliance.

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the viewer. It provides instructions for upgrading Adobe Reader or visiting a support URL.

This document is not relevant to bidders as it does not contain any information about the opportunity, requirements, or submission details. It appears to be a technical issue with the document rendering.

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the current PDF viewer. It provides instructions on how to upgrade to the latest version of Adobe Reader or seek further assistance.

This document is not directly relevant to the opportunity's requirements or scope. It serves as a technical notification and does not contain information that bidders can use to prepare a proposal or understand the procurement.

Other / Unclassified

This document is a placeholder page indicating that the PDF viewer may not be able to display the document's content. It suggests upgrading to the latest version of Adobe Reader or visiting a provided link for assistance.

This document does not contain substantive information related to the SAM.gov opportunity. It is a technical message related to PDF rendering and does not provide details on requirements, scope, or submission instructions for bidders.

Questions & Answers / Clarifications

This document is a Q&A log providing responses to prospective vendors' questions regarding the "HT003826RE001" solicitation for Program Executive Office (PEO) Defense Healthcare Management Systems (DHMS) Deployment Solutions. The questions and answers were submitted and replied to between March 5, 2026, and March 24, 2026.

• Facility Clearance (FCL) and CMMC: The current IDIQ PWS does not require an FCL, but task orders may delineate this requirement. CMMC Level 2 is anticipated for task orders.
• Task Order PWS: Each multiple award contract (MAC) holder will receive the same IDIQ PWS as an attachment. Specificity will be provided at each task order level.
• Bidscale Portal: The government will consider recommendations for primary and backup Bidscale accounts and support processes for access issues.
• Page Limits and Line Numbering: Line numbering applies to all volumes, and page limits apply per volume unless an exception is noted.
• AI Tools: AI tools will be used solely as an administrative aid; all evaluation judgments will be made by Government personnel. Proposal data will not be used to train AI models.
• Small Business Participation: The government is considering using Small Business Participation as an evaluation factor for the IDIQ competition. Specifics on task order evaluation and reporting are being considered.
• Organizational Conflict of Interest (OCI): OCI declarations are not required for draft RFP feedback. "Teams" refers to anyone directly employed by an offeror or subcontractor. The government is revising Attachment 16 to provide additional clarity on OCI declarations.
• Challenge Scenarios: Specific details for Challenge Scenarios 1a and 1b (e.g., hosting location, data exchange, network constraints, hardware assumptions) are clarified, with some details to be provided at the task order level.
• Hardware Procurement: The government will provide and image hardware for Challenge Scenarios 1a and 1b. For other task orders, hardware procurement responsibilities will be defined at the task order level, with the government providing network infrastructure.
• Training: Existing training curriculum and materials are available, but offerors may need to tailor or develop new content. Training environments will be specified at the task order level.
• Task Order Structure: Task orders may be grouped by product, region, or other logical manner supporting end-to-end deployments. Task orders will be competed among all contract holders, with no small business set-asides anticipated at the task order level.

These Q&As provide clarifications and address concerns regarding various aspects of the solicitation, including technical requirements, submission instructions, evaluation criteria, and contractual obligations. The government indicated that some sections will be revised in the combined synopsis/solicitation based on industry feedback.

Questions & Answers / Clarifications

This document is a Q&A Log for the Program Executive Office (PEO) Defense Healthcare Management Systems (DHMS) Deployment Solutions opportunity (HT003826RE001), dated March 19, 2026. It addresses questions submitted by prospective vendors regarding the draft Request for Proposal (RFP).

• Facility Clearance (FCL): The current IDIQ PWS does not require an FCL, but requirements will be determined at the task order level.
• CMMC Level: CMMC Level 2 is anticipated for task orders, with implementation potentially beginning November 10, 2026.
• PWS for Task Orders: The IDIQ PWS provides the scope of end-to-end tasking. Specificity will be provided in individual task order PWS documents.
• Bidscale Submission Portal: The government will consider recommendations for allowing primary and backup Bidscale accounts and clarifying support processes for access issues.
• Page Limits & Line Numbering: Page limits apply to the Volume unless an exception is noted. Line numbering applies to all Volumes.
• AI Tools in Evaluation: AI tools will be used solely as an administrative aid; all evaluation judgments will be made by Government personnel. Proposal data will not be used to train AI models.
• Small Business Participation: The government is considering the practicality of using Small Business Participation as an evaluation factor for the IDIQ competition.
• Organizational Conflict of Interest (OCI): OCI declarations are not required for draft RFP feedback. "Teams" refers to anyone directly employed by an offeror or subcontractor. Potential OCI exists with awarded contracts supporting mid-office/back-office functions.
• Task Order Structure: Task orders may be grouped by product, region, or other logical manner supporting end-to-end deployments. Specificity will vary by task order.
• Evaluation of Scalability: The government is revising 52.212-1 to define scalable, innovative, feasible, and coherent approaches for evaluation.
• Incumbent Contractors: Several contractors have performed aspects of this acquisition under different contract vehicles.
• File Size Limitations: Bidscale has a 1.5 GB per file limit.
• Amendments: Amendments will be acknowledged by digital signature on the SF 30 Box 15.
• Support Contractor Access Consent Form: Permission should be included in the cover letter.
• Deployment Scale: Specificity regarding deployment scale, concurrency, and operational tempo will vary by product and task order.
• Training Environment: Any requirement for the contractor to provide and/or maintain a training environment will be specified at the task order.
• Data Migration: Specificity regarding data volumes, legacy sources, and validation will vary by task order.
• Cybersecurity/RMF: The contractor will not be responsible for authorization packages or defining RMF documentation responsibilities, but must comply with implemented security controls.
• Technical Acceptability: 52.212-2 provides the minimum criteria for technical acceptability for each evaluation factor.
• Proposal Page Limitations: Graphics, diagrams, and tables count toward page limits. Font size limitations apply to all narrative elements, graphics, art, figures, imported charts, and any other graphical representation that includes text.
• AI Use in Evaluation: AI tools will be used solely for administrative summarization, not to assist evaluators in identifying evaluation themes.
• Bidscale Contingency: Contingency instructions are located in 52.212-1 Section 2.2 Paragraph 3. Early submissions are encouraged.
• Deployment Approach Detail: Offerors shall propose the necessary details to meet minimum evaluation criteria listed in 52.212-2, Factor 1 Challenge Scenario, based on assumptions and page limitations.
• Subcontractor Commitments: Teaming Agreements can be included as part of the Contract Document Volume.
• Deployment Timelines/Milestones: Offerors shall propose estimated deployment timelines based on the scenario, assumptions, and response.
• Risk Management: Offerors shall address risk management in their proposed approach for Factor 1, Sub-Factor 1 Program Management and Governance.
• User Adoption: User adoption considerations are addressed in CDRL A003.
• Infrastructure Integration: Network configuration, hardware integration, and interoperability expectations are addressed in PWS Section 3.3.1.
• Multi-Site Coordination: Offerors shall review scenarios and provide an approach based on business decisions.
• Document Availability: Issues with document rendering may be related to browser settings; downloading and opening in Adobe is recommended.
• End-to-End Deployment Services: The government anticipates task order awardees to provide end-to-end services for specific deployments, as delineated in task orders.

These clarifications and responses will inform vendor proposals and may lead to revisions in the final solicitation documents. Vendors should review these Q&As carefully to ensure their proposals address all clarified requirements and expectations.

Solicitation / RFP / RFQ

This solicitation seeks full and open competitive offers for the Program Executive Office – Defense Healthcare Management System (PEO DHMS) Deployment Solutions. The government intends to award multiple award contracts to all qualifying offerors. Price will not be an evaluation factor.

The solicitation requires offerors to propose innovative and scalable deployment plans for two interconnected lines of effort:

• Federal EHR product modernization and deployment: Implementation of the Federal EHR at established, high-capacity treatment facilities, including a large OCONUS medical center, community hospitals, and outpatient clinics. This includes full-spectrum healthcare services and integration with complex hardware and IT systems.
• OpMed products' modernization and deployment: Mobile and interoperable OpMed solutions for deployed and tactical environments (CONUS and OCONUS), including theater hospitals, hospital ships, and submarines. This involves integrating with complex Service-specific hardware and diverse networks, ensuring system security, and addressing low-to-no touch remote deployments.

This is an Indefinite Delivery, Indefinite Quantity (IDIQ) multiple award contract.

• Submission Portal: Proposals must be submitted electronically via the Bidscale portal. Offerors must request an account by emailing customersuccess@bidscale.com at least 72 hours before the deadline.

• Evaluation Factors: Proposals will be evaluated on the following factors:

  • Factor 1: Challenge Scenario (covering both Federal EHR and OpMed deployments)
  • Factor 2: Small Business Participation (minimum goals: Total Small Business - 30%, Small Business - 12%, HUBZone - 3%, Service-Disabled Veteran-Owned Small Business - 5%, Small Disadvantaged Business - 5%, Women-Owned Small Business - 5%)
  • Factor 3: Supply Chain Risk

• Award Basis: Award will be made to each and all qualifying offerors whose proposals are determined to be Technically Acceptable and responsible. A proposal must be rated "Acceptable" in all evaluation factors. Offerors rated "Unacceptable" in any factor will not be eligible for award, with specific allowances for Factor 1 if an acceptable rating is achieved in at least one scenario.

• Proposal Format: Proposals must adhere to specific page limitations, formatting, and content requirements outlined in the solicitation, including specific volumes for each factor.

• Period of Acceptance: Offers must be held firm for 180 calendar days from the date specified for receipt of offers.

• Offerors must be registered in the System for Award Management (SAM) at the time of proposal submission.

• Specific small business participation goals are outlined for Factor 2.

• All questions must be submitted to the Contract Specialist via email. Offerors are responsible for monitoring SAM.gov for responses and any amendments.

• The Government may use AI tools for administrative purposes during evaluation, but all judgments will be made by Government personnel.

• Organizational Conflict of Interest (OCI) will be assessed, and unmitigated conflicts may result in withholding award.

Form / Attachment / Pricing Sheet

This document appears to be an Excel spreadsheet containing feedback or comments related to a solicitation, and also lists various Contract Data Requirements List (CDRL) items. It may serve as a reference for bidders regarding specific requirements or areas for potential feedback.

• The 'Feedback' sheet contains columns for Document Name, Page #, Section Name, Paragraph or Line Number, and Comment/Feedback, suggesting it's a log of comments on a solicitation document.
• The 'Sheet2' lists various CDRL items (A001 through A011) and references "Solicitation" and "PWS" along with "52.212-1&-2", indicating these are related to contract requirements and performance work statements.

This document provides insight into potential areas of focus or feedback for the solicitation and PWS. The listed CDRLs indicate specific data deliverables that may be required under the contract. Bidders should review these items to understand the expected documentation and reporting requirements.

Form / Attachment / Pricing Sheet

This document, Attachment 16, is an Organizational Conflict of Interest (OCI) Declaration and Disclosure Statement required for solicitation HT003826RE001. Its purpose is for the Government to vet all offerors and ensure they do not have an OCI that would disqualify them from competing for this procurement, as per Revolutionary Federal Acquisition Regulation (FAR) Overhaul (RFO) 9.5.

• Offerors must complete this form to declare whether they have an Organizational Conflict of Interest.

• The form requires the name of the authorized representative and the company name.

• Offerors must attest that they have not had access to non-public information regarding the solicitation that would provide an unfair advantage, nor have they provided services that would influence the competition.

• Alternatively, if an OCI exists, the offeror must provide a separate disclosure statement attached to this form detailing all relevant information.

• Mandatory Submission: Failure to provide this statement, or providing incomplete or misrepresented information, may result in the offeror being deemed ineligible for award.

• Disclosure Requirement: Bidders must carefully review their company's activities and potential conflicts of interest related to solicitation HT003826RE001 and accurately declare this information. This includes any entities on their team.

• Compliance: This form is critical for ensuring compliance with federal acquisition regulations regarding conflicts of interest.

Other / Unclassified

This document is a placeholder or error message indicating that the PDF content could not be displayed by the viewer. It provides instructions for upgrading Adobe Reader or visiting a support URL.

This document does not contain substantive information related to the SAM.gov opportunity. It is a technical message related to PDF rendering and does not provide details on requirements, deliverables, or submission instructions for bidders.

Solicitation / RFP / RFQ

This solicitation seeks full and open competitive offers for the Program Executive Office – Defense Healthcare Management System (PEO DHMS) Deployment Solutions. The government intends to award multiple award contracts to all qualifying offerors. Price will not be an evaluation factor.

Offerors must propose a deployment approach for two interconnected lines of effort:

• Federal EHR Modernization and Deployment: Full implementation of the Federal EHR at established, high-capacity treatment facilities, including a large OCONUS medical center and associated community hospitals and clinics. This includes full-spectrum healthcare services and integration with complex hardware and IT systems.

• OpMed Products Modernization and Deployment: Delivery of mobile and interoperable OpMed solutions to medical forces in deployed and tactical environments globally. This includes theater hospitals, hospital ships, and submarines, with deployments managed across multiple sites and countries.

• The contract will be an Indefinite Delivery, Indefinite Quantity (IDIQ) multiple award contract.

• The period of acceptance of offers is 180 calendar days from the date specified for receipt of offers.

• Submission Portal: Proposals must be submitted electronically via the Bidscale portal. Offerors must request an account by emailing customersuccess@bidscale.com.

• Deadlines: Specific dates and times for account creation requests and proposal submission are to be inserted.

• Evaluation Factors: Proposals will be evaluated on the following factors:

  • Factor 1: Challenge Scenario (Acceptable/Unacceptable rating for two scenarios: Federal EHR and OpMed)
  • Factor 2: Small Business Participation (minimum 30% total small business goal)
  • Factor 3: Supply Chain Risk

• Award Basis: Award will be made to technically acceptable and responsible offerors. A proposal must receive an "Acceptable" rating in all evaluation factors. For Factor 1, an "Acceptable" rating in at least one of the two challenge scenarios is required.

• Discussions: The government does not intend to hold discussions but reserves the right to do so. Offerors are advised to submit their best terms initially.

• Offerors must be registered in the System for Award Management (SAM).

• Small business participation goals are outlined, with a minimum of 30% total small business participation required.

• Points of Contact (POCs) are provided for questions and concerns.

• All questions must be submitted via email to dha.ncr.co.mbx.cd-dhms-contracting@health.mil.

• The document outlines specific formatting, page limitations, and content requirements for proposal volumes.

• Offerors must address Organizational Conflict of Interest (OCI) and provide a Small Business Subcontracting Plan.

Statement of Work (SOW) / Performance Work Statement (PWS)

This Performance Work Statement (PWS) outlines the requirements for a non-personal services contract to provide services and materials necessary to support and execute the on-demand deployment of Defense Healthcare Management Systems (DHMS) products and related components. The overarching goal is to deliver fully functional and adopted solutions that ensure seamless and accurate data transmission across all roles of care, meeting mission needs and supporting critical health record updates and data aggregation for Command and Control Situation Awareness (C2SA) reporting.

• Program Management: Establishing a program management framework, designating a Program Manager, and providing support for governance, stakeholder engagement, risk and issue management, and quality/change management.

• Deployment Planning and Execution: Developing and executing deployment approaches, implementation plans, readiness assessments, configuration, validation, and cutover activities.

• Stabilization and Transition: Providing post-deployment stabilization support and managing the transition to sustainment teams.

• Hardware Delivery and Connectivity: Managing procurement, logistics, installation, and network integration of hardware.

• Product Connectivity and Interface Validation: Testing data mapping between products and validating medical device connectivity.

• User Enablement Services: Providing training, adoption, and user support services, including Human Systems Integration (HSI) alignment, consideration of operational environments, global user community support, and comprehensive training programs.

• Adoption and Change Management: Facilitating user adoption and change management to ensure smooth transitions and user buy-in.

• Data Management and Migration: Ensuring secure and accurate management, migration, and validation of clinical and administrative data.

• Period of Performance (PoP): One (1) Base Year of 12 months and four (4) 12-month option years.

• Place of Performance: Specific locations will be identified in individual Task Orders, covering Continental United States (CONUS) and Outside Continental United States (OCONUS) locations.

• Transition-in Period: 30 days from task order award for integration and onboarding.

• Transition-out Period: Contractor cooperation for orderly transition to a successor, including developing a Transition-out Plan.

• Security: Compliance with various security requirements, including NIST SP 800-171, CMMC, cybersecurity requirements, and personnel security clearances (Tier 1 or Tier 3 background investigations).

• Data Rights: Government has unlimited rights to all data, documents, and materials produced.

• Reporting: Monthly Progress Reports (CSP Report), Integrated Master Schedule (IMS), Contractor Work Breakdown Structure (CWBS), and Cost and Software Data Reporting (CSDR).