JOMIS_MEDCOP_RFI.pdf

HT0038-21-R-0003 MEDCOP

Request for Information

Medical Common Operating Picture

HT0038-21-R-0003

November 12, 2020

PART 1: EXECUTIVE SUMMARY

Requiring Activity: Program Executive Office- Defense Healthcare Management System’s (PEO DHMS) Joint Operational Medicine Information Systems (JOMIS) Program Management Office

Opportunity Title: Medical Common Operating Picture (MEDCOP)

Announcement Type: Request for Information

Solicitation Number: HT0038-21-R-0003

Important Dates Request for Information Posting Date: November 12, 2020 Request for Information Responses Due Date: 25 November 2020

The Problem

Operational Commanders lack timely, complete, actionable health information for operational decision-making, thereby putting troops at unnecessary risk to illness or injury and jeopardizing force strength and morale. PEO DHMS/ JOMIS requires a common operating picture to provide a single display of information shared by multiple commands and entities to facilitate collaborative planning, assist in situational awareness, and enable effective decision-making for appropriate mission execution.

The current legacy information system, Medical Situational Awareness in the Theater (MSAT), does not meet the entirety of needs for end users to conduct Medical Command and Control and Medical Situational Awareness business processes. MSAT does not efficiently obtain information from various data sources.

Rather, MSAT requires intensive human manipulation and cannot aggregate the necessary information for effective decision making in a timely manner.

Another issue with MSAT is that it allows different agencies to provide data sporadically and this makes it difficult to sort, understand, and generate actionable knowledge within operational timeframes from the vast amount of existing raw data. The inability to integrate the Medical Common Operating Picture with Joint Command and Control, and share this data with Coalition Partners and other non-DOD agencies is a commonly reported issue and known gap submitted by current end users of MSAT. These drawbacks result in poor user adoption and unreliable data

PEO DHMS/ JOMIS requires a Medical Common Operating Picture (MEDCOP) that will facilitate Medical Command and Control and Medical Situational Awareness business processes to produce a stream of actionable knowledge as a result of synergy between appropriate personnel, logistics, medical and other systems in a Joint-All Domain Command and Control environment. Or, in laymen’s terms, the proposed solution must be able to obtain data from various sources and create an integrated picture of the data related to personnel, supply chain, and other data sets. The solution must provide PEO DHMS/ JOMIS visibility from one system to see a full snapshot across all data sets to provide decision support for operational commanders.

The goal of MEDCOP is to provide geospatial and dashboard-based data visualization tools enabling collaboration, reporting and predictive analytics to enable command decision making, future planning and the identification and documentation of lessons learned in a medically-relevant common operating picture. PEO DHMS/JOMIS seeks a software solution that is capable of supporting the current and future medical threats in a Joint-All Domain Command and Control environment.

A proposed solution must provide relevant information from health threat intelligence, disposition of forces and other operational sources to inform medical operations, medical logistics, the status of medical facilities and the status of Health Service Support and Force Health Protection. A medically-relevant globally integrated MEDCOP which generates shared understanding throughout the medical enterprise supporting the full range of military operations must incorporate the technical capabilities listed below.

Desired Solution Technical Capabilities

With the objective of shortening the time it takes to gather medically relevant data and information from days to minutes, the desired solution should include the following features:

Security

• A production platform that can be hosted on Secret Internet Protocol Routing Network

• A DevSecOps Environment with Continuous Authority to Operate (cATO)

• Application deployment across concurrent information impact level environments (i.e. simultaneous

Impact Level (IL4, IL-5, and IL-6 production environments), and bi-directional cross domain solutions between impact levels

Network Infrastructure and Interoperability

• Continuous integration/continuous delivery/deployment (CI/CD)

• Distributed data replication

• Cloud native computing

• Container orchestration using an open source system

• Microservice architecture and development using an open source service mesh

• Scalability

• Enterprise Data Integration Standards and Best Practices

• Artificial Intelligence (AI) / Machine Learning (ML)

Agile Development

• Agile software development in small iterations

• Infrastructure as Code (IaaC) managed interfaces between commercial and military networks (e.g.

utilizing a Zero Trust Security Model)

User Experience

• Business Process Automation

• User-centered design

• Test-driven development

• Integrated business features, such as chat, file-sharing and collaboration

Questions and feedback are encouraged throughout this acquisition process. The solicitation process will be iterative with a draft solicitation, comment period, and an industry engagement.

Anticipated Award: The solicitation for this effort may result in single or multiple awards. Resulting contracts will be new Indefinite Delivery/Indefinite-Quantity contract(s) using FAR and DFARS procedures.

Request for Information Response Email: indy.m.toliver2.civ@mail.mil mailto:indy.m.toliver2.civ@mail.mil

PART 2: RELEVANT INFORMATION

A. Background

Operational medicine is the application of routine and emergency medical practices in complex dynamic environments, such as U.S. Navy ships, hospital ships, submarines, theatre hospitals, and forward resuscitative sites worldwide in order to maintain the health of military personnel. Operational medicine services include, but are not limited to, preventive, routine, emergency, surgical, en-route care, and diagnostic care. Operational medicine systems provide Commanders and medical professionals with integrated, timely, and accurate information to make critical Command and Control and medical decisions.

When implemented, the systems are intended to function in constrained, intermittent, and non-existent communications environments while providing access to authoritative sources of clinical and operational data. JOMIS will provide an end-to-end software solution to support the medical business practices and operational medicine capabilities in deployed environments. The Joint Publication 04-02, Health Services Support, provides guidance on how the Military Health System and joint force plan, prepare, and execute health service support across the range of military operations, humanitarian assistance, and disaster response. Increased efficacy and efficiency in knowledge management conducted in support of operational health care functions is critical to enable informed and timely decisions regarding the delivery of health care in an Area of Responsibility /Joint Operational Area.

Today, operational medicine capabilities in deployed environments are supported by the Theater Medical Information Program – Joint (TMIP-J) Program. TMIP-J is a systems framework that integrates components of the Military Health System sustaining base systems and the Services´ medical information systems to ensure timely interoperable medical support for mobilization, deployment, and sustainment of all Theater and deployed forces. This Operational Medicine environment includes an estimated 450+ Forward & Resuscitative Sites, 300+ Ships, 2 Hospital Ships, 6 Theater Hospitals and 3 Aeromedical Staging units deployed across all Geographic Combatant Commands.

B. Description of Need

In pursuit of this objective to modernize Medical Command and Control and Medical Situational Awareness in support of critical national security missions, the JOMIS PMO will develop a Joint, interactive, decision support platform that arms Command Surgeons and Medical Commanders with real-time medical surveillance and medical operations visibility that enables more-informed decisions leading to mission success. The solution will enable real-time decision making using integrated data that provides a Medical Common Operating Picture.

Any proposed solution must rely on robust agile software development and DevSecOps techniques and incorporate input from key stakeholders including Defense Health Agency, The Office of the Joint Staff Surgeon, Combatant Command Surgeons and the Services’ Surgeons General. The proposed solution will be a new operational capability that will modernize Medical Command and Control and Medical Situational Awareness for the Operational Medicine community of interest. The Government intends to apply agile development activity to create, design, develop, demonstrate the operational utility of, and deploy the Medical Common Operating Picture Software System across the Department of Defense

SECTION 3: REQUEST FOR INFORMATION PROCESS

To conduct a market survey and determine the best solicitation approach, PEO DHMS/ JOMIS seeks responses to this Request for Information. PEO DHMS/JOMIS strongly encourages interested parties to provide feedback or questions regarding the needed solution.

A. Requested Information

The JOMIS PMO is interested in learning about software products that can meet operational medicine capabilities supporting Medical Command and Control and Medical Situational Awareness as described herein. In response to this Request for Information, please provide a white paper that adheres to the guidelines listed below.

B. Response Guidelines

Interested parties are requested to respond to this RFI with a white paper in accordance with the White Paper Format provided in Appendix 1. Submissions should be single spaced, 11-point type with at least one-inch margins on 8 1/2” X 11” page size. Cover pages are not included in the page limit. The response should not exceed a 5 MB e-mail limit for all items associated with the Request for Information response. Responses must specifically describe the contractor’s ability to meet the requirements of this effort. Oral communications are not permissible. Submissions shall adhere to the following page limits:

• Section 1 shall not exceed one (1) page with the requested vendor demographic information

• Section 2 shall not exceed two (2) pages for responses to acquisition questions

• Section 3 shall not exceed four (4) pages for responses to technical capability questions and

• Section 4 shall not exceed one (1) page for additional recommendations.

Companies who wish to respond to this Request for Information should send responses via email no later than November 25, 2020 to Indy Toliver at indy.m.toliver2.civ@mail.mil. Responses may be utilized in the development of future JOMIS draft solicitations. The Government will not reimburse companies for any costs associated with the development or submission of their responses. Questions regarding this Request for Information shall be submitted via email to Indy Toliver at indy.m.toliver2.civ@mail.mil. The Government does not guarantee that questions received after November 19, 2020 will be answered.

1. Additional Resources

To assist with these Request for Information questions- upon request to Indy Toliver at indy.m.toliver2.civ@mail.mil- the JOMIS PMO will provide a copy of the Theater Medical Information Requirements– Information Systems – Capabilities Development Document and the Medical Command and Control and Medical Situational Awareness Capability Needs Statement.

2. Program office contact regarding responses

JOMIS PMO representatives may choose to meet with Request for Information Respondents and hold one-on-one discussions. Such discussions would only be intended to obtain further understanding of potential capability to meet the operational medicine requirements, including any development, integration, and certification risk.

C. Organizational Conflict of Interest

Please see FAR 9.5 and DFARS 209.5 for background information related to organizational conflicts of interest. PEO DHMS/JOMIS anticipates the final solicitation will require the execution of corporate nondisclosure agreements and non-compete commitments, and the resulting contract(s) will require the execution of appropriate associate agreements with prime-mission product partners to gain access to technical data and other proprietary information generated during the performance of those contracts.

Additionally, respondents to this notice should be aware that PEO DHMS/JOMIS may utilize contractor support personnel from the below listed companies to review responses and information submitted.

• The MITRE Corporation

• Booz Allen Hamilton, Inc.

• SeKON Enterprise

• Deloitte Consulting

• Axiom

These companies and individual employees are bound contractually by Organizational Conflict of Interest and disclosure clauses with respect to proprietary information, and they will take all reasonable action necessary to preclude unauthorized use or disclosure of a respondent’s proprietary data. Request for information responses MUST clearly state whether permission is granted allowing the program office support contractors identified below access to any proprietary information.

SECTION 4: DISCLAIMER

This Request for Information is not a Solicitation and should not be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals nor will any award be made as a result of this Request for Information. All information contained in the Request for Information is preliminary as well as subject to modification and is in no way binding on the Government. The Government does not intend to pay for information received in response to this notice.

Responders to this invitation are solely responsible for all expenses associated with responding to this Request for Information. This Request for Information will be the basis for collecting information on capabilities available and is issued solely for information and planning purposes.

Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this Request for Information that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned. Responses to this Request for Information are not offers and cannot be accepted by the Government to form a binding contract.

APPENDIX 1: WHITE PAPER FORMAT

Section 1.0 Vendor Information (Maximum Page Limit: 1)

Company Name: _______________ Company Address : __________________ Primary Point of Contact: ________________ Phone Number:_________________________ Email Address: _________________________ Cage Code: ____________________________

DUNS: ___________________________________

Suggested NAICS: __________________________ Projected NAICS: 54151 Company website: ___________________________ Other Classifications (e.g. large business, small business, SDB, HUBZone, 8(a), SDVOSB, WOSB, etc.): ____________________________________________________________

List Government-wide DOD, DHA, PEO DHMS contracts that you support as a prime contractor or subcontractor (include projects in which you are partnered on as DOD DevSecOps platform or COTS DevSecOps Platform): ______________________________________________________

List your interest in this acquisition as a Prime Subcontractor, Team Arrangement, etc.: ____________

Are you interested in a Reverse Industry Day: ________________________________________

Section 2.0 Acquisition Strategy (Maximum Page Limit: 2)

2.1 DoD or COTS DevSecOps Platform

Please provide feedback on the Government’s intent to leverage a DoD or COTS DevSecOps Platform, including your company’s ability to support or provide those capabilities and the specific benefits to JOMIS

PMO.

2.2 Recommended Acquisition Strategy

Please provide feedback on the preferred approaches to fulfill this acquisition

2.3 Other Transactions for Prototypes- United States Code Title 10 Section 2371b (d) Please describe your approach to satisfying USC Title 10 applicability for Other Transactions authority.

Describe whether your company qualifies as a non-traditional defense contractor and/or your approach for including nontraditional defense contractors, including small businesses, and/or implementing cost sharing.

2.4 Data Rights

Please describe the approach you’ll use to ensure the Government maintains the right level of data rights ownership. Describe how this approach is used with other program management offices or organizations that use your solution.

Section 3.0 Technical Capability Questions (4 Page Limit)

3.1 Medical Command and Control & Medical Situational Awareness Experience Please explain your company’s experience supporting Operational Medicine in the use of Medical Command and Control (MedC2) and Medical Situational Awareness (MedSA) capabilities, include insights, recommendations, strategies and past performance. What are the challenges, gaps and pains points associated with MedC2/MedSA and what does a modernized solution provide leaders at all echelons. Does your solution enable workflows and functions as outlined in Joint Publication Health Services0 4.02? Does your solution enable aggregated data reporting? Specifically, describe your approach to developing a solution that brings together these functions.

3.2 Data Interface Management

Please explain your company’s experience and ability to manage data interfaces between commercial, military government systems. Describe which data partners are relevant to providing a MEDCOP and how you would integrate that data. Describe your agile or lean methods to document and manage this integration.

Is your solution open-source, open standards are easily integrated? Specifically, describe approaches to ensure near-real-time access and data exchanges between unclassified and classified data sources.

3.3 Continuous Integration/Continuous Delivery (CI/CD) Strategy/Approach Provide a description of your approach to managing the CI/CD process for this system. Does your company have a DevSecOps platform, does it provide a continuous Authority to Operate (cATO)? On what domains and classification levels?

3.4 Agile Framework and Methodology

Please describe how you would utilize an Agile Development Methodology to speed capability into production. Please include proposed timelines for a Minimum Viable Product (MVP) and a Minimum Viable Capabilities Release (MVCR). How do you sustain these capabilities to remain cost efficient and ensure you can deliver new capabilities at the speed of relevance?

3.5 How Automated Testing is utilized in the Development Process Please describe how automated testing is used throughout CD/CI? How are outcomes from automated tests used in the CD/CI process to determine movement of the configuration items thru the CD/CI process?

Describe the implications of DOT&E and JITC involvement in this process, what is their role?

3.6 Solution Support Infrastructure

Provide a description of the manner in which User Feedback is collected and integrated into the development cycle. How is User feedback implemented in your backlog and prioritized? Does your solution and company provide a service desk? Please describe the operations, types of issues and incidences typically reported by end users.

3.7 Product Backlog Management

Provide a description of how you support backlog management, grooming and your experience in integrating with Government software development management tools. Specific examples are encouraged.

3.8 Distributed Management, Cloud Infrastructure, Delayed/ Disconnected, Intermittently-Connected Low Bandwidth (DIL) and Infrastructure Costs The capability will need to be able to be accessible by MedC2/MedSA end users across the DoD describe your approach to ensure access during periods of growth and contraction of Cloud infrastructure resources as well as how other approaches could be implemented to meet the current and future requirements. Does your solution work in the DIL environment? If so, please describe where and how this operates.

3.9 Artificial Intelligence/Machine Learning

Provide a description of your approach to integrating AI and ML into MedC2 and MedSA workflows.

Specifically describe how this would impact Sr. Medical Leaders decisions. What types of data would you apply these technologies to and what would those impacts mean for the medical community? Describe your company’s experience with AI/ML on other solutions and the outcomes they have provided.

3.10 Cross-Domain Services

Provide a description of your ability to automate data from unclassified to classified levels. Which tools and approach would you use to automate data movement, how would you enable capability at the unclassified level to be collected, integrated and synthesized and ensure data replication and aggregation on the classified domains. Please describe any solution for automating data movement from the Classified to REL or Unclassified levels.

3.11 Mission Command Services

Provide a description of your approach to enabling medical mission command in your platform. What are the tools you would use to ensure information flowed vertically, horizontally and how would you enable the inclusion of coalition partners? Does your solution provide an enterprise messaging or communication capability? Does your solution provide file sharing, data library or ability to collaborate with other users?

Does your solution provide dashboards? Please describe all capabilities related to command and control.

3.12 Product Supportability

Describe your approach to deploying, sustaining and supporting end users of your solution. What methods would you use to train DoD end users? How would you communicate with stakeholders, how would you sustain usage?

3.13 Stakeholder / End User Domain

Describe your understanding of the stakeholders in Operational Medicine. Specifically, in MedC2 and MedSA, what approach would you take to understanding those user personas, managing the change from legacy to your solution?

Section 4.0 Recommendations (1 Page Limit) Provide any other recommended acquisition or technical approaches that the Government should consider for this effort.

APPENDIX 2: CAPABILITY DESCRIPTIONS

Medical Command & Control and Medical Situational Awareness

The Government is interested in understanding the state of medical situational awareness capabilities in the Operational Medicine environment that meets corresponding capability requirements, as further described in the Theater Medical Information Requirement Capability Development Document.

The medical common operating picture (MEDCOP) development will modernize capabilities found in the legacy Medical Situational Awareness in Theater (MSAT) solution. Through a human-centered design approach, the JOMIS PMO will utilize agile software development methodologies to effectively manage user interactions through an intuitive user interface that is responsive to each user’s individual requirements. The MEDCOP system will replace MSAT’s capabilities and functionality and deliver a solution to meet current and future needs in support of the full range of military operations. DoD users have identified challenges associated with the MSAT platform that was underutilized, not fully adopted and did not meet the entirety of needs of the OpMed end users.

The DevSecOps capability developed under this effort will be designed to be compatible with the Joint All- Domains Command & Control concepts supporting the multi-domain operations. The DoD MEDCOP capability will be developed using an agile approach to iteratively develop a minimum viable product. An initial useful capability will be deployed to DoD users quickly to obtain vital end-user feedback as the development team transitions to scaling the capability with increased functionality across an expanding user base. Development will focus on regular and repeated delivery of incremental improvements. The development team will work with DOD stakeholders to identify operational, cybersecurity, and quality assurance requirements. Software testing will be automated to enable critical updates to be deployed in days to weeks as opposed to months or years.

APPENDIX 3: HIGH LEVEL OPERATIONAL MEDICINE CAPABILITIES

Capability Description Minimum Values

Operational Health Care Functions

The ability to identify, capture, organize, disseminate, and synthesize required operational health and medical force information (and associated information from the sustaining base) in support of operational commanders' plans, operations and sustainment activities within their Area of Responsibility/Joint Operational Area

The system allows for bi-directional exchange of information across authorized systems, or store-and- forward capability as appropriate, using current Department standards.

All authorized users are able to access relevant databases and applications from their assigned device.

Medical command and control (MedC2)

The ability to synchronize and integrate health and medical force-related information (in accordance with information releasability guidelines) during planning, preparation, execution (direction, coordination and control of medical assets) and assessment of Combatant Commanders/JFC/SCCs’ plans, operations and sustainment activities.

All Medical Command and Control information is managed within timelines established in support of the command's planning process.

Medical Situational Awareness activities (MEDSA)

The ability to synchronize and integrate medical and medically-related information and computable electronic data gained through surveillance, readiness reporting, and other collection and reporting activities, during the synthesis and analysis of broader data, information and context in order to aid decision- making.

All MedSA information is synchronized and integrated into the command's situational awareness in time to support known decision points and decisions made in response to unforeseen circumstances.

Medical Logistics

(MEDLOG)

The ability to synchronize, integrate and synthesize medical and related information required to organize and provide life-cycle management of medical products and services and to integrate and manage the provision of integrated medical logistics capabilities in support of (ISO) operational medical forces.

All medical logistics information is synchronized and integrated into the command's sustainment activities in accordance with established timelines.

Health Care Delivery

(HCD)

The ability to synchronize and integrate medical and medically-related information required to execute casualty management (treatment of wounded or ill patients in an operational environment) and health care activities (including the agreed upon scope of services available across DOD not limited to primary care, preventative care, dental, veterinary, pain management, behavioral health, acute care, critical care, dental, specialty care, etc.) and to manage provider and facility administration when possible.

Information necessary to facilitate health care delivery is able to be captured, queried and/or discovered when and where required.

Patient Movement

(PM)

The ability to synchronize and integrate medical and medically-related information required to execute activities related to Patient Movement Activities (e.g.

casualty evacuation, medical evacuation, aeromedical evacuation, en-route care, PM planning, medical regulating, patient staging, PMI management, maintaining patient in-transit visibility), and maintenance of the Department’s Global Patient Movement Network.

Information related to platform, treatment node, patient locations, and patient statuses is managed in (near) real time, allowing for seamless integration and coordination of PM activities.

C. Organizational Conflict of Interest

Appendix 3: High Level Operational Medicine Capabilities