Solicitation_Attachments.docx
DOCX document 95 KB Posted
- Attached to
- Digital Dental Imaging (DDI) System Refresh Federal contract opportunity
- Solicitation number
- N62645-17-Q-0011
About this file
Solicitation Attachments
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Attachment_2_Equipment_Listing_and_Quantities,_Revised.xlsx | XLSX spreadsheet | |
| N62645-17-Q-0011_0003.docx | DOCX document | |
| N62645-17-Q-0011_0002.docx | DOCX document | |
| N62645-17-Q-0011_0001.pdf | ||
| N62645-17-Q-0011.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENTS
1. Statement of Work
1. Equipment Listing and Quantities
1. Business Associate Agreement
1. Contract Administration Plan (CAP) for Fixed Price Contracts
1. Past Performance Information Sheet
Attachment 1: Statement of Work (SOW) The Contractor shall replace, herein referred to as a refresh, the attached list of dental equipment associated with the Digital Dental Imaging (DDI) System at Naval Medical Center, Portsmouth, Naval Health Clinic New England, Naval Hospital (NH) Jacksonville, and NH Pensacola and their branch clinics, see Attachment 2.
Detailed Description of Requirements:
The Contractor shall furnish, install, and provide training for the equipment listed in Attachment 2, Equipment Listing and Quantities. In addition, the Contractor shall install and provide training for the latest version of Apteryx Digital Imaging and Communications in Medicine Capture Viewer (DCV) software, which was purchased by the Government under a separate agreement, and furnish and install additional Apteryx DCV licenses, which are included in Attachment 2. The Contractor shall utilize Commercial Off the shelf (COTS) hardware (servers, computers, etc.) consistent with existing network and x-ray capturing equipment. With the exception of Apteryx, all brand name references are brand name or equal. The minimum requirements for equal products are described below and in Attachment 2. The Government requires retention of any failed hard drive(s) for all servers, storage arrays, computers, and laptops. The system shall provide a redundant system configuration for data integrity and minimize system down time.
The Contractor shall provide full warranty support of all new hardware and software, supplies and services for a period of not less than one (1) year. The Contractor shall acknowledge that there shall be no charge for services or software support during the warranty period for normal warranty support.
Installation and setup of the DDI equipment is essentially replacing similar equipment already installed at each facility. The Contractor shall work with each site to setup and install equipment specified in Attachment 2 at each Dental Clinic and regional data center. Installation and training services shall be provided Monday through Friday during normal business hours. The regional server will be located in each Command’s primary data center. The local servers will go in either a data center or communication closet at the various facilities. The laptop computer workstations will be replacing the existing workstations located in each mobile dental unit. The server shall be loaded with the latest release of the Apteryx DCV version 3.4 software, which includes transfer of the existing DCV Data Manager licenses. The servers and workstations will be hardened by the Government according to local site specifications prior to installation by the Contractor. When setting up each of the Apteryx servers, the Contractor shall work with key personnel at each site and the Naval Medical Logistics Command (NMLC) to incorporate and adhere to the federal social security number (SSN) reduction act numbering scheme. The patient identifier will be changed from the sponsor’s SSN to the new Electronic Data Interchange Person Numbers (EDIPN), also known as the Department of Defense (DoD) identification (ID) number. The new DDI system shall include migration of all existing data on the current servers to new the servers at each facility. The DCV Primary application and DCV additional licenses shall be loaded on the computers designated by the DDI Project Coordinator at each site, contact information to be provided after award. The new DDI equipment shall be thoroughly tested to ensure the proper operation.
The Contractor’s project manager(s) shall fully participate in regular status update briefings to the Government’s representatives, to include a kick-off meeting, regularly scheduled project meetings, and a post or close out meeting, all held via teleconference. The Contractor’s project team will engage Naval Medical Logistics Command Program Office, each Command’s Project Coordinator, Dental Clinical, Information Management Department (IMD), and Materials Management and Facilities leads to ensure that all devices are properly accounted for, as needed.
Training Requirements: During the installation at each site, the Contractor shall offer refresh training that highlights the functional updates within the computer hardware, software application, and supporting DDI equipment to help users become familiar with the system.
Training shall incorporate the perspectives of the Dentist, Dental Technician (DT) and the general clinical/administrative user. These perspectives shall consider the varying levels of detail and application interaction that may be required by the dynamic groups of users that will typically utilize an enterprise DDI solution. System administration training shall be provided to at least two command personnel. These individuals should be from the Information Technology (IT) Department and or Biomedical Repair.
The Contractor shall provide a Pre-Implementation (Survey) Report to NMLC and the responsible site personnel as soon as possible after award to allow time for any facility, network, or other modifications. The Contractor shall, at the completion of the DDI installation, ensure that the DDI system seamlessly acquires, views, prints, stores, and transfers images and data throughout each Dental Clinic and it area of responsibility.
Minimum requirements for Brand name or equal items:
The following are the minimum requirement for an item to be considered equal to the brand name:
DICOM-based dental imaging suite that is scalable to any size organization. The system shall provide a standardized way to capture, store, retrieve, and view dental images across an entire organization. The system shall support imaging devices commonly used in dentistry, including: Intra-oral sensors, specifically Carestream/Kodak 6100 sensors, Phosphor Plate Scanners, Planmeca Panoramic/Cephalometric units, Carestream 3D/CAT scan, Tomography, Intra-oral Cameras, Extra-oral Cameras, Endoscopes, and Flatbed Scanners. The system shall be Digital Imaging and Communications in Medicine (DICOM) and HIPAA compliant with the ability to control who can access the software and what they are able to perform within the application. The system shall seamlessly integrate with the existing Apteryx DICOM Capture Viewer (DCV) Data Manager and Clients at each Dental Clinic. The system shall have full audit trail capabilities that can record the actions of all users. The system shall be capable of acting as a standalone enterprise dental imaging PACS solution or as an acquisition modality with auto submission to a pre-existing PACS.
In addition to the requirements noted above, all equal products must meet the requirements outlined in Attachment 2.
ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)
The Contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this Contract for the Navy via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.
Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.
Travel to Naval Hospital Guantanamo Bay (NHGB):
The Contractor shall have entry approval prior to traveling to NHGB for installation and training. The Government will assist in arranging air transportation to and from NHGB via military or contracted aircraft, reserve government lodging, and rental car during your stay on the Naval Base. Prior to boarding the aircraft, the Contractor is required to pay the one way airfare at the manifest for each flight.
INSTALLATION LOCATIONS:
For Naval Medical Center Portsmouth (except Naval Hospital Guantanamo Bay, Cuba) all equipment, accessories and software shall be shipped to:
Naval Medical Center (NMC) Portsmouth 620 John Paul Jones Circle, Bldg. 250 Portsmouth, VA 23708-5000
The Government will then tag and distribute appropriately to the locations listed below. Upon notice, the Contractor shall proceed to the designated location to provide installation and training as required.
Naval Station Norfolk (Includes 4 Dental Vans) Branch Health Clinic, NAVSTA Norfolk 1647 Admiral Taussig Blvd.
Norfolk, VA 23511-2896
Boone Branch Health Clinic 1035 Nider Blvd., Suite 100 Virginia Beach, VA 23459-2731
Branch Health Clinic Dan Neck Annex Naval Air Station Oceana Dam Neck Annex 1885 Terrier Avenue, Suite 100 Virginia Beach, VA 23461
Oceana Branch Health Clinic Naval Air Station Oceana 1550 Tomcat Blvd., Suite 150 Virginia Beach, VA 23460-2188
Branch Health Clinic, Naval Weapons Station, Yorktown 160 Main Road, Building 1806 Yorktown, VA 23691
Northwest Branch Health Clinic 1317 Ballahack Road Chesapeake VA 23322
Norfolk Naval Shipyard Branch Health Clinic (NNSY) Building 277, Second Floor Norfolk Naval Shipyard Portsmouth, VA, CA 23709
Ship to Location for Naval Hospital Guantanamo Bay GITMO Expediter ICO Trans Atlantic LLC Blount Island Marine Terminal 8998 Blount Island Jacksonville, FL 32226
MARK FOR: NH GTMO, N61564-1199-E146
Training & Installation Location for Naval Hospital Guantanamo Bay
U.S. NAVAL HOSPITAL GITMO
CARAVELA POINT BLDG H-3
GUANTANAMO BAY CU
For Naval Health Clinic New England, all equipment, accessories and software shall be shipped to:
Naval Health Clinic, New England (NHCNE) One Riggs Road Bldg 44, Receiving Code 25 Newport, RI 02841-1000
The Government will then tag and distribute appropriately to the locations listed below. Upon notice, the Contractor shall proceed to the designated location to provide installation and training as required.
Naval Health Clinic New England
43 Smith Road
Newport, RI 02841-1002
Naval Branch Health Clinic, Groton 1 Wahoo Ave Groton, CT 06349
Naval Branch Health Clinic Portsmouth One Ayres Circle Bldg. H-1 PNS Portsmouth, NH 03804-5000
Naval Branch Health Clinic
1 West Avenue, Suite 230
Saratoga Springs, NY 12866
For Naval Hospital Pensacola, all equipment, accessories and software shall be shipped to:
Naval Hospital Pensacola Materiel Management Dept 6000 West Highway 98 Pensacola, FL 32512-0001
The Government will then tag and distribute appropriately to the locations listed below. Upon notice, the Contractor shall proceed to the designated location to provide installation and training as required.
Naval Hospital Pensacola
6000 West Highway 98 Pensacola, FL 32512
Naval Branch Health Clinic, NAS Pensacola
Bldg 3600, Naval Air Station Pensacola Pensacola, FL 32508
Naval Branch Health Clinic, Naval Air Technical Training Center (NATTC) 760 East Avenue, Building 3911 Pensacola, FL 32508
Naval Branch Health Clinic, CWO3 Gary R. Schuetz Memorial Medical Clinic (SMMC) Corry Station 790 Veterans Way Pensacola, FL 32507
Naval Branch Health Clinic, Panama City 2500 Veterans Way Panama City, FL 32408
Naval Branch Health Clinic, NAS Meridian 1801 Fuller Rd.
Meridian, MS 39309
Naval Branch Health Clinic, Naval Construction Battalion Center (NCBC) Gulfport 5501 Marvin Shields Blvd.
Gulfport, Mississippi 39501-5007
Naval Branch Health Clinic, Naval Support Activity (NSA) Mid-South Millington 5722 Integrity Drive, Bldg S-771 Millington, TN 38054-5021
Naval Branch Health Clinic, NAS JRB Belle Chasse 400 Russell Avenue, Bldg 41 New Orleans, LA 70143
For Naval Hospital Jacksonville, all equipment, accessories and software shall be shipped to:
Naval Hospital Jacksonville
BLDG H-2091
2080 Child Street Jacksonville, FL 32214-5000
The Government will then tag and distribute appropriately to the locations listed below. Upon notice, the Contractor shall proceed to the designated location to provide installation and training as required.
Naval Hospital Jacksonville 2080 Child Street, Jacksonville, Florida 32214
Naval Branch Health Clinic (BHC) Naval Air Station (NAS) Jacksonville 104 Child Street Jacksonville, FL 32228
Naval Branch Health Clinic (BHC) Mayport 2104 Massey Ave, Jacksonville, FL 32228
Naval Branch Health Clinic (BHC) Kings Bay USS James Madison Rd, Kings Bay Base, GA 31547
Branch Health Clinic (BHC) Albany 814 Radford Blvd, Albany, GA 31704
Naval Branch Health Clinic (BHC) Key West 1300 Douglas Cir, Key West, FL 33040
SUPTXT204-9400(1-17) Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information
Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The Deputy Secretary of Defense Directive-Type Memorandum (DTM) 08-006 – “DoD Implementation of Homeland Security Presidential Directive – 12 (HSPD-12)” dated November 26, 2008 (or its subsequent DoD instruction) directs implementation of HSPD-12. This clause is in accordance with HSPD-12 and its implementing directives.
APPLICABILITY
This text applies to contractor employees requiring physical access to any area of a federally controlled base, facility or activity and/or requiring access to a DoN or DoD computer/network/system to perform certain unclassified sensitive duties. This clause also applies to contractor employees who access Privacy Act and Protected Health Information, provide support associated with fiduciary duties, or perform duties that have been identified as National Security Position, as advised by the command security manager. It is the responsibility of the responsible security officer of the command/facility where the work is performed to ensure compliance.
Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.
ACCESS TO FEDERAL FACILITIES
Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command’s Security Manager upon arrival to the Command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.
ACCESS TO DOD IT SYSTEMS
In accordance with SECNAV M-5510.30, contractor employees who require access to DoN or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions which require access to information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity’s Command Information Assurance Manager.
Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation , which is a higher level investigation than the National Agency Check with Law and Credit (NACLC)/T3/T3R described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.
Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the “supervisor”.
The SAAR-N shall be forwarded to the Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.
When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.
INTERIM ACCESS
The Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DoN or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.
DENIAL OR TERMINATION OF ACCESS
The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.
CONTRACTOR’S SECURITY REPRESENTATIVE
The contractor shall designate an employee to serve as the Contractor’s Security Representative. Within three work days after contract award, the contractor shall provide to the requiring activity’s Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor’s Security Representative. The Contractor’s Security Representative shall be the primary point of contact on any security matter. The Contractor’s Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.
BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVE DUTIES
Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Contractor employees under this contract are recognized as Non-Critical Sensitive [ADP/IT-II] positions when the contract scope of work require physical access to a federally controlled base, facility or activity and/or requiring access to a DoD computer/network, to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC or T3 or T3R equivalent investigation to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The investigation consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a non-critical sensitive or IT-II position is required to complete:
· SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)
· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)
· Original Signed Release Statements
Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date. Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.
Regardless of their duties or IT access requirements ALL contractor employees shall in-process with the Command’s Security Manager upon arrival to the command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Employees requiring IT access shall also check-in and check-out with the Navy Command’s Information Assurance Manager. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N shall be forwarded to the Navy Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date.
The contractor shall ensure that each contract employee requiring access to IT systems or networks complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. Contractor employees shall accurately complete the required investigative forms prior to submission to the Command Security Manager. The Command’s Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM); Potential suitability or security issues identified may render the contractor employee ineligible for the assignment. An unfavorable determination is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Command’s Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DoD Central Adjudication Facility (CAF) for a determination.
If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the Joint Personnel Adjudication System (JPAS) or a hard copy VAR directly from the contractor’s Security Representative. Although the contractor will take JPAS “Owning” role over the contractor employee, the Command will take JPAS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee’s performance under the contract.
BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO OR PERFORMING NON-SENSITIVE DUTIES
Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc. ...) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:
· Must be either a US citizen or a US permanent resident with a minimum of 3 years legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and
· Must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including a FBI fingerprint check prior to installation access.
To be considered for a favorable trustworthiness determination, the Contractor’s Security Representative must submit for all employees each of the following:
· SF-85 Questionnaire for Non-Sensitive Positions
· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)
· Original Signed Release Statements
The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation, or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM
Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.
* Consult with your Command Security Manager and Information Assurance Manager for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.
Attachment 2: Equipment Listing and Quantities
Attachment 3: Business Associate Agreement
This Business Associate Agreement (BAA) incorporates HIPAA/HITECH Act requirements under the HHS Final Omnibus Rule (78 FR 5566, published 25 Jan 2013), effective 23 Sep 2013. This BAA is for use by MHS components outside of DHA.
Business Associate Agreement
Introduction
In accordance with 45 CFR 164.502(e)(2) and 164.504(e) and paragraph C.3.4.1.3 of DoD 6025.18-R, “DoD Health Information Privacy Regulation,” January 24, 2003, this document serves as a business associate agreement (BAA) between the signatory parties for purposes of the Health Insurance Portability and Accountability Act (HIPAA) and the “HITECH Act” amendments thereof, as implemented by the HIPAA Rules and DoD HIPAA Issuances (both defined below). The parties are a DoD Military Health System (MHS) component, acting as a HIPAA covered entity, and a DoD contractor, acting as a HIPAA business associate. The HIPAA Rules require BAAs between covered entities and business associates. Implementing this BAA requirement, the applicable DoD HIPAA Issuance (DoD 6025.18-R, paragraph C3.4.1.3) provides that requirements applicable to business associates must be incorporated (or incorporated by reference) into the contract or agreement between the parties.
(a) Catchall Definition. Except as provided otherwise in this BAA, the following terms used in this BAA shall have the same meaning as those terms in the DoD HIPAA Rules: Data Aggregation, Designated Record Set, Disclosure, Health Care Operations, Individual, Minimum Necessary, Notice of Privacy Practices (NoPP), Protected Health Information (PHI), Required By Law, Secretary, Security Incident, Subcontractor, Unsecured Protected Health Information, and Use.
Breach means actual or possible loss of control, unauthorized disclosure of or unauthorized access to PHI or other PII (which may include, but is not limited to PHI), where 12 Nov 2013 Page 2 of 10 persons other than authorized users gain access or potential access to such information for any purpose other than authorized purposes, where one or more individuals will be adversely affected. The foregoing definition is based on the definition of breach in DoD Privacy Act Issuances as defined herein.
Business Associate shall generally have the same meaning as the term “business associate” in the DoD HIPAA Issuances, and in reference to this BAA, shall mean the contractor.
Agreement means this BAA together with the documents and/or other arrangements under which the Business Associate signatory performs services involving access to PHI on behalf of the MHS component signatory to this BAA.
Covered Entity shall generally have the same meaning as the term “covered entity” in the DoD HIPAA Issuances, and in reference to this BAA, shall mean the Government facility(s) and office(s) that are supported under this contract.
DHA Privacy Office means the DHA Privacy and Civil Liberties Office. The DHA Privacy Office Director is the HIPAA Privacy and Security Officer for DHA, including the National Capital Region Medical Directorate (NCRMD).
DoD HIPAA Issuances means the DoD issuances implementing the HIPAA Rules in the DoD Military Health System (MHS). These issuances are DoD 6025.18-R (2003), DoDI 6025.18 (2009), and DoD 8580.02-R (2007).
DoD Privacy Act Issuances means the DoD issuances implementing the Privacy Act, which are DoDD 5400.11 (2007) and DoD 5400.11-R (2007).
HHS Breach means a breach that satisfies the HIPAA Breach Rule definition of breach in 45 CFR 164.402.
HIPAA Rules means, collectively, the HIPAA Privacy, Security, Breach and Enforcement Rules, issued by the U.S. Department of Health and Human Services (HHS) and codified at 45 CFR Part 160 and Part 164, Subpart E (Privacy), Subpart C (Security), Subpart D (Breach) and Part 160, Subparts C-D (Enforcement), as amended by the 2013 modifications to those Rules, implementing the “HITECH Act” provisions of Pub. L. 111-5. See 78 FR 5566-5702 (Jan. 25, 2013) (with corrections at 78 FR 32464 (June 7, 2013)). Additional HIPAA rules regarding electronic transactions and code sets (45 CFR Part 162) are not addressed in this BAA and are not included in the term HIPAA Rules.
Service-Level Privacy Office means one or more offices within the military services (Army, Navy, or Air Force) with oversight authority over Privacy Act and HIPAA privacy compliance.
I. Obligations and Activities of Business Associate
(a) The Business Associate shall not use or disclose PHI other than as permitted or required by the Agreement or as required by law.
(b) The Business Associate shall use appropriate safeguards, and comply with the DoD HIPAA Rules with respect to electronic PHI, to prevent use or disclosure of PHI other than as provided for by the Agreement.
(c) The Business Associate shall report to Covered Entity any Breach of which it becomes aware, and shall proceed with breach response steps as required by Part V of this BAA. With respect to electronic PHI, the Business Associate shall also respond to any security incident of which it becomes aware in accordance with any Information Assurance provisions of the Agreement. If at any point the Business Associate becomes aware that a security incident involves a Breach, the Business Associate shall immediately initiate breach response as required by part V of this BAA.
(d) In accordance with 45 CFR 164.502(e)(1)(ii)) and 164.308(b)(2), respectively), as applicable, the Business Associate shall ensure that any subcontractors that create, receive, maintain, or transmit PHI on behalf of the Business Associate agree to the same restrictions, conditions, and requirements that apply to the Business Associate with respect to such PHI.
(e) The Business Associate shall make available PHI in a Designated Record Set, to the Covered Entity or, as directed by the Covered Entity, to an Individual, as necessary to satisfy the Covered Entity obligations under 45 CFR 164.524.
(f) The Business Associate shall make any amendment(s) to PHI in a Designated Record Set as directed or agreed to by the Covered Entity pursuant to 45 CFR 164.526, or take other measures as necessary to satisfy Covered Entity’s obligations under 45 CFR 164.526.
(g) The Business Associate shall maintain and make available the information required to provide an accounting of disclosures to the Covered Entity or an individual as necessary to satisfy the Covered Entity’s obligations under 45 CFR 164.528.
(h) To the extent the Business Associate is to carry out one or more of Covered Entity's obligation(s) under the HIPAA Privacy Rule, the Business Associate shall comply with the requirements of HIPAA Privacy Rule that apply to the Covered Entity in the performance of such obligation(s); and
(i) The Business Associate shall make its internal practices, books, and records available to the Secretary for purposes of determining compliance with the HIPAA Rules.
II. Permitted Uses and Disclosures by Business Associate
(a) The Business Associate may only use or disclose PHI as necessary to perform the services set forth in the Agreement or as required by law. The Business Associate is not permitted to de-identify PHI under DoD HIPAA issuances or the corresponding 45 CFR 164.514(a)-(c), nor is it permitted to use or disclose de-identified PHI, except as provided by the Agreement or directed by the Covered Entity.
(b) The Business Associate agrees to use, disclose and request PHI only in accordance with the HIPAA Privacy Rule “minimum necessary” standard and corresponding DHA policies and procedures as stated in the DoD HIPAA Issuances.
(c) The Business Associate shall not use or disclose PHI in a manner that would violate the DoD HIPAA Issuances or HIPAA Privacy Rules if done by the Covered Entity, except uses and disclosures for the Business Associate’s own management and administration and legal responsibilities or for data aggregation services as set forth in the following three paragraphs.
(d) Except as otherwise limited in the Agreement, the Business Associate may use PHI for the proper management and administration of the Business Associate or to carry out the legal responsibilities of the Business Associate. The foregoing authority to use PHI does not apply to disclosure of PHI, which is covered in the next paragraph.
(e) Except as otherwise limited in the Agreement, the Business Associate may disclose PHI for the proper management and administration of the Business Associate or to carry out the legal responsibilities of the Business Associate, provided that disclosures are required by law, or the Business Associate obtains reasonable assurances from the person to whom the PHI is disclosed that it will remain confidential and used or further disclosed only as required by law or for the purposes for which it was disclosed to the person, and the person notifies the Business Associate of any instances of which it is aware in which the confidentiality of the information has been breached.
(f) Except as otherwise limited in the Agreement, the Business Associate may use PHI to provide Data Aggregation services relating to the Covered Entity’s health care operations.
III. Provisions for Covered Entity to Inform Business Associate of Privacy Practices and Restrictions
(a) The Covered Entity shall provide the Business Associate with the notice of privacy practices that the Covered Entity produces in accordance with 45 CFR 164.520 and the corresponding provision of the DoD HIPAA Issuances.
(b) The Covered Entity shall notify the Business Associate of any changes in, or revocation of, the permission by an Individual to use or disclose his or her PHI, to the extent that such changes affect the Business Associate’s use or disclosure of PHI.
(c) The Covered Entity shall notify the Business Associate of any restriction on the use or disclosure of PHI that the Covered Entity has agreed to or is required to abide by under 45 CFR 164.522, to the extent that such changes may affect the Business Associate’s use or disclosure of PHI.
IV. Permissible Requests by Covered Entity
The Covered Entity shall not request the Business Associate to use or disclose PHI in any manner that would not be permissible under the HIPAA Privacy Rule or any applicable Government regulations (including without limitation, DoD HIPAA Issuances) if done by the Covered Entity, except for providing Data Aggregation services to the Covered Entity and for management and administrative activities of the Business Associate as otherwise permitted by this BAA.
V. Breach Response
(a) In general.
In the event of a breach of PII/PHI held by the Business Associate, the Business Associate shall follow the breach response requirements set forth in this Part V, which is designed to satisfy both the Privacy Act and HIPAA as applicable. If a breach involves PII without PHI, then the Business Associate shall comply with DoD Privacy Act Issuance breach response requirements only; if a breach involves PHI (a subset of PII), then the Business Associate shall comply with both Privacy Act and HIPAA breach response requirements. A breach involving PHI may or may not constitute an HHS Breach. If a breach is not an HHS Breach, then the Business Associate has no HIPAA breach response obligations. In such cases, the Business Associate must still comply with breach response requirements under the DoD Privacy Act Issuances.
If the DHA Privacy Office determines that a breach is an HHS Breach, then the Business Associate shall comply with both the HIPAA Breach Rule and DoD Privacy Act Issuances, as directed by the DHA Privacy Office, regardless of whether the breach occurs at DHA or at one of the Service components. If the DHA Privacy Office determines that the breach does not constitute an HHS Breach, then the Business Associate shall comply with DoD Privacy Act Issuances, as directed by the applicable Service-Level Privacy Office. The following provisions of Part V set forth the Business Associate’s Privacy Act and HIPAA breach response requirements for all breaches, including but not limited to HHS breaches.
This Part V is designed to satisfy the DoD Privacy Act Issuances and the HIPAA Breach Rule as implemented by the DoD HIPAA Issuances. In general, for breach response, the Business Associate shall report the breach to the Covered Entity, assess the breach incident, notify affected individuals, and take mitigation actions as applicable. Because DoD defines “breach” to include possible (suspected) as well as actual (confirmed) breaches, the Business Associate shall implement these breach response requirements immediately upon the Business Associate’s discovery of a possible breach.
(b) Government Reporting Provisions
The Business Associate shall report the breach within one hour of discovery to the US Computer Emergency Readiness Team (US CERT), and, within 24 hours of discovery, to the DHA Privacy Office and the other parties set forth below. The Business Associate is deemed to have discovered a breach as of the time a breach (suspected or confirmed) is known, or by exercising reasonable diligence would have been known, to any person (other than the person committing it) who is an employee, officer or other agent of the Business Associate.
The Business Associate shall submit the US-CERT report using the online form at https://forms.us-cert.gov/report/. Before submission to US-CERT, the Business Associate shall save a copy of the on-line report. After submission, the Business Associate shall record the US-CERT Reporting Number. Although only limited information about the breach may be available as of the one hour deadline for submission, the Business Associate shall submit the US-CERT report by the deadline. The Business Associate shall e-mail updated information as it is obtained, following the instructions at http://www.us-cert.gov/pgp/email.html. The Business Associate shall provide a copy of the initial or updated US-CERT report to the DHA Privacy Office and the applicable Service-Level Privacy Office, if requested by either. Business Associate questions about US-CERT reporting shall be directed to the DHA or Service-Level Privacy Office, not the US-CERT office.
The Business Associate report due within 24 hours shall be submitted by completing the New Breach Reporting Form DD 2959 at the Breach Response page on the DHA Privacy Office web site and emailing that form to, as applicable, the DHA Privacy Office, the Service-Level Privacy Office, the Contracting Officer (CO) and Contracting Officer’s Representative (COR) and the Business Associate’s DoD point of contact (POC) unless the POC specifies another addressee for breach reporting. Encryption is not required, because Breach Report Forms should not contain PII/PHI. The email address for notices to the DHA Privacy Office is provided at the Privacy Office website breach response page. If electronic mail is not available, telephone notification is also acceptable, but all notifications and reports delivered telephonically must be confirmed by email as soon as technically feasible.
If multiple beneficiaries are affected by a single event or related set of events, then a single reportable breach may be deemed to have occurred, depending on the circumstances. The Business Associate shall inform the DHA Privacy Office as soon as possible if it believes that “single event” breach response is appropriate; the DHA Privacy Office will determine how the Business Associate shall proceed and, if appropriate, consolidate separately reported breaches for purposes of Business Associate report updates, beneficiary notification, and mitigation.
When a Breach Report Form initially submitted is incomplete or incorrect due to unavailable information, or when significant developments require an update, the Business Associate shall submit a revised form or forms, stating the updated status and previous report date(s) and showing any revisions or additions in red text. Examples of updated information the Business Associate shall report include, but are not limited to: confirmation on the exact data elements involved, the root cause of the incident, and any mitigation actions to include, sanctions, training, incident containment, follow-up, etc. The Business Associate shall submit these report updates promptly after the new information becomes available. Prompt reporting of updates is required to allow the DHA Privacy Office to make timely final determinations on any subsequent notifications or reports. The Business Associate shall provide updates to the same parties as required for the initial Breach Reporting Form. The Business Associate is responsible for reporting all information needed by the DHA Privacy Office to make timely and accurate determinations on reports to HHS as required by the HHS Breach Rule and reports to the Defense Privacy and Civil Liberties Office as required by DoD Privacy Act Issuances.
In the event the Business Associate is uncertain on how to apply the above requirements, the Business Associate shall consult with the DHA Privacy Office (or the Service-Level Privacy Office, which will consult with the Privacy Office as appropriate) when determinations on applying the above requirements are needed.
(c) Individual Notification Provisions
If the DHA Privacy Office determines that individual notification is required, the Business Associate shall provide written notification to individuals affected by the breach as soon as possible, but no later than 10 working days after the breach is discovered and the identities of the individuals are ascertained. The 10 day period begins when the Business Associate is able to determine the identities (including addresses) of the individuals whose records were impacted.
The Business Associate’s proposed notification to be issued to the affected individuals shall be submitted to the parties to which reports are submitted under paragraph V(a) for their review, and for approval by the DHA Privacy Office. Upon request, the Business Associate shall provide the DHA Privacy Office with the final text of the notification letter sent to the affected individuals. If different groups of affected individuals receive different notification letters, then the Business Associate shall provide the text of the letter for each group. (PII shall not be included with the text of the letter(s) provided.) Copies of further correspondence with affected individuals need not be provided unless requested by the Privacy Office. The Business Associate’s notification to the individuals, at a minimum, shall include the following:
—The individual(s) must be advised of what specific data was involved. It is insufficient to simply state that PII has been lost. Where names, Social Security Numbers (SSNs) or truncated SSNs, and Dates of Birth (DOBs) are involved, it is critical to advise the individual that these data elements potentially have been breached.
—The individual(s) must be informed of the facts and circumstances surrounding the breach. The description should be sufficiently detailed so that the individual clearly understands how the breach occurred.
—The individual(s) must be informed of what protective actions the Business Associate is taking or the individual can take to mitigate against potential future harm. The notice must refer the individual to the current Federal Trade Commission (FTC) web site pages on identity theft and the FTC’s Identity Theft Hotline, toll-free: 1-877-ID-THEFT (438-4338); TTY: 1-866-653-4261.
—The individual(s) must also be informed of any mitigation support services (e.g., one year of free credit monitoring, identification of fraud expense coverage for affected individuals, provision of credit freezes, etc.) that the Business Associate may offer affected individuals, the process to follow to obtain those services and the period of time the services will be made available, and contact information (including a phone number, either direct or toll-free, e-mail address and postal address) for obtaining more information.
Business Associates shall ensure any envelope containing written notifications to affected individuals are clearly labeled to alert the recipient to the importance of its contents, e.g., “Data Breach Information Enclosed,” and that the envelope is marked with the identity of the Business Associate and/or subcontractor organization that suffered the breach. The letter must also include contact information for a designated POC to include, phone number, email address, and postal address.
If the Business Associate determines that it cannot readily identify, or will be unable to reach, some affected individuals within the 10 day period after discovering the breach, the Business Associate shall so indicate in the initial or updated Breach Report Form. Within the 10 day period, the Business Associate shall provide the approved notification to those individuals who can be reached. Other individuals must be notified within 10 days after their identities and addresses are ascertained. The Business Associate shall consult with the DHA Privacy Office, which will determine which media notice is most likely to reach the population not otherwise identified or reached. The Business Associate shall issue a generalized media notice(s) to that population in accordance with Privacy Office approval.
The Business Associate shall, at no cost to the government, bear any costs associated with a breach of PII/PHI that the Business Associate has caused or is otherwise responsible for addressing.
Breaches are not to be confused with security incidents (often referred to as cyber security incidents when electronic information is involved), which may or may not involve a breach of PII/PHI. In the event of a security incident not involving a PII/PHI breach, the Business Associate shall follow applicable DoD Information Assurance requirements under its Agreement. If at any point the Business Associate finds that a cyber security incident involves a PII/PHI breach (suspected or confirmed), the Business Associate shall immediately initiate the breach response procedures set forthhere. The Business Associate shall also continue to follow any required cyber security incident response procedures to the extent needed to address security issues, as determined by DoD/DHA.
VI. Termination
(a) Termination. Noncompliance by the Business Associate (or any of its staff, agents, or subcontractors) with any requirement in this BAA may subject the Business Associate to termination under any applicable default or other termination provision of the Agreement.
(b) Effect of Termination.
(1) If the Agreement has records management requirements, the Business Associate shall handle such records in accordance with the records management requirements. If the Agreement does not have records management requirements, the records should be handled in accordance with paragraphs (2) and (3) below. If the Agreement has provisions for transfer of records and PII/PHI to a successor Business Associate, or if DHA gives directions for such transfer, the Business Associate shall handle such records and information in accordance with such Agreement provisions or DHA direction.
(2) If the Agreement does not have records management requirements, except as provided in the following paragraph (3), upon termination of the Agreement, for any reason, the Business Associate shall return or destroy all PHI received from the Covered Entity, or created or received by the Business Associate on behalf of the Covered Entity that the Business Associate still maintains in any form. This provision shall apply to PHI that is in the possession of subcontractors or agents of the Business Associate. The Business Associate shall retain no copies of the PHI.
(3) If the Agreement does not have records management provisions and the Business Associate determines that returning or destroying the PHI is infeasible, the Business Associate shall provide to the Covered Entity notification of the conditions that make return or destruction infeasible.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .