SAP MFR For Sole Source HCD Role 3 Servers_signed_Redacted.pdf

MEMORANDUM TO THE FILE

Subj: USE OF OTHER THAN FULL AND OPEN COMPETITION FOR AN

ACQUISITION UNDER THE SIMPLIFIED ACQUISITION THRESHOLD

I. BACKGROUND:

1. FAR 13.106-1(b)(1)(i) states for purchases not exceeding the simplified acquisition threshold, Contracting Officers may solicit from one source if the Contracting Officer determines that the circumstances of the contract action deem only one source reasonably available (e.g., urgency, exclusive licensing agreements, brand-name or industrial mobilization).

2. As required by FAR 13.106-3(b)(3)(i), this memorandum explains the absence of competition for this acquisition, as only one source will be solicited for this requirement and the requirement is not expected to exceed the simplified acquisition threshold.

The Government’s strategy when procuring the MHS GENESIS solution anticipated evaluating differing solutions that utilized some varying amount of centralized, regional, and local hosting instances, depending on a particular solution’s architecture. The solution that is being implemented utilizes a highly centralized and virtualized architecture that leverages a single primary data center at Tier 1 (with a back-up for redundancy only) while foregoing any regional or local hosting infrastructure with the exception of local caching to support COOP requirements. Further, the architecture of MHS GENESIS is highly virtualized at the client level, which drives a higher level of requirements related to application processing at the centralized, server level.

During the October 2015 DoD Senior Steering Group, and based on the technical analysis of the MHS GENESIS solution, and its market research, USD (AT&L) provided direction to implement a commercial hosting strategy instead of utilizing DISA. Based on the analysis, documented in the original J&A the Government determined that Cerner was the only commercial source available capable of meeting the Government’s requirements for the Tier 1 hosting, which resulted in significant revisions to the architecture of the solution over the subsequent years.

MHS GENESIS is replacing functionality of core legacy systems (AHLTA, CHCS, Essentris, AHLTA-T, TMIP-J, and others), and is being deployed to both fixed medical treatment facilities and operational medicine facilities worldwide. In addition to the solution being provided, the Leidos Partnership for Defense Health is providing services for the integration, configuration, testing, initial deployment, training, operational management, and sustainment of MHS GENESIS for the DoD.

On July 01, 2017, the Secretary of the VA issued a Determination and Findings (D&F) pursuant to 41 U.S.C. § 3304(a)(7) that it was in the public interest for VA to issue a solicitation directly to Cerner for the acquisition of the EHR system being deployed by the DoD, specifically the DHMSM DoD Healthcare Management System Modernization (DHMSM®) Program Management Office, in order to enable seamless healthcare to Veterans and qualified beneficiaries. On March 22, 2018, the Deputy Commandant for Mission Support – United States Coast Guard, formally requested to partner with PEO DHMS to implement MHS GENESIS for the USCG.

Given these major changes, it is absolutely essential to ensure consistency (the standard solution baseline) among the Agencies, and Military Services for Operational Medicine, to ensure the accessibility and reliability of the same patient data as well as to maintain continuity with the system’s upgrades and updates achieve the benefits of the standard solution sought by the various Agencies and Services. The standard solution baseline consists of, among other components, common “Best of Suite” and “Best of Breed” off-the-shelf software, common clinical application services, common interfaces and ESBs, and common shared infrastructure, that, when configured, results in much greater commonality in practical workflows, roles, order sets, plans, and reports, as well as the training materials that support them.

Suffice to say, the delivery of a Role 3 solution has been and is very complex, and extremely difficult. While the solution was expected to be delivered in 2016, given the factors above, a solution that works in a DIL environment remained elusive. Because the main MHS GENESIS solution is so heavily virtualized and centrally hosted, it depends on significant network infrastructure. The OpMed version, therefore, requires extensive reengineering that introduces many potential bugs and failure points. Now that the solution is finally ready to be delivered, it is even more essential that it is adequately tested to ensure it is completely ready to be deployed in warfighting environments.

II. DESCRIPTION OF ITEM OR SERVICE:

Four each of:

• 1x RPS217D-X22-A1 RUGGED PORTABLE SERVER

- DUAL 22-CORE XEON CPU

- 512GB REG ECC RAM

- 17.3 HD LCD WITH AR GLASS

- SEALED KEYBOARD & TOUCHPAD

- CAC READER

- INTEGRATED UPS BATTERY BACKUP

- 10 REMOVABLE HARD DRIVE BAYS

• 1x 1.92TB ENT SATA SSD

• 2x 7.68TB ENT SATA SSD

The server hardware being procured will support the hardware/software integration testing necessary to validate it for the Services as a supported server platform for the HCD Role 3 software solution. The server hardware will also support ongoing lifecycle testing, Operational Assessments (OAs) (including the JOMIS HCD OA scheduled to begin 22 January 2024), cybersecurity accreditation steps, and iterative demos and training to the Service communities.

The server hardware integrated with the HCD Role 3 EHR software solution (MHS GENESIS- Theater (MHSG-T)) creates a mobile, ruggedized, EHR appliance that can be instantiated at Services' Role 3 sites for documenting patient care. The server hardware meets the specifications necessary to run the HCD Role 3 EHR solution, enabling end users to provide, document and coordinate emergency and specialty surgery, intensive care, medical specialty care, and extended holding capacity, and robust ancillary support, thereby improving patient outcomes.

Additionally, the server hardware provides the ability to maintain back-up data for restoration in the event of a system failure.

Acquiring this server hardware enables the JOMIS PMO to: 1) deliver EHR software validated to perform on a specified hardware platform that can be deployed by all Services as an appliance;

2) deliver a ruggedized EHR appliance to all Services that can be easily maintained in the deployed environment; 3) conduct iterative product lifecycle testing to support initial deployment as well as iterative update/upgrade/patch releases; and 4) support EHR appliance demonstrations to the Services as well as training.

The USAF uses the Core Systems Rugged Portable Server to deploy the EHR software product.

III. THE DETERMINATION FOR USE OF OTHER THAN FULL AND OPEN

COMPETITION IS BASED ON THE FOLLOWING (select all that apply):

A. _X__ ONLY ONE RESPONSIBLE SOURCE (select all that apply):

1. ___ RESTRICTIVE RIGHTS. The source has established proprietary rights, limited rights in data, patent rights, copyrights or secret processes in the item or service required.

2. ___ EXCLUSIVE LICENSING AGREEMENTS. The item or service is only available from the Original Equipment Manufacturer (OEM), or there is only one authorized distributor or technical representative for the OEM.

3. __X_ OTHER REASONS.

Without this server hardware, the JOMIS PMO will be unable to fully test and validate EHR software functionality and performance on the target server hardware platform before software acceptance and deployment to the Services. This results in PMO JOMIS not being able to provide the Services with validated server hardware specifications and, therefore, the risk of Services not being able to deploy the EHR as well as the risk of Services procuring server hardware that cannot support the EHR. Additionally, if this server hardware is not acquired, then the EHR software may not be able to complete the Operational Assessment (OA) scheduled to begin 22 January 2024. While this may not be the only hardware required for the OA, at least the Air Force portion of the testing will require this hardware.

An Operational Assessment (OA) is an evaluation of operational effectiveness and operational suitability made by an independent Operational Test Agency (OTA), with user support as required, on other than production systems. Testing on representative hardware is part and parcel of an OA, and is essential for the results of the test to be meaningful.

B. ___ BRAND NAME. Item required must be a brand name product, or feature of a product, particular to one manufacturer.

C. ___UNUSUAL AND COMPELLING URGENCY. The supplies or services are of such unusual and compelling urgency that the Government would be seriously injured unless the agency is permitted to limit the number of sources from which it solicits bids or proposals.

Urgent requirements are supplies or services that will result in a work stoppage, or are mission critical and the routine processing time would result in injury to the Government. The determination that the procurement for the above item/service is an urgent and compelling requirement is based on the following:

IV. CERTIFICATIONS/APPROVALS:

A. Technical / Requirements Certification: I certify that the facts and representation under my cognizance which are included in this justification are complete and accurate to the best of my knowledge and belief.

Signature HCD Role 3 APM

B. Certification/Approval.

___________________ ___Matthew Hudson_____________________

Signature Contracting Officer and Gentleman