Attachment_5_-_Sample_TO_SOO.pdf

Indian Health Service

HEALTH INFORMATION TECHNOLOGY

MODERNIZATION PROGRAM

RFP No. 140D0421R0050 Attachment 5: Sample Task Order

Statement of Objectives (SOO)

Attachment 5: Sample Task Order SOO

IHS Heal th IT Modernizat ion Program 2

1.0 Introduction

The purpose of this Sample Task Order Statement of Objectives (SOO) is to define IHS’s objectives for achieving the Modernized Health IT enterprise build and initial Go- Live at three sample Service Units (A, B, and C). A Service Unit is an administrative entity, whether operated by the IHS or a tribe, with the responsibilities for planning, managing, and evaluating the IHS program serving a defined geographic area less than that for which an Area Office is responsible. A Service Unit consists of a main facility, such as a Hospital or Health Center, and one or more satellite facilities, which may be Health Centers or Health Stations.

Sample Service Unit A includes one Large Hospital, one Small Health Center, one Large Health Center, and two Health Stations.

Sample Service Unit B includes a single Medium Health Center. Service Unit B’s connectivity is currently limited to a single fragmentary 1.544 Mbps (T-1) link with a history of intermittent daily performance where turnaround times on transactions are long, sometimes exceeding transaction turnaround time and may require waiting for the connectivity to return.

In addition, Service Unit B’s personnel skills and numbers require reliance on connectivity for ready consultation on patient conditions.

Sample Service Unit C includes one Small Health Center, one Large Health Center, and four Health Stations.

The Sample Service Units are representative of the larger population of IHS sites;

however, they are notional for the purpose of this Sample Task Order.

Appendix A, Notional Facility Information and Services, details the types and quantities of occupational positions provided at each facility. Additionally, it provides a list of services provided at each type of facility. It also provides the Average Visits Per Year and Number of Hospital Beds for each facility. The Average Visits Per Year represents the number of encounters with Health IT-mediated systems, such as providers, pharmacy, laboratory, etc. These do not only represent episodes of care.

Once eligible for IHS services, patients are free to obtain services from any facility in IHS. Therefore, there is no assigned patient population for each medical facility. The IHS hospitals provide ambulatory and emergency services as a primary focus. Lastly, Appendix A provides a list of Acute (Hospital) and Ambulatory (Health Center, Health Station) services.

Appendix B, Clinical and Business Processes for Sample Service Units, lists which of the IHS Clinical and Business Processes will need to be supported at the sample service units.

IHS Heal th IT Modernizat ion Program 3

For the purposes of this Sample Task Order, assume each site provides the services listed in the associated columns of Sample TO SOO, Appendix A, autonomously without dependence on other sites.

Table 1 – Sample Service Unit Information Hospital Health Center Health

Station Sample Service Unit Large Small Medium Large

Service Unit A (Acute + Ambulatory Multi Site)

1 1 0 1 2

Service Unit B (Ambulatory- Only Single Site)

0 0 1 0 0

Service Unit C (Ambulatory- Only Multi Site)

0 1 0 1 4

2.0 Scope

The scope of this Sample Task Order includes three broad components:

1. Build and configure the modernized enterprise EHR solution, including the hosting environment.

2. Prepare for, achieve, and complete Go-Live, Hypercare, and Post-Go-Live at Sample Service Units A, B, and C.

• Go-Live –system made available for real time operation

• Hypercare- delivers elevated support to ensure seamless adoption of the new system

• Post-Go-Live- assists users in the production environment with training, communication and issue resolution

3. Complete 12 months of Operations & Maintenance support for Service Units A, B, and C

• Keep system viable, operationally efficient, secure and supported on a continuous basis

3.0 Solution Capabilities

The solution shall meet the capabilities described in the IDIQ SOO, Section 5.0, Solution Capabilities.

4.0 Solution Objectives

The solution objectives below are aligned to the IDIQ SOO, Section 6.0, Solution Objectives, and IDIQ SOO Appendices A-F.

4.1 Usability of Solution Capabilities

• Employ the principles of usability as described in the IDIQ SOO, Section 6.1, Usability of Solution Capabilities.

IHS Heal th IT Modernizat ion Program 4

4.2 Planning and Implementation of Solution Capabilities

4.2.1 Enterprise Implementation Planning

• Assessing the organizational readiness of the Sample Service Units A, B, and C to receive and use the Health IT modernization solutions.

• Analyzing the IT infrastructure – network, data centers, etc.– that will need to be present in IHS to optimally support the Health IT solution.

o Providing detailed recommendations for updating, upgrading, modifying that infrastructure to be ready for go‐live.

o Providing reassessment/review of the IHS enterprise infrastructure once IHS has addressed the identified issues.

o Provide a complete Enterprise Build. An Enterprise Build is the system of production scale, reliable, baseline software including system core and all business process listed in the Appendix A of the IDIQ SOO and the capabilities listed in Appendix B of the IDIQ SOO.

4.2.2 Site Implementation Planning and Deployment

• Assessing the site’s organizational readiness to receive and use the Health IT modernization solutions.

• Analyzing the site IT infrastructure – network, data centers, etc. – that will need to be present in IHS to optimally support the Health IT solution.

o Providing detailed recommendations for updating, upgrading, modifying that infrastructure to be ready for go‐live.

o Providing reassessment/review of the site infrastructure once IHS has addressed the identified issues.

• Complete provisioning, installation, configuration, checkout, and testing of all Health IT solutions (i.e., users, providers, credentials, clinics, templates, formularies, local and reference laboratory tests, etc.) to fully meet the needs of the Service Units identified in the Introduction and further described in Appendix A.

4.2.3 Go-Live, Hypercare and Post-Go-Live Support

• Go live requires final site checkout, sign-off by IHS that contractor’s implementation criteria has been met.

• Hypercare is elevated support to ensure seamless adoption of the new system

• Post-Go-Live Support for each installation will be for a period of 90 days until full transition to sustainment.

4.3 Training

• Enable Government and Contractor personnel to maintain and manage the modernized enterprise solution.

o Provide training for IHS‐identified specialists (estimated to be 20 SMEs for the purposes of this SOO) to formally certify IHS-identified specialists on solution systems. This will better enable IHS staff to work with offeror solution engineers in implementing IHS workflows.

IHS Heal th IT Modernizat ion Program 5

4.4 Data Management

• Provide a full range of data conversion, migration, management, analytics, reporting, and archiving capabilities to meet the objectives described in the IDIQ SOO, Section 6.4, Data Management.

4.5 Interoperability

• Provide interoperability with other systems and medical devices, to include the systems identified in the IDIQ SOO, Section 6.5, Interoperability.

4.6 Quality Assurance and Testing Strategy

• Provide a Quality Assurance and Release Management Plan that addresses the objectives described in the IDIQ SOO, Section 6.6, Quality Assurance and Testing Strategy.

4.7 Operations and Support

4.7.1 Enterprise Operations and Support

• Establishing and maintaining an enterprise baseline design and configuration (to include hosting) of the Health IT Modernization solution that meet the following objectives:

o Executing an enterprise domain strategy, structure, and processes for conducting training, testing, configuration and implementation, operations, and disposal.

o Fully configuring and demonstrating the enterprise system before deployment.

• Developing and implementing center operating procedures.

• Provide an enterprise solution that meets the objectives described in the IDIQ

SOO, Section 6.7, Operations and Support.

4.7.2 Site Operations and Maintenance Support

• Operate and sustain the installed baseline solution that meets the objectives described in the IDIQ SOO, Section 6.7, Operations and Support, for 12 months.

4.8 Cybersecurity and Access

• Provide a solution that meets the cybersecurity and access objectives outlined in the Health IT Modernization IDIQ SOO, Section 6.8, Cybersecurity and Access.

4.9 Project Management

• Provide flexible project management procedures and methods that meet the ongoing demands of the IHS Health IT Modernization Program and support the IHS Health IT Modernization Program Management Office.

4.9.1 Capital Planning and Investment Control

• Meet the objectives described in the IDIQ SOO, Section 6.9.1, Capital Planning and Investment Control.

IHS Heal th IT Modernizat ion Program 6

4.9.2 Section 508 Compliance Materials

• Meet the objectives described in the IDIQ SOO, Section 6.9.2, Section 508

Compliance Materials.

4.9.3 Contract Personnel

• Meet the objectives described in the IDIQ SOO, Section 6.9.3, Contract

Personnel.

Attachments

Appendix A: Notional Facility Information and Services Appendix B: Clinical and Business Processes for Sample Service Units