STATEMENT OF WORK.doc

Environmental Public Health Tracking Program Statement of Work Title: Promotion of Interoperable Public Health Data through Application of Standards and Best Practices for Data Collection, Analysis, Use and Dissemination Section 1. Background and Need Environmental public health tracking is a type of surveillance. Surveillance is a method to monitor trends by collecting, interpreting, and reporting data. CDC's Environmental Public Health Tracking Network (Tracking Network) brings together health and environment data in one place, making it easier to compare hazards and exposures with health outcomes at a local and national level. The goal of the Tracking Network is to provide information to help improve where we live, work, and play.

The Tracking Network is part of CDC's National Environmental Public Health Tracking Program. The Tracking Program includes not only the Tracking Network but the people, resources, and program management involved in building this network. Tracking funds 33 state and local health departments to continue building public health capacity and expertise in environmental health surveillance and to modernize data systems to empower public health practitioners, healthcare providers, community members, policy members, and others to make information-driven decisions that affect their health. The Tracking program receives data directly from these recipients.

The Tracking Network is unique in that it provides the United States with accurate and timely standardized data and supports ongoing efforts within the public health and environmental sectors to improve data collection, accessibility, and dissemination as well as analytic and response capacity. Data that were previously collected for different purposes and stored in separate systems are now available in a nationally standardized format, allowing programs to begin bridging the gap between health and the environment. Having accurate and timely tracking data enables public health authorities to determine temporal and spatial trends in disease and potential environmental exposures, identify populations most affected, and develop and assess the environmental public health policies and interventions aimed at reducing or eliminating diseases associated with environmental factors. The availability of these types of data in a standardized network provide researchers, public health authorities, healthcare practitioners, and the public to have a better understanding about the possible associations between the environment and adverse health effects, and to assist them with decision making.

Some data goals of the Tracking Network include improving the quality and timeliness of data received, increasing the amount of data, and having more geographically refined data to facilitate local-level interventions.

Section 2. Project Objective This contract will help address the above-mentioned data goals by assisting in the promotion of interoperable public health data through the application of standards and best practices for data collection, analysis, and dissemination by state and local health departments who are funded by CDC’s Tracking Program (recipients). The standards and guidance will also make critical data available to recipients, thus avoiding a complex layer of individual data requests, duplications, and redundancy.

This contract builds on the efforts from CDC-RFA-EH18-1802 to facilitate data sharing between states, improve data timeliness, and assist with the development of standards and guidance for data collection, analysis, and dissemination.

Section 3. Scope of Work The contractor will work with the Tracking Program to identify and refine Tracking data requirements; identify and evaluate new data sources and summarize their characteristics and potential to meet Tracking’s data requirements; work with recipients to develop use cases for the new data sources as well as for existing sub-county data; and help recipients select and pilot a new data source/s and summarize findings and lessons learned from the pilot.

Section 4. Tasks to be Performed Task 1: Surveillance

· Identify and refine Tracking Program’s data needs

· Evaluate new data sources (e.g., all—payer claims database, Electronic Surveillance System for Early Notification of Community-based Epidemic – ESSENCE etc.) to allow for access to more timely, local, complete data

· Develop use cases for these new data (e.g., additional sub-county data; more timely data; more complete data etc.)

· Help recipients pilot new data sources and standards (e.g., HL7/FHIR) to support use-cases

· Develop use case for sub-county and work with recipients to allow more to submit finer spatial resolution data to the Tracking Program (i.e., hospitalization and emergency department (ED) discharge data)

· Support data sharing between states

· Improve data sharing and data timeliness between states and the Tracking program

Task 2: Collaboration

· Participate in Tracking content Work groups

· Provide technical assistance to interested recipients to submit hospitalization and ED data to CDC

· Collaborate with Tracking partners on data exchange activities

· Provide other technical assistance to Tracking recipients on hospitalization and ED data (e.g., ICD-9 to ICD-10 conversion) Task 3: Outreach/Communications

· Conduct outreach and increase awareness about Tracking-related activities among memberships and partners

Task 4: Program Evaluation/Performance Measurement

· Monitor the impact and performance of program activities Section 5 - Government Furnished Materials

This contract will not utilize any government furnished property.

Section 6 - Period of Performance

The period of performance for this contract is from 9/1/2023 to 8/31/2026.

Section 7 - Place of Performance

Performance of activities will take place at the contractor’s facility.

Section 8 - Reporting Schedule:

The contractor shall provide monthly progress reports, including both a narrative and financial summary, on all activities no later than 15 days after the end of each month. Costs shall be attributed to the major task areas. Invoices for all activities shall be submitted no later than 30 days after the end of the month for which the expenses have been incurred. Expenses shall be identified by each major task, clearly attributed to each task/subtask when multiple activities are being conducted and/or billed simultaneously.

The contractor and CDC shall communicate via monthly telephone conference calls to discuss progress on this project

CDC and the contractor shall hold face to face meetings as needed.

Section 9 – Deliverables Schedule:

The contractor will meet the following project timelines (approximate and open to negotiation based on award date):

Task 1:

Within 2 weeks of award

Within 30 days of the effective date of this contract

August 31, 2024 And Annually

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Task 2:

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Task 3:

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Task 4:

Monthly throughout the contract period of performance

Monthly throughout the contract period of performance

Section 10 - Travel

Travel may be necessary by contract staff to attend annual conferences and workshops conducted by the Tracking Program in alignment with the associated budget and deliverables.

All travel shall be in accordance with the Federal Travel Regulations (FTR) and the Joint Travel Regulations (JTR) and adhere to FAR 31.205-46. The contractor shall ensure that the required travel costs will not exceed the amount authorized in this task order. Required travel must be submitted to COR in an official request with anticipated expenses and justification.

All travel must be authorized by the COR and be in compliance with the task order and all other applicable requirements. The contractor shall use only the minimum number of travelers and rental cars needed to accomplish the trip purpose. Travel shall be scheduled during normal duty hours whenever possible. Airfare will be reimbursed for actual common carrier fares which are obtained by the most reasonable and economical means.

The contractor shall provide a Trip Report for each trip associated with a travel approval. The contractor shall maintain a summary to be included in the monthly report of all approved travel, to include at a minimum, the name of the traveler, location of travel, duration of trip, total cost of trip Section 11 - Special Considerations

HHSAR Provision, 352.239-74: Electronic and Information Technology Accessibility Notice

(a) Pursuant to Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998, all electronic and information technology (EIT) supplies and services developed, acquired, or maintained under this contract or order must comply with the "Architectural and Transportation Barriers Compliance Board Electronic and Information Technology (EIT) Accessibility Standards" set forth by the Architectural and Transportation Barriers Compliance Board (also referred to as the "Access Board") in 36 CFR part 1194. Information about Section 508 is available at http://www.hhs.gov/web/508. The complete text of Section 508 Final Provisions can be accessed at http://www.access-board.gov/sec508/standards.htm.

(b) The Section 508 accessibility standards applicable to this contract or order are identified in the Statement of Work or Specification or Performance Work Statement. The contractor must provide any necessary updates to the submitted HHS Product Assessment Template(s) at the end of each contract or order exceeding the simplified acquisition threshold (see FAR 2.101) when the contract or order duration is one year or less. If it is determined by the Government that EIT supplies and services provided by the Contractor do not conform to the described accessibility standards in the contract, remediation of the supplies or services to the level of conformance specified in the contract will be the responsibility of the Contractor at its own expense.

(c) The Section 508 accessibility standards applicable to this contract are: 36 CFR part 1194.

205 WCAG 2.0 Level A & AA Success Criteria

302 Functional Performance Criteria

502 Inoperability with Assistive Technology

503 Applications

504 Authoring Tools

602 Support Documentation

603 Support Services

(d) In the event of a modification(s) to this contract or order, which adds new EIT supplies or services or revises the type of, or specifications for, supplies or services, the Contracting Officer may require that the contractor submit a completed HHS Section 508 Product Assessment Template and any other additional information necessary to assist the Government in determining that the EIT supplies or services conform to Section 508 accessibility standards. Instructions for documenting accessibility via the HHS Section 508 Product Assessment Template may be found under Section 508 policy on the HHS Web site: (http://hhs.gov/web/508). If it is determined by the Government that EIT supplies and services provided by the Contractor do not conform to the described accessibility standards in the contract, remediation of the supplies or services to the level of conformance specified in the contract will be the responsibility of the Contractor at its own expense.

(e) If this is an Indefinite Delivery contract, a Blanket Purchase Agreement or a Basic Ordering Agreement, the task/delivery order requests that include EIT supplies or services will define the specifications and accessibility standards for the order. In those cases, the Contractor may be required to provide a completed HHS Section 508 Product Assessment Template and any other additional information necessary to assist the Government in determining that the EIT supplies or services conform to Section 508 accessibility standards. Instructions for documenting accessibility via the HHS Section 508 Product Assessment Template may be found at http://hhs.gov/web/508. If it is determined by the Government that EIT supplies and services provided by the Contractor do not conform to the described accessibility standards in the provided documentation, remediation of the supplies or services to the level of conformance specified in the contract will be the responsibility of the Contractor at its own expense.

SOCIAL MEDIA AND OTHER THIRD-PARTY WEBSITE USAGE

Use of any and all third-party2 / social media3 sites must be approved in advance, and comply with HHS and CDC policies, procedures and best practices (including security and privacy) such as those found at: http://www.hhs.gov/web/socialmedia/ and http://www.cdc.gov/SocialMedia/Tools/guidelines/. Contractor will submit necessary documentation, in cooperation with the Project Officer, to obtain approval through designated CDC Social Media governance, as well as Information Security and Privacy Officers.

RECORDS RETENTION

All data created during the course of this contract must be retained, stored and disposed of in accordance with the appropriate CDC Records Control Schedule.

DATA RIGHTS

The Government has unlimited rights to all documents/material or other products produced under this contract. All documents, materials or other products, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights Baseline Security Requirements

1) Applicability. The requirements herein apply whether the entire contract or order (hereafter “contract”), or portion thereof, includes either or both of the following:

a. Access (Physical or Logical) to Government Information: A Contractor (and/or any subcontractor) employee will have or will be given the ability to have, routine physical (entry) or logical (electronic) access to government information.

b. Operate a Federal System Containing Information: A Contractor (and/or any subcontractor) employee will operate a federal system and information technology containing data that supports the HHS mission. In addition to the Federal Acquisition Regulation (FAR) Subpart 2.1 definition of “information technology” (IT), the term as used in this section includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), and related resources.

2) Safeguarding Information and Information Systems. In accordance with the Federal Information Processing Standards Publication (FIPS)199, Standards for Security Categorization of Federal Information and Information Systems, the Contractor (and/or any subcontractor) shall:

a. Protect government information and information systems in order to ensure:

· Confidentiality, which means preserving authorized restrictions on access and disclosure, based on the security terms found in this contract, including means for protecting personal privacy and proprietary information;

· Integrity, which means guarding against improper information modification or destruction, and ensuring information non-repudiation and authenticity; and

· Availability, which means ensuring timely and reliable access to and use of information.

b. Provide security for any Contractor systems, and information contained therein, connected to an HHS network or operated by the Contractor on behalf of HHS regardless of location. In addition, if new or unanticipated threats or hazards are discovered by either the agency or contractor, or if existing safeguards have ceased to function, the discoverer shall immediately, within one (1) hour or less, bring the situation to the attention of the other party.

c. Adopt and implement the policies, procedures, controls, and standards required by the HHS Information Security Program to ensure the confidentiality, integrity, and availability of government information and government information systems for which the Contractor is responsible under this contract or to which the Contractor may otherwise have access under this contract. Obtain the HHS Information Security Program security requirements, outlined in the HHS Information Security and Privacy Policy (IS2P), by contacting the CO/COR or emailing fisma@hhs.gov.

d. Comply with the Privacy Act requirements and tailor FAR clauses as needed.

3) Information Security Categorization. In accordance with FIPS 199 and National Institute of Standards and Technology (NIST) Special Publication (SP) 800-60, Volume II: Appendices to Guide for Mapping Types of Information and Information Systems to Security Categories, Appendix C, and based on information provided by the ISSO, CISO, or other security representative, the risk level for each Security Objective and the Overall Risk Level, which is the highest watermark of the three factors (Confidentiality, Integrity, and Availability) of the information or information system are the following:

Confidentiality:

[x ] Low [ ] Moderate [ ] High

Integrity:

Availability:

Overall Risk Level:

[ x] Low [ ] Moderate [ ] High

Based on information provided by the ISSO, Privacy Office, system/data owner, or other security or privacy representative, it has been determined that this solicitation/contract involves:

[ x ] No PII [ ] Yes PII

4) Personally Identifiable Information (PII). Per the Office of Management and Budget (OMB) Circular A-130, “PII is information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual.” Examples of PII include, but are not limited to the following: social security number, date and place of birth, mother‘s maiden name, biometric records, etc.

PII Confidentiality Impact Level has been determined to be: [ x] Low [ ] Moderate [ ] High

5) Controlled Unclassified Information (CUI). CUI is defined as “information that laws, regulations, or Government-wide policies require to have safeguarding or dissemination controls, excluding classified information.” The Contractor (and/or any subcontractor) must comply with Executive Order 13556, Controlled Unclassified Information, (implemented at 32 CFR, part 2002) when handling CUI. 32 C.F.R. 2002.4(aa) As implemented the term “handling” refers to “…any use of CUI, including but not limited to marking, safeguarding, transporting, disseminating, re-using, and disposing of the information.” 81 Fed. Reg. 63323. All sensitive information that has been identified as CUI by a regulation or statute, handled by this solicitation/contract, shall be:

a. marked appropriately;

b. disclosed to authorized personnel on a Need-To-Know basis;

c. protected in accordance with NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations applicable baseline if handled by a Contractor system operated on behalf of the agency, or NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations if handled by internal Contractor system; and

d. returned to HHS control, destroyed when no longer needed, or held until otherwise directed. Destruction of information and/or data shall be accomplished in accordance with NIST SP 800-88, Guidelines for Media Sanitization.

6) Protection of Sensitive Information. For security purposes, information is or may be sensitive because it requires security to protect its confidentiality, integrity, and/or availability. The Contractor (and/or any subcontractor) shall protect all government information that is or may be sensitive in accordance with OMB Memorandum M-06-16, Protection of Sensitive Agency Information by securing it with a FIPS 140-2 validated solution.

7) Confidentiality and Nondisclosure of Information. Any information provided to the contractor (and/or any subcontractor) by HHS or collected by the contractor on behalf of HHS shall be used only for the purpose of carrying out the provisions of this contract and shall not be disclosed or made known in any manner to any persons except as may be necessary in the performance of the contract. The Contractor assumes responsibility for protection of the confidentiality of Government records and shall ensure that all work performed by its employees and subcontractors shall be under the supervision of the Contractor. Each Contractor employee or any of its subcontractors to whom any HHS records may be made available or disclosed shall be notified in writing by the Contractor that information disclosed to such employee or subcontractor can be used only for that purpose and to the extent authorized herein.

The confidentiality, integrity, and availability of such information shall be protected in accordance with HHS and [CDC] policies. Unauthorized disclosure of information will be subject to the HHS/[CDC] sanction policies and/or governed by the following laws and regulations:

a. 18 U.S.C. 641 (Criminal Code: Public Money, Property or Records);

b. 18 U.S.C. 1905 (Criminal Code: Disclosure of Confidential Information); and

c. 44 U.S.C. Chapter 35, Subchapter I (Paperwork Reduction Act).

8) Internet Protocol Version 6 (IPv6). All procurements using Internet Protocol shall comply with OMB Memorandum M-05-22, Transition Planning for Internet Protocol Version 6 (IPv6).

9) Government Websites. All new and existing public-facing government websites must be securely configured with Hypertext Transfer Protocol Secure (HTTPS) using the most recent version of Transport Layer Security (TLS). In addition, HTTPS shall enable HTTP Strict Transport Security (HSTS) to instruct compliant browsers to assume HTTPS at all times to reduce the number of insecure redirects and protect against attacks that attempt to downgrade connections to plain HTTP. For internal-facing websites, the HTTPS is not required, but it is highly recommended.

10) Contract Documentation. The Contractor shall use provided templates, policies, forms and other agency documents to comply with contract deliverables as appropriate.

11) Standard for Encryption. The Contractor (and/or any subcontractor) shall:

a. Comply with the HHS Standard for Encryption of Computing Devices and Information to prevent unauthorized access to government information.

b. Encrypt all sensitive federal data and information (i.e., PII, protected health information [PHI], proprietary information, etc.) in transit (i.e., email, network connections, etc.) and at rest (i.e., servers, storage devices, mobile devices, backup media, etc.) with FIPS 140-2 validated encryption solution.

c. Secure all devices (i.e.: desktops, laptops, mobile devices, etc.) that store and process government information and ensure devices meet HHS and CDC-specific encryption standard requirements. Maintain a complete and current inventory of all laptop computers, desktop computers, and other mobile devices and portable media that store or process sensitive government information (including PII).

d. Verify that the encryption solutions in use have been validated under the Cryptographic Module Validation Program to confirm compliance with FIPS 140-2. The Contractor shall provide a written copy of the validation documentation to the COR.

e. Use the Key Management system on the HHS personal identification verification (PIV) card or establish and use a key recovery mechanism to ensure the ability for authorized personnel to encrypt/decrypt information and recover encryption keys. Encryption keys shall be provided to CDC Office of Chief Information Security Officer (OCISO).

12) Contractor Non-Disclosure Agreement (NDA). Each Contractor (and/or any subcontractor) employee having access to non-public government information under this contract shall complete the CDC non-disclosure agreement, as applicable. A copy of each signed and witnessed NDA shall be submitted to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition.

13) Privacy Threshold Analysis (PTA)/Privacy Impact Assessment (PIA) – The Contractor shall assist the CDC Senior Official for Privacy (SOP) or designee with conducting a PTA for the information system and/or information handled under this contract in accordance with HHS policy and OMB M-03-22, Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002.

a. The Contractor shall assist the CDC SOP or designee in reviewing the PIA at least every three years throughout the system development lifecycle (SDLC)/information lifecycle, or when determined by the CDC SOP that a review is required based on a major change to the system (e.g., new uses of information collected, changes to the way information is shared or disclosed and for what purpose, or when new types of PII are collected that could introduce new or increased privacy risks), whichever comes first.

A. Training

1) Mandatory Training for All Contractor Staff. All Contractor (and/or any subcontractor) employees assigned to work on this contract shall complete the applicable HHS/CDC Contractor Information Security Awareness, Privacy, and Records Management training (provided upon contract award) before performing any work under this contract. Thereafter, the employees shall complete CDC Security Awareness Training (SAT), Privacy, and Records Management training at least annually, during the life of this contract. All provided training shall be compliant with HHS training policies.

2) Role-based Training. All Contractor (and/or any subcontractor) employees with significant security responsibilities (as determined by the program manager) must complete role-based training (RBT) within 60 days of assuming their new responsibilities. Thereafter, they shall complete RBT at least annually in accordance with HHS policy and the HHS Role-Based Training (RBT) of Personnel with Significant Security Responsibilities Memorandum.

All HHS employees and contractors with SSR who have not completed the required training within the mandated timeframes shall have their user accounts disabled until they have met their RBT requirement.

Training Records. The Contractor (and/or any subcontractor) shall maintain training records for all its employees working under this contract in accordance with HHS policy. A copy of the training records shall be provided to the CO and/or COR within 30 days after contract award and annually thereafter or upon request.

B. Rules of Behavior

1) The Contractor (and/or any subcontractor) shall ensure that all employees performing on the contract comply with the HHS Information Technology General Rules of Behavior.

2) All Contractor employees performing on the contract must read and adhere to the Rules of Behavior before accessing Department data or other information, systems, and/or networks that store/process government information, initially at the beginning of the contract and at least annually thereafter, which may be done as part of annual CDC Security Awareness Training. If the training is provided by the contractor, the signed ROB must be provided as a separate deliverable to the CO and/or COR per defined timelines above.

C. Incident Response

FISMA defines an incident as “an occurrence that (1) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (2) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines incidents as events involving cybersecurity and privacy threats, such as viruses, malicious user activity, loss of, unauthorized disclosure or destruction of data, and so on.

A privacy breach is a type of incident and is defined by Federal Information Security Modernization Act (FISMA) as the loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where (1) a person other than an authorized user accesses or potentially accesses personally identifiable information or (2) an authorized user accesses or potentially accesses personally identifiable information for an other than authorized purpose.

OMB Memorandum M-17-12, “Preparing for and Responding to a Breach of Personally Identifiable Information” (03 January 2017) states:

Definition of an Incident:

An occurrence that (1) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (2) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies.

Definition of a Breach:

The loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where (1) a person other than an authorized user accesses or potentially accesses personally identifiable information or (2) an authorized user accesses or potentially accesses personally identifiable information for an other than authorized purpose.

It further adds:

A breach is not limited to an occurrence where a person other than an authorized user potentially accesses PII by means of a network intrusion, a targeted attack that exploits website vulnerabilities, or an attack executed through an email message or attachment. A breach may also include the loss or theft of physical documents that include PII and portable electronic storage media that store PII, the inadvertent disclosure of PII on a public website, or an oral disclosure of PII to a person who is not authorized to receive that information. It may also include an authorized user accessing PII for an other than authorized purpose.

The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines a breach as “a suspected or confirmed incident involving PII”.

Contracts with entities that collect, maintain, use, or operate Federal information or information systems on behalf of CDC shall include the following requirements:

1) The contractor shall cooperate with and exchange information with CDC officials, as deemed necessary by the CDC Breach Response Team, to report and manage a suspected or confirmed breach.

2) All contractors and subcontractors shall properly encrypt PII in accordance with OMB Circular A-130 and other applicable policies, including CDC-specific policies, and comply with HHS-specific policies for protecting PII. To this end, all contractors and subcontractors shall protect all sensitive information, including any PII created, stored, or transmitted in the performance of this contract so as to avoid a secondary sensitive information incident with FIPS 140-2 validated encryption.

3) All contractors and subcontractors shall participate in regular training on how to identify and report a breach.

4) All contractors and subcontractors shall report a suspected or confirmed breach in any medium as soon as possible and no later than 1 hour of discovery, consistent with applicable CDC IT acquisitions guidance, HHS/CDC and incident management policy, and United States Computer Emergency Readiness Team (US-CERT) notification guidelines. To this end, the Contractor (and/or any subcontractor) shall respond to all alerts/Indicators of Compromise (IOCs) provided by HHS Computer Security Incident Response Center (CSIRC) or CDC Computer Incident Response Team (CSIRT) within 24 hours via email at csirt@cdc.gov or telephone at 866-655-2245, whether the response is positive or negative.

5) All contractors and subcontractors shall be able to determine what Federal information was or could have been accessed and by whom, construct a timeline of user activity, determine methods and techniques used to access Federal information, and identify the initial attack vector.

6) All contractors and subcontractors shall allow for an inspection, investigation, forensic analysis, and any other action necessary to ensure compliance with HHS/CDC Policy and the HHS/CDC Breach Response Plan and to assist with responding to a breach.

7) Cloud service providers shall use guidance provided in the FedRAMP Incident Communications Procedures when deciding when to report directly to US-CERT first or notify CDC first.

8) Identify roles and responsibilities, in accordance with HHS/CDC Breach Response Policy and the HHS/CDC Breach Response Plan. To this end, the Contractor shall NOT notify affected individuals unless and until so instructed by the Contracting Officer or designated representative. If so instructed by the Contracting Officer or representative, all notifications must be pre-approved by the appropriate CDC officials, consistent with HHS/CDC Breach Response Plan, and the Contractor shall then send CDC- approved notifications to affected individuals; and,

9) Acknowledge that CDC will not interpret report of a breach, by itself, as conclusive evidence that the contractor or its subcontractor failed to provide adequate safeguards for PII.

D. Position Sensitivity Designations

All Contractor (and/or any subcontractor) employees must obtain a background investigation commensurate with their position sensitivity designation that complies with Parts 1400 and 731 of Title 5, Code of Federal Regulations (CFR).

Section 12 – Reference Material

· Federal Information Security Management Act of 2002 (FISMA). http://csrc.nist.gov/groups/SMA/fisma/index.html

· Federal Section 508 Laws and Guideline http://www.access-board.gov/508.htm

· The Privacy Act of 1974 - adequate administrative, operational, and technical security controls must be implemented to prevent unauthorized access to or disclosure of any personally identifiable information (PII) that will be accessed by the contractor http://www.hhs.gov/foia/privacy/index.html

· Paperwork Reduction Act (PRA) http://www.hhs.gov/ocio/policy/collection/index.html

· E-Government Act of 2002 http://www.archives.gov/about/laws/egov-act-section-207.html

· CDC Information Technology Guidelines (May be made available by the COR upon request, after execution of a CDC/HHS Non-disclosure Agreement)

· CDC Web Template Guidelines http://www.cdc.gov/healthcommunication/ToolsTemplates

· CDC Social Media Guidelines http://www.cdc.gov/SocialMedia/Tools/guidelines/index.html

· Other guidelines as produced and sanctioned by the CDC.gov web Council and the CDC Social Media Council http://www.cdc.gov/healthcommunication/index.html

· Office of Management and Budget (OMB), National Institute of Standards and Technology (NIST), and General Accounting Office (GAO) policies that can be primarily found at or through the Federal CIO Council website at http://cio.gov

· NCEH/ATSDR Information Resources Governance Board See CDC/HHS Enterprise Performance Life Cycle {EPLC} http://www2a.cdc.gov/cdcup/library/other/eplc.htm NOTE: Copies of relevant non–public CDC internal information security and privacy guidance can be made available upon execution and submission of an appropriate non-disclosure form to the supporting Information System Security Officer, via the Contracting Officer.

Section 13 - Contracting Officer’s Representative Information

TBD

Evaluation Factors

Title: Promotion of Interoperable Public Health Data through Application of Standards and Best Practices for Data Collection, Analysis, Use and Dissemination

1. Technical Evaluation:

Offeror shall provide a discussion of their technical approach and program management plan for providing the services required for this acquisition. Offeror shall provide information on the experience and examples indicating your organizational capacity for projects similar in complexity and scope as proposed under this requirement. Offeror shall provide a clear and substantive understanding of the concepts and requirements of this acquisiton.

This criterion will be evaluated according to the soundness, practicality, and feasibility of the Contractor’s technical approach for providing the services required for this Purchase Order.

2. Price Evaluation:

A price analysis of the quote will be conducted to determine the reasonableness of the Contractor’s price.