SF30 GDIT HHSN316201200023W 75D30121F10678 00005.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE PAGE OF PAGES

1 53

2. AMENDMENT/MODIFICATION NO.

00005

3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO.

00HCPNEB-2023-71086

5. PROJECT NO. (If applicable)

6. ISSUED BY CODE 8219 7. ADMINISTERED BY (If other than Item 6) CODE 8219 Centers for Disease Control and Prevention

(CDC)

Office of Acquisition Services (OAS) 2900 Woodcock Blvd, MS TCU-4 Atlanta, GA 30341-4004

Centers for Disease Control and Prevention (CDC) Office of Acquisition Services (OAS) 2900 Woodcock Blvd, MS TCU-4 Atlanta, GA 30341-4004

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

GENERAL DYNAMICS INFORMATION TECHNOLOGY, INC.

3150 FAIRVIEW PARK DR STE 100

FALLS CHURCH, VA 22042-4504

X

9A. AMENDMENT OF SOLICITATION NO.

9B. DATED (See Item 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

75D30121F10678

10B. DATED (See Item 13)

CODE SMNWM6HN79X5 FACILITY CODE 03/31/2021

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

No funding changes are associated with this modification.

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN

X B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

X

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

FAR 43.103(a) Bilateral Modification

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, X is required to sign this document and return 1 copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See page 2.

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED

16B. UNITED STATES OF AMERICA

BY ___________________________________________

(Signature of Contracting Officer)

16C. DATE SIGNED

NSN 7540-01-152-8070 STANDARD FORM 30 (REV. 10-83)

PREVIOUS EDITION UNUSABLE 30-105 Prescribed by GSA

FAR (48 CFR) 53.243

ITEM 10A.

Ann E. Bettinger, Contracts Administrator Advisor

March 2, 2023

HHSN316201200023W 75D30121F10678 00005

The purposes of this modification are as follows:

1. To add HHSAR clause 352.232-71 Electronic submission of payment requests (February 2022) and to remove local term CDCA.G001 CDCA_G001 – Invoice Submission (Mar 2021) within Part 4;

2. To update the contractor’s point of contact as shown below;

3. To add the section entitled “Optional Task Line Items” to Part 2;

4. To reduce the total potential value of CLIN 2004 by $363,272.40, from $363,272.40 to $0.00;

5. To reduce the total potential value of CLIN 2006 by $2,361.27, from $2,361.27 to $0.00;

6. To create CLIN 0007, which has a potential value of $190,068.00, and CLIN 0008, which has a potential value of $1,235.44, for Optional Task 9 and the NITAAC fee for Optional Task 9;

7. To create CLIN 0009, which has a potential value of $173,204.40, and CLIN 0010, which has a potential value of $1,125.83, for Optional Task 10 and the NITAAC fee for Optional Task 10;

8. To add Optional Task 11 to Part 3 and to update the Task Order Deliverables and Milestones and Performance Matrix tables accordingly;

9. To create CLIN 0011, which has a potential value of $258,852.50, and CLIN 0012, which has a potential value of $1,682.54, for Optional Task 11 and the NITAAC fee for Optional Task 11;

10. To increase total the total potential value of this task order by $260,535.04, from $5,248,345.99 to $5,508,881.03, and to update the summary of pricing within Part 2 accordingly.

All other terms and conditions remain in full force and effect.

Points of Contact:

Contractor POC: Ann Bettinger Email: ann.bettinger@gdit.com Phone: (860) 448-4417

CSELS (COR) Kimberly Riggle Email: kvh6@cdc.gov Phone: (404) 498-2447

OFR/OAS (CO /CS) Michael Crow Email: wyv2@cdc.gov Phone: (770)488-3208

PART 2 - SUPPLIES OR SERVICES AND PRICES/COSTS

Option Year 2 Items:

ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE

2004 Optional Task - NNDSS Support

PWS Tasks 9, 10

This is an optional line item.

This is a Severable Fixed Price line item.

Period of Performance: 12/01/2022 – 11/30/2023

12 Months $0.00 $0.00

2006 NITAAC Fee (Unfunded):

Option year 2: Unfunded.

NITAAC Fee of .65% for unfunded CLIN 2004.

1 Each $0.00 $0.00

2007 Optional Task - NNDSS Support:

PWS Task 9

This is an optional line item.

This is a Severable Fixed Price line item.

Period of Performance: 12/01/2022 - 11/30/2023

12 Months $15,839.00 $190,068.00

2008 NITAAC Fee (CLIN 2007):

NITAAC Fee of .65% for unfunded CLIN 2007.

1 Each $1,235.44 $1,235.44

2009 Optional Task - NNDSS Support:

PWS Task 10

This is an optional line item.

This is a Severable Fixed Price line item.

Period of Performance: 12/01/2022 - 11/30/2023

12 Months $14,433.70 $173,204.40

2010 NITAAC Fee (CLIN 2009):

NITAAC Fee of .65% for unfunded CLIN 2009.

1 Each $1,125.83 $1,125.83

2011 Optional Task - Data Standardization and Harmonization for NNDSS

PWS Task 11

This is an optional line item.

This is a Severable Fixed Price line item.

Period of Performance: 02/01/2023 - 11/30/2023.

10 Months $25,885.25 $258,852.50

2012 NITAAC Fee (CLIN 2011):

NITAAC Fee of .65% for unfunded CLIN 2011.

1 Each $1,682.54 $1,682.54

Summary of Pricing Base Period (Funded) $ 1,042,660.96 Base Period (Unfunded) $ 240,802.93 Option Year 1 (Funded) $ 1,645,758.35 Option Year 1 (Unfunded) $ 361,035.57 Option Year 2 (Funded) $ 1,592,454.51 Option Year 2 (Unfunded) $ 626,168.71 Total Potential Value $5,508,881.03 Total Obligated Funding $ 4,280,873.82

Optional Task Line Items

The Contracting Officer may exercise the optional tasks within the listed period of performance within each optional CLIN. The optional task line items, CLINs 2007, 2008, 2009, 2010, 2011, and 2012, may be exercised once up to the total extended price listed per CLIN.

The Contracting Officer may exercise the option by written notice to the Contractor within the period of performance of the CLIN associated with the optional line item, as shown in the schedule above. The exact period of performance for each optional task will be established at the time it is exercised and may be for a different period of time than other line items in this task order. The vendor will be notified in writing, by letter or email, at least 15 days before the option is exercised. After that written notification, a funded, unilateral modification will be issued to exercise and fund the option or options. Modification funding will be obligated according to the number of units (months) exercised according to the period of performance established at the time each optional CLIN is exercised.

The Government reserves the right not to exercise any optional task CLINs if no optional tasks are required during the performance of this contract.

Part 3. Performance Work Statement

I. Overview of Work:

The purpose of this project is to support and improve the public health information data flow within the surveillance programs in the Division of Health Informatics and Surveillance (DHIS) which resides within the Center for Surveillance, Epidemiology, and Laboratory Services at the U.S. Centers for Disease Control and Prevention (CDC).

The Contractor will provide defined, subject matter expertise and specific technical support services to the National Notifiable Diseases Surveillance System (NNDSS) program and the National Syndromic Surveillance Program (NSSP). DHIS has identified a broad range of support requirements. These requirements range from assisting, updating, and maintaining our current Public Health Information Network Specification (PHIN Spec) which is our implementation guide (IG) for the NNDSS program; coordinate the development of message mapping guides (MMGs); Health Level 7 (HL7) subject matter expertise supporting the current development of MMGs; identifying and applying vocabulary standards; creating new vocabulary and data dictionaries for public health using current and future IT systems; and applying this knowledge and expertise to current and future-developed systems to better support surveillance Support requirements also include providing Help Desk support for associated PHIN systems and Epi Info™ (https://www.cdc.gov/epiinfo/index.html) and providing program management support services for the NNDSS and NSSP program offices. Additional support requirements may include providing operations and maintenance support (O&M) for two IT systems, PHIN VADS and PHIN DIR. (URLs:

https://www.cdc.gov/phin/tools/phinvads/index.html and https://www.cdc.gov/phin/tools/phindir/index.html), creating new web content and updating existing content for the Epi Info™ website, and providing support to the NNDSS Analytic and Data Quality Support Teams totaling three (3) Optional Tasks.

II. Background and Need:

The Centers for Disease Control and Prevention (CDC), located in Atlanta, Georgia, USA, is an agency of the Department of Health and Human Services (HHS). CDC’s mission is to promote health and quality of life by preventing and controlling disease, injury, and disability. CDC is the Nation’s leading prevention agency for these adverse health events. Within the CDC, the Division of Health Informatics and Surveillance (DHIS) is seeking consultation and technical support to the National Notifiable Diseases Surveillance System (NNDSS) and the National Syndromic Surveillance Program (NSSP).

The following provides specific detailed background information for each unit supported under this contract.

Division of Health Informatics and Surveillance (DHIS) The Division of Health Informatics and Surveillance provides leadership and support to oversee and improve public health information, integrated surveillance systems, and to provision high-quality health data used to monitor, control, and prevent the occurrence and spread of diseases and other adverse health conditions. Tasks identified below shall provide support for activities, projects, and systems in both branches.

1. Surveillance and Data Branch (SDB) The SDB supports the National Notifiable Diseases Surveillance System (NNDSS) program and the National Syndromic Surveillance Program (NSSP) by providing the expertise and processes used to receive national notifiable disease data and syndromic data with the goal of providing more comprehensive, timely, and higher quality data than ever before for public health decision making. This branch is where Message Mapping Guides (MMGs) and our Public Health Information Network (PHIN) Specification (e.g., our Implementation Guide) originate. The MMG brings together the data elements (vocabulary) with the messaging specification (e.g., HL7 2x) for a given disease or group of diseases. MMGs are developed in partnership with the program and jurisdictions.

The Contractor will work as part of a diverse team to update and create new MMGs in our current process using one of the HL7 versions listed above. This branch is also where the Implementation Guide (IG) for the National Syndromic Surveillance Program (NSSP) program originates. The Contractor will work as part of a team to support the piloting of the Draft Standard for Trial Use (DSTU) version of the implementation guide, incorporate those findings to prepare the implementation guide for HL7 balloting, and provide general support around balloting.

2. Information Systems Branch (ISB) The ISB is the “home” of the IT systems and their respective Help Desks that support the surveillance programs, National Notifiable Diseases Surveillance System (NNDSS) program and the National Syndromic Surveillance Program (NSSP). The Contractor will provide expertise and this expertise will be leveraged by using the following systems: Message Mapping Guide Authoring Tool (MMGAT), PHIN Vocabulary Access Distribution System (VADS), PHIN Directory (DIR), and Epi Info™. The Contractor will be asked to work collaboratively at times with staff from MVPS (Message Validation, Processing, and Provisioning System), NBS (NEDSS Base System), and the Accelerator Team (XLR), which all support the NNDSS program as well.

III. Project Objective:

Overall Objectives:

The objectives of this contract are the further enhancement and support of the NNDSS and/or NSSP Program with the support of Subject Matter Experts providing consultation and technical support; furtherance of public health information exchange through the adoption and implementation of standards; and the operations, maintenance, and support of systems used by the public health community. This expertise will help CDC/DHIS meet its objectives in providing more comprehensive, timely, and higher quality data for public health decision making within CDC, as well as the jurisdictions on a local, state and national level.

IV. Period and Place of Performance:

Period of Performance

The Task Order awarded as a result of this RFTOP is anticipated to have the performance period noted below:

Base Period: 04/01/2021 – 11/30/2021 Option Year 1: 12/01/2021 – 11/30/2022 Option Year 2: 12/01/2022 – 11/30/2023

Location and Staff Assignment

Surveillance Systems, VADS, and Help Desk Support Services:

Contractors: Onsite (CDC Space) 0%; Offsite: 100%

Program Management Support Services Team (Tasks 7 and 8): Onsite - (CDC Space): 100% Offsite: When teleworking or during a Continuity of Operations declared emergency

NNDSS Analytic and Data Quality Support Team (Optional Tasks 9 and 10): Onsite - (CDC Space): 0% Offsite: 100%

Accomplishment of the results contained in this PWS requires Surveillance Systems, VADS, DIR, and Help Desk/Epi Info™, and NNDSS Analytic and Data Quality Support Team (Optional Tasks 9 and 10) to be performed at the Contractor’s facilities or at an alternative location such as when on a regular telework schedule or during a Continuity of Operations declared emergency. Exception: Hoteling and touchdown space at CDC in Building 2500 Century Parkway, Atlanta, Georgia will only be provided on an occasional basis for extenuating circumstances/situations. Otherwise, regular meetings among CDC staff and Contractors should be conducted via Skype/Zoom/Microsoft Teams, etc., or if feasible, in person at the Contractor’s on-site conference room.

However, the Contractors working on the Program Management Support Services Team will be assigned a designated workspace in Century Center, Building 2500 on the 3rd Floor. On-site Contractor(s) will be provided with a computer desktop, monitor(s), desk phone and access to network printers. If a Contractor teleworks, laptops and other government-owned equipment will not be provided except for card readers.

Normal workdays are Monday through Friday except US Federal Holidays. Contractors are expected to typically work eight (8) hours per day, 40 hours per week. Flextime workers start no earlier than 0600 and no later than 0900.

CDC core hours of work are from 0900 to 1530. All employees are expected to be available during core hours.

There may be instances that require broader time coverage, depending on the task requirements.

Justification/Rationale for Specific Onsite Contractor Staff

Due to the nature of the Program Management Support Services for NNDSS and/or NSSP as detailed in this PWS, the Contractor will need constant access to and engagement with DHIS management and staff to provide the most effective consultation regarding creation of new strategic planning initiatives, business processes, web development, policy strategies and various communications vehicles including, pamphlets, journals, websites, SharePoint sites, etc. Telework is permitted. If telework is proposed, it shall not exceed 2 days per week.

For the Program Management Support Services Team Only: If regular telework days are observed, those days may need to be adjusted/changed to accommodate any meetings for the Program Office where the Contractor will need to be present onsite for NNDSS and/or NSSP task work such as logistical setup of meeting space, etc.

Alternate Place of Performance – Unforeseen/Emergency Conditions: The Contractor may be required to work at other locations, to include, but not limited to, working from an approved Continuity of Operations (COOP) location designated by the contracting company or working from other designated/alternate work locations as set forth by CDC. When working at any alternate location, the Contractor will prepare all deliverables and other contract documentation utilizing Contractor resources. To the extent possible, the Contractor will provide the same level of support as stated in the PWS when utilizing an alternate work location.

V. Description of Work:

For the purpose of this contract, the Scope of Work includes the following:

Technical and consultation support services to the following systems:

- National Notifiable Diseases Surveillance System (NNDSS)

- National Syndromic Surveillance Program (NSSP)

- Public Health Information Network Vocabulary Access and Distribution System (PHIN

VADS) and Public Health Information Network Directory (PHIN DIR) (Optional Task 6)

- PHIN Help Desk, Epi Info™ Help Desk, o and Help Desk Communications Support (Optional Task on Task 5)

Program management support services for:

- The National Syndromic Surveillance Program (NSSP) program office

- The National Notifiable Diseases Surveillance System (NNDSS) program office

Expertise required in this RFTOP include, but is not limited to the following:

- Vocabularies from Standards Developing Organizations (SDOs)

- HL7

- MMG development

This project will provide ongoing activities necessary to provide leadership and support to oversee and improve public health information, integrated surveillance systems, and to provision high-quality health data used to monitor, control, and prevent the occurrence and spread of diseases and other adverse health conditions. It is the expectation that the Contractor shall perform a broad range of services related to information systems in support of the Division of Health Informatics and Surveillance (DHIS) in the Office of Public Health Scientific Services (OPHSS), Center for Surveillance, Epidemiology, and Laboratory Services (CSELS) and Program Management Support Services to the NNDSS and NSSP program offices.

Performance Management - This Task Order will use performance-based principles wherever possible and prudent.

Individual Tasks will incorporate performance measures wherever possible and appropriate. Earned Value Management may be used where appropriate.

VI. Tasks to be Performed:

Technical Requirements – the Contractor shall execute and implement the following tasks:

Task 1 – Transition-in (Optional):

Task 1.1 - The Transition-In Task facilitates the effective transition from the incumbent Contractor to the awardee of this task order.

Task 1.2 - Successful and full (100%) transition between outgoing and incoming Contractors shall be defined by the incoming Contractor’s ability and capacity to maintain full (95% or better) continuity of operations, high productivity, and exemplary service quality.

Task 1.3 - To minimize level of risk and enhance potential for successful transition, the selected Contractor shall follow the approved Transition Plan submitted as part of their respective proposal. The selected Contractor shall recruit required personnel/skillsets and promptly submit appropriate clearance documentation related to background investigations required for CDC Network access and any other related clearance requirements.

Task 1.4 - In addition to the transition actions in the approved Transition Plan, the Contractor shall perform the following activities during the transition-in period:

1.4.a. Non-Disclosure Agreement (NDA) review, completion and signature 1.4.b. Promptly submit appropriate clearance documentation (http://isp-v-maso-apps/eforms/download.aspx?ID=2065)#) related to background investigations required for CDC Network access.

1.4.c. Review and understand all the technical and process documentation;

1.4.d. Review and understand the existing data and system security policies in place;

1.4.e. Review and understand server and system architecture;

1.4.f. Review and understand the database structure;

1.4.g. Review and understand different data sources and their interrelationships;

1.4.h. Review and understand the data refresh process;

1.4.i. Review and understand the DHIS systems architecture and application code;

1.4.j. Review and understand all DHIS custom web applications;

1.4.k. Review and understand the metadata database, update process, and utilization throughout the system;

1.4.l. Review and understand the Department of Health and Human Services

(HHS) Enterprise Performance Life Cycle (EPLC) Framework for specific tailoring of EPLC project activities and documentation as approved by the Contracting Officer’s Representative (COR). Additional information regarding HHS EPLC framework can be found at:

http://www.hhs.gov/ocio/eplc/index.html CDC Leadership message and priority areas of interest

Task 2– Message Mapping Guide (MMG) Development in support of the National Notifiable Diseases Surveillance System (NNDSS) Program:

The Contractor shall be responsible for providing leadership in the adoption, adaptation, development and conformance of MMGs. This task will exist throughout the entire lifecycle of the contract. As such, the Contractor shall provide an MMG Lead who will perform the following tasks:

2.1 The MMG Lead is responsible for leading the development and/or update of message mapping guides under NNDSS. The Contractor shall:

2.1.a. Guide CDC disease programs in developing and documenting data element requirements for the transmission of HL7 notifications to CDC in the form of message mapping guides.

2.1.b. Work with HL7 analysts and vocabulary specialists to assign appropriate standardized vocabulary and HL7 messaging components to each data element 2.1.c. Collaborate with and assist CDC program staff in developing additional HL7 artifacts such as test scenarios, HL7 test messages, and supplemental implementation guidance documents related to public health monitoring and surveillance for nationally notifiable disease data

2.2 The MMG Lead shall work with the developers of the message mapping guide authoring tool (MMGAT) as a subject matter expert (SME) to document requirements needed for MMGAT and test updates released by the developers

2.3 The MMG Lead shall coordinate the timeline for development of the MMG with various programs

2.4 The MMG Lead shall respond to questions or requests for information related to various aspects of an MMG

2.5 The MMG Lead shall work with the NNDSS change control board to request approval of and implement changes to previously developed MMGs

2.6 The MMG Lead shall coordinate with the DHIS Office of Management and Budget (OMB) coordinator to submit request for OMB approval to collect various data elements

2.7 The MMG Lead shall present MMGs to states via national webinars to solicit comments on guides

2.8 The MMG Lead shall compile and respond to state or jurisdiction questions and comments about the guide, during the piloting of the guide

Task 3 – HL7 Support for the following programs/initiatives:

Task 3.1 – National Notifiable Diseases Surveillance System (NNDSS) and National Syndromic Surveillance Program (NSSP) support. The Contractor shall be responsible for assisting in the adoption, adaptation, development, and conformance of HL7 health messages and messaging standards. This task will exist throughout the entire lifecycle of the contract.

The following tasks are applicable to Task 3.1

For the NNDSS Program the Contractor shall:

a. Prepare HL7 messaging instructions in MMGs for the submission of case notification data from reporting jurisdictions to CDC.

b. Provide technical messaging expertise to projects and systems that utilize interfaced communication protocols, focusing on the HL7 v2X standards.

c. Assess if changes in messaging or data provisioning approach necessitate a revision in the PHIN

Messaging Specification for Case Notification and if so, revise the specification and technical conformance profile. The current version of the specification is available for review at:

https://wwwn.cdc.gov/nndss/document/PHIN_Messaging_Specification_for_Case_Notification_v3%200_ Release_2_20170815.docx

d. Develop HL7 Test Messages based upon information provided in Test Scenarios, in order to help external partners, implement the HL7 v2X Case Notification Messages. Validate accuracy of test messages.

e. Provide technical expertise and advice about best practices in the use of the HL7 standard, as well as conduct ongoing knowledge transfers of HL7, XML analysis, interface specification, design and implementation to project teams.

f. Facilitate communication sessions with other messaging subject matter experts (internal and external representatives) and project support personnel on information about standards setting expectations and on-going national and state standard setting activities. Examples of internal representatives include HL7 messaging experts working at CDC—both internal and external to SDB. Examples of external representatives include HL7 experts at the Association of Public Health Laboratories (this organization is assisting reporting jurisdictions in implementing the HL7 case notification messages), Contractors working on the NEDSS Base System, and technical experts working in state and local health departments who are being asked to implement the HL7 case notification standard.

g. Contribute to the development of messaging standard components such as data definitions, terminology and nomenclature, schemas, and conformance profiles which can be used as a common requirement by information systems sharing information among stakeholders;

h. Assist CDC and other Contractor staff in the process required to analyze, communicate and manage the documentation associated with the development and adoption of electronic health-related messaging.

i. Provide technical expertise to projects and systems that utilize interfaced communication protocols, focusing on the HL7 standards.

j. Provide assistance in the development, testing, and validation of message implementation spreadsheets, test messages and business use cases.

k. Provide support for message validation and troubleshooting during the onboarding process and communicate to stakeholders’ issues, outcomes, and resolutions.

l. The MMG development process uses an agile approach to development and participation in daily 15-minute sprint meetings and in review and planning meetings after each 2-4-week sprint about MMG development is required.

m. Create Standard Operating Procedures (SOP) that describe in detail how HL7 messaging work is performed for MMG development. The SOP should be updated as new decisions are made about how messaging should be applied to the MMGs.

n. Create Best Practices for messaging work applied to MMG development. The best practices should document decisions made about messaging in MMGs, the rationale for the decision, the pros and cons for the decision, and the people who contributed to the decision.

For the NSSP Program, the Contractor shall:

o. Support the piloting of the Draft Standard for Trial Use (DSTU) Message.

Incorporate findings from the piloting of the DSTU message and prepare the message for balloting.

p. Support the balloting of the updated Message.

Task 4 – Vocabulary Support in support of the following programs/initiatives:

Task 4.1 – National Notifiable Diseases Surveillance System (NNDSS) and National Syndromic Surveillance Program (NSSP) support. The Contractor shall provide vocabulary expertise to the NNDSS and NSSP programs, specifically the MMG development and revision process, and updating of the DSTU message for HL7 balloting. The Contractor shall provide expertise in SNOMED, LOINC, ICD, UCUM, HL7 value sets, and other EHR-related standards. This task will exist throughout the entire lifecycle of the contract.

Task 4.2 – Public Health Information Network Vocabulary Access and Distribution System (PHIN VADS) Support. PHIN VADS is used for accessing, searching, and distributing vocabularies used in public health and clinical care practice. The Contractor shall provide vocabulary expertise for the PHIN VADS system, specifically, for customers other than NNDSS and NSSP which include internal CDC programs and external CDC partners. The Contractor shall provide expertise in SNOMED, LOINC, ICD, UCUM, HL7 value sets, and other EHR-related standards. This task will exist throughout the entire lifecycle of the contract.

The following tasks are applicable to all subtasks (4.1-4.2) The Contractor shall:

a. Identify existing medical vocabulary and terminology options (e.g., LOINC, SNOMED, RXNORM) which could be used to support data elements in the Message Mapping Guides and NSSP guides and if none exists to support this need, develop a new vocabulary standard for public health.

b. Develop data dictionaries which provide information regarding how the new vocabulary in the MMGs map to legacy data elements. In addition, map and translate the valid values in the new vocabulary to the valid values in the relevant legacy data elements. The data dictionaries will provide the instructions for how the data can be provisioned across the new and legacy data elements. Validate the information in the data dictionaries with the CDC programs and revise when corrections are needed.

c. Identify or develop vocabulary options for harmonizing similar data elements across national notifiable conditions/diseases and provide advice to SDB and CDC program staff in terms of how best to harmonize and standardize data elements across national notifiable conditions.

d. Interact with internal CDC partners to maintain standardized vocabulary content needed for electronic messages and systems.

e. Map and translate the valid values in the new vocabulary to the valid values in the relevant legacy data elements. The data dictionaries will provide the instructions for how the data can be provisioned across the new and legacy data elements.

f. Maintain and update PHIN VADS with medical vocabulary and terminology data. Identify how data elements which are harmonized across national notifiable conditions should be identified and updated in applications responsible for distributing harmonized and non-harmonized vocabulary.

g. Maintain standardized vocabulary content needed for electronic messages and systems, updating vocabulary and value sets as needed.

h. Identify how data elements which are harmonized across national notifiable conditions should be identified and updated in applications responsible for distributing harmonized and non-harmonized vocabulary.

i. Create Standard Operating Procedures (SOP) that describe in detail how vocabulary work is performed for MMG development. The SOP should include procedures for updating vocabularies and validating content. The SOP should be updated as new decisions are made regarding vocabulary work to support

MMG development.

j. Create Best Practices for vocabulary work applied to MMG development. The best practices should document decisions made about vocabulary, the rationale for the decisions, the pros and cons for the decision, and the people who contributed to the decision.

k. Develop and update standardized vocabulary content needed for electronic messages and systems.

l. Contribute to and provide medical vocabulary and terminology data updates to public health applications used by the NNDSS program.

Task 5 – Help Desk:

The Contractor shall:

1. Support and maintain the phone numbers and mailboxes associated with PHIN systems

2. Maintain a knowledge-based repository using HP Service Center

3. Triage and escalate tickets to the appropriate team or resource through a tiered approach.

a. “Tier 1” support includes intake of supporting mailbox, phone calls, and web form submissions

b. “Tier 2” support includes creation/tracking tickets, triage/escalation, and knowledgebase

c. “Tier 3” support refers to escalation to a developer for reproducing a problem, developing a technical solution (bugs, platform issues), etc.

4. When required, provide extended hours support, such as emergency operations

5. Provide customer support to requests for service and inquiries

a. For Epi Info™ Support:

b. Epi Info™ (https://www.cdc.gov/epiinfo/) is the primary portfolio of applications supported and in-depth knowledge and understanding is needed.

c. ERHMS (Emergency Responder Health Monitoring and Surveillance™ at https://www.cdc.gov/niosh/erhms/) is also supported.

d. CDC EOC (Emergency Operations Center) requires 24/7 support during a “surge” response to an emergency.

e. Epi Info™ Help Desk currently has three (3) dedicated human resources: Two (2) Contractors and one (1) FTE (Government staff).

f. For incident logging and tracking, JIRA software, a commercial tool by Atlassian

(https://www.atlassian.com/software/jira) is used.

g. Staff provides Tier 3 support for Epi Info™, especially on different mobile devices.

h. Epi-Info’s Help Desk Email Box (epiinfo@cdc.gov) automatically redirects users to the JIRA tool hosted by Atlassian. The Help Desk page on the Epi Info™ website https://www.cdc.gov/epiinfo/support/Help Desk.html also links to the Questions for Confluence user forum: “https://epiinfo.atlassian.net/wiki/questions”

i. Epi Info™ 7 is based on a .Net configuration.

j. Provide communication services to contribute to the mandatory annual review of the Epi Info™

Website by using the CDC’s current web content management system and to create and develop new content, as required.

k. Maintain customer relationships.

l. Maintain technical data reports.

Task 5.1 – Help Desk Communications Support (Optional Task):

The contractor shall provide additional communications support in relation to Epi Info™

Following CDC style guides and plain language guidelines (www.plainlanguage.gov), create new content and update existing content on the Epi Info™ website, online User Guide, and update tutorials to match the latest version of Epi Info™. The current Epi Info™ website can be found at www.cdc.gov/epiinfo. The Epi Info™ Help Desk team or others on the Epi Info™ Development team can provide guidance and demonstrations on how to use each of these tools and their specific features, as needed.

1. Working with the CDC Epi Info™ Team to prioritize the most important focus areas, and using the updated content inventory, update existing web page content including descriptions, step-by-step instructions, and images so that the pages will better describe the current version of the Epi Info™ tools that are available for use.

2. For the tools, features, and functions that are either undocumented, or incompletely documented, create new, or update existing content. For the purpose of this task, the term “content” shall include descriptions, step-by-step instructions, images, captions, annotations, and Image Alt Text for Section 508 accessibility compliance.

3. Create a Content Change Log document in Word format for each main website section, User Guide chapter, Epi Info™ tool, and Epi Info™ tutorial -- at least 32 discreet logs total.

a. Indicate the name of the web page for which the content is written and the section where the text should appear.

b. Record the path and file name of the image, its caption and Alt-Text to the Content Change Log document as a placeholder to show where the image should appear.

c. Save images as a separate file to a common network location specified by the COR.

4. Images or screenshots of Epi Info™ software and features should be taken using a tool such as SnagIt to capture and annotate the image being described.

a. Images may need annotations in order to emphasize the detail being described in the text.

b. Save the image in the PNG format with a file name that matches the naming convention used through the rest of the website.

5. Create content for additional features that are under documented and need to be described which include:

a. Epi Info™ Survey Manager

b. Epi Info™ Web Survey Data Viewer

c. Epi Info™ Web Survey Admin Client

d. Epi Info™ Cloud Data Capture

e. Epi Info™ iOS App

6. Update content for tutorials currently written for the out-of-date Epi Info™ 3.5.4 version so they represent the latest version of Epi Info™ 7.2.4.

a. Original versions of these tutorials can be found at https://www.cdc.gov/epiinfo/support/tutorials.html.

b. Prepare content to be added to new web pages as done in sub-tasks 5 and 6 above.

c. Tutorials to be updated to Epi Info™ 7 version are:

i. Community Health Assessment tutorial and

ii. Cholera Outbreak in Rwenshama tutorial.

7. Review existing web pages for completeness and accuracy and update the Epi Info™ Content Inventory to indicate the web pages that need updates. All of the pages listed in the inventory shall be reviewed alongside the Epi Info™ tools in order to identify areas to be updated. The inventory from the previous year may be used as a guide, but additional changes to the software may have been introduced since the inventory was last reviewed.

Task 6 – Operations and Maintenance (O&M) of PHIN VADS and PHIN DIR (Optional Task):

1. The Contractor shall maintain and support the current technical architecture of PHIN VADS and PHIN

DIR.

2. The Contractor shall understand the methodology for publication of content through the Universal Authoring Framework (UAF).

3. Provide communications support to the vocabulary community and maintain all webpages and services.

4. Create monthly usage records using Adobe Analytics.

5. Manage the RESTful API that uses Open Data Protocol (OData) standards.

6. Sustain the Object Identifier (OID) registry.

7. Develop a process for the insertion of bulk OID requests into the database.

8. Engage the public health community to plan the future of vocabulary services to define the target architecture and requirements to evolve vocabulary management capabilities.

9. Maintain the internal and external web pages for PHIN VADS and PHIN DIR.

10. Develop and refine the content for https://phinvads.cdc.gov/vads/SearchVocab.action

11. Understand and apply CDC web content management concepts to all PHIN web pages.

12. Consult on communications for public health partners for electronic public health information exchange, vocabulary, and technical inquiries.

13. Ensure compliance with the EPLC for CDC project management principles and CDC Enterprise

Architecture (EA) as communicated by CDC project team throughout the life cycle of the contract.

The contractor shall deliver all required project artifacts as per the EPLC and EA framework as requested by the CDC project management team.

14. Plan and execute security patches and address system issues/defects when identified and ensure they are well tested and approved by CDC before releasing into production environment.

15. The contractor shall document system requirements, specifications, technical architecture, test plan and results, release notes, and technical support processes.

Task 7 –Program Management and Project Management Support Services – NSSP:

This task includes coordination and logistics support for various program-related activities. Principal tasks include:

Coordinate and support the day to day operations and planning requirements of the NSSP program as staff collaborate with a broad range of stakeholders on public health syndromic surveillance. This support includes:

a. Coordination of assigned project components, tracking progress and ensuring follow-up

b. Meeting coordination (planning, engaging presenters, set-up, execution, notes)

c. Document review and analysis, including policy documents and web content

d. Support for strategic planning and decision making, including analysis of needs and opportunities, documenting plans, tracking execution and reporting on progress

e. Guiding the development of operational plans and measurable outcomes

f. Support for coordination of stakeholder engagements and follow up

g. Managing databases used for collaboration and knowledge management

Task 8 –Program Management and Project Management Support Services – NNDSS:

This task includes coordination and logistics support for various program-related activities. Principal tasks include:

Coordinate and support the day to day operations and planning requirements of the NNDSS program as staff collaborate with a broad range of stakeholders on public health case-based surveillance. This support includes:

a. Coordination of assigned project components, tracking progress and ensuring follow-up

b. Meeting coordination (planning, engaging presenters, set-up, execution, notes)

c. Document review and analysis, including policy documents and web content

d. Support for strategic planning and decision making, including analysis of needs and opportunities, documenting plans, tracking execution and reporting on progress

e. Guiding the development of operational plans and measurable outcomes

f. Support for coordination of stakeholder engagements and follow up

g. Managing databases used for collaboration and knowledge management

Task 9 - NNDSS Data Quality (Optional Task):

1. The Contractor shall provide Data Quality Support as follows:

a. Review and ensure the quality of data transmission for all reporting jurisdictions, diseases, and specified years. The Contractor shall notify NNDSS program staff of data issues or anomalies discovered, and at the direction of NNDSS program staff shall investigate and propose resolutions adhering to CDC standard operating procedures for contacting and communicating with CDC programs or state/local health departments.

b. At the direction of CDC, the Contractor shall develop, maintain, produce, and disseminate automated data quality assessment and data processing reports based on CDC requirements. Based upon NNDSS program requirements, the Contractor shall develop automated, user-customized data quality reports that describe data timeliness, completeness, and validity for any data source, diseases/conditions, and years allowing for the investigation of data anomalies as needed as well as information about the status and results of data processing.

c. The Contractor shall utilize software/development tools approved by CDC for the purpose of developing data quality reports, databases, and dashboards. The software/development tools may include SQL, SQL Server Analysis Services, HTML, JAVA, R, SAS statistical software, Microsoft Visual Studio, Microsoft BI and/or other products approved by CDC for utilization on the MVPS platform-hosted servers. The Contractor shall prepare written documentation and training materials needed by users to guide them in understanding the results of data quality for the reports, databases, and dashboards.

d. Data Quality reports (automated and user-customized) shall be delivered according to Schedule. Upon delivery, results will be reviewed for acceptance and approval by the CDC COR.

Task 10 –NNDSS Analytic Support (Optional Task):

a. The Contractor shall provide NNDSS Analytic support in conjunction with CDC staff. The Contractor shall analyze or interpret NNDSS data utilizing SAS, R-Studio and/or other CDC-approved software, and may be required to use external information sources, such as public health event reports, for interpretation of analytical results. Topics for analysis, whether ad hoc investigations or analyses to be included in standard reports, shall be authorized by CDC and dissemination of results shall meet NNDSS criteria for publication or presentation (including obtaining formal clearance as necessary).

b. The Contractor shall provide enhanced analytic support and report generation to support CDC needs utilizing CDC-provided reporting formats or templates for significant public health events (such as those declared public health emergencies like the COVID-19 response). Events targeted for enhanced support will be approved by the CDC. Enhanced analytic activity may be conducted in close collaboration with DHIS, CDC program, or jurisdictional partner staff, and reports may be required as frequently as daily, and may require performance on weekends or federal holidays.

c. The Contractor shall develop knowledge, generate documents, and provide technical assistance in the utilization of NNDSS applications and services hosted by CDC and its funded partners. The Contractor shall define, implement, and/or utilize content-specific reports that monitor data feed performance, data quality issues, end-user utilization characteristics, and data processing functions to assess impact upon interpretation of case-based surveillance analytic results and system use by end users. This End-user Utilization Report shall be required on a monthly basis.

d. The Contractor shall aid in the provisioning of NNDSS data for CDC program-specific analytic use. The Contractor shall provide coding and/or programs/analytic tools to customize the development of analytic datasets based on specified needs.

Task 11 – Data Standardization and Harmonization for NNDSS (Optional Task):

The Contractor shall provide support and subject matter expertise to identify data concepts for adoption across all NNDSS conditions. Upon identification these concepts, they are to be adapted into an MMG and other applicable formats in conformance with applicable standards. Under this optional task, the contractor shall:

a. Coordinate across internal and external partners to determine data element concepts and vocabulary standards for data common to public health case investigations;

b. Collaborate with vocabulary specialists to assign appropriate standard vocabulary to the data elements and to assess alignment with other data standardizing organizations;

c. Guide the development of transmitting HL7 data to CDC in the form of a message mapping guide and potentially other formats as determined by the Agency to include any additional artifacts such as test scenarios, test messages, supplementary guidance, and other documents needed to support public health surveillance and data monitoring;

d. Work with NNDSS change control board, DHIS Officer of Management and Budget (OMB) coordinator, and other offices or partners ensuring the identified data concepts can be received by

CDC;

e. Present the work to CDC personnel to solicit input throughout the identification of the data concepts and execution;

f. Compile feedback, respond to inquiries, provide recommendations, and document all decisions related to defining the data concepts and building into an MMG or other formats;

g. Provide expertise to NNDSS, specifically for harmonizing data across MMGs and other data formats used for case notifications. Expertise in SNOMED, LOINC, ICD, UCUM, HL7 value sets, and other EHR-related standard shall be provided.

VII. Government Furnished Materials, Facilities and Property

The Government will provide standard office space, office equipment, and software/hardware to the Contractor employees working onsite at CDC. The Contractor staff must comply with all Federal rules and regulations regarding the use of government equipment. Depending on the assignment and at the Government’s sole discretion, a Contractor staff member may be allowed to work offsite if access to confidential data is not required. The CDC will only provide desktop computers, network accessible printers, and desk phones to the Contractor employees working onsite. For Contractor employees working offsite, the CDC will not provide Government Funded Equipment (GFE), except when necessary for access to the CDC network via VPN, and Leased Line, in very limited cases. For access via CITGO, the CDC will only provide Portable Smart Card Readers for those with smart cards.

Key Fobs are no longer issued to Contractors. It will be the responsibility of the Contractor to supply the needed hardware, software, laptop and other materials for their staff to work offsite, during normal times and during emergencies.

To the extent applicable, this Task Order hereby incorporates by reference the updated version of FAR 52.245-1 Government Property (Apr 2012)

VIII. Task Order Deliverables and Milestones

Contract Deliverables. Unless the Contracting Officer or COR otherwise directs, all Contract Deliverables shall be in written form (i) delivered electronically to the COR and such other parties as the COR may designate to the Offeror in writing; and (ii) be formatted in Microsoft Word, Excel or other editable formatting approved by the COR. All deliverables in this Contract must be prepared in consideration of CSELS security, confidentiality, and architecture compliance requirements.