N0018320Q0158 Multimedia RFQ Amended.docx
DOCX document 90 KB Posted
- Attached to
- Multimedia Equipment and Installation Federal contract opportunity
- Solicitation number
- N0018320Q0158
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| MHD office pics.docx | DOCX document | |
| N0018320Q0158 Multimedia RFQ.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
N0018320Q0158
Section A - Solicitation/Contract Form
COMPLETE THE FOLLOWING:
Company Name:
TIN:
CAGE:
DUNS:
Point of Contact:
Phone:
E-Mail:
This solicitation is set-aside for small business.
Refer to Section C of RFQ for Salient Characteristics of required items. For this solicitation FAR 52.211-6, Brand name or equal applies see full text in Section I.
Refer to Section M of RFQ information pertaining to criteria for “Best Value” evaluation factors used to determine award.
Include along with quote an invoice(s) with the same/similar items or a Published Price List.
PAYMENT INFORMATION:
Invoice/Payment in Arrears, Net 30 Days
Reference Request for Quotation (RFQ) Number N0018319Q0158 on all correspondence relating to this RFQ/Solicitation.
Naval Medical Center Portsmouth Point of Contact:
Contracting: LaTeasha Cunningham; 757-953-5005; E-Mail: lateasha.e.cunningham.civ@mail.mil
NOTE: Vendor will be required to provide billing electronically via the WAWF Electronic Invoicing Method per Section G of this RFQ. For additional information, a review of the following web sites may be required: https://wawf.eb.mil; http://wawftraining; Email: usn.detrick.navmedlogcomftdmd.list.nmlc-wawf@mail.mil
PROMPT PAYMENT: For Prompt Payment Act purposes, this contract is subject to the 7-calendar day constructive acceptance period.
Section B - Supplies or Services and Prices
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 1 |
| Each |
Multimedia equipment to include install
FFP
Microphone Mixer Amplifier and Telephone Hybrid, 65" LCD Display, HDMI Switcher with RS232 Control, Tabletop Touch Panel, Ceiling speakers, Integrated Controller, Program AV equipment, etc. See Section C: Salient Characteristics FOB: Destination
MILSTRIP: N0018320RC27006
PURCHASE REQUEST NUMBER: N0018320RC27006
PSC CD: 5895
NET AMT
Section C - Descriptions and Specifications
SALIENT CHARACTERISTICS
Microphone Mixer Amplifier and Telephone Hybrid Qty: 1
· Input Only Expansion Box with Channel AEC
Extra Wide Tilt Wall Mount Qty: 1
· For 37” to 70” TVs up to 165lbs
· Black
65” 4K Ultra-HD Commercial LCD Display Qty: 1
· 3240 x 2160 Native Resolution
· HDMI
· RS232
· USB
· VGA
· RJ45
· 2 years warranty
5x1 HDMI 2.0 Switcher with RS232 Control Qty: 1
Ceiling microphones Qty: 2
Ceiling tile speakers Qty: 1
· 2x2 grid Downward firing
· 801-C white
7” Tabletop Touch Panel Qty:1
· Landscape
· 10240x600 ; 16:9
· Audio Full duplex intercom
HDMI wall plate with HDMI, VGA connector Qty: 1 PoE Injector Adapter Qty:1 AV programming Qty: 1
· Program Digital AV equipment
Labor/Installation Qty: 1
· Complete electrical installation of new AV equipment
20x20 watt Mini power amp Qty: 1
Volume controller Qty: 1
· 3 audio volume control channels
· Balanced or Unbalanced line operation
· Programmable 128 steps of audio level, mute audio, variable ramp speed and level presets
· Max input/output level: +16 dBm
· Nominal input level: -10 to +4 dBm
4x4 Matrix Switcher Qty: 1
· for 4K@60Hz (4:2:0) HDMI signals and embedded audio
Cable Package Qty: 1
· Misc. cables, adapters, connectors, and hardware that are not listed to complete the install
Integrated Controller Qty: 1
· 4 Digital I/O Ports
· RS232 / 422/ 485
· 8GB SDHC Flash Memory
· 512 MB onboard RAM
· Ethernet / ICSLan Connections
· File Import / Export from USB Drive
· Active Power Consumption 4.2 W
Rack Enclosure Qty: 1 (wall mounted?)
· Glass Door
· 130lbs. weight capacity
· Adjustable shelf
· Lock
· Casters
Wireless Keyboard and mouse Qty: 1
PWS
PERFORMANCE WORK STATEMENT (PWS)
FOR MULTIMEDIA INSTALLATION AT NAVAL MEDICAL CENTER PORTSMOUTH (NMCP)
PART 1
SCOPE OF WORK
This contract is for the procurement, installation, and programming of multimedia equipment. The contractor shall provide fully operational equipment and systems that meets the government requirements which must interface with existing government provided equipment. The contractor shall provide a plan for a system design to include any changes, recommendations, and wiring with the new installation. All components or equipment installed must be new and fully operational prior to government testing and acceptance. No refurbished equipment will be used for this installation.
GENERAL: This is a non-personal services contract to provide Multimedia equipment installation. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.
Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, other items, and non-personal services necessary to perform a turn-key multimedia installation as defined in this PWS except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.
Background: The procurement, installation, and digital programming of multimedia equipment, along with the removal and disposal of current multimedia equipment.
Objectives:
a. Installation of new equipment
b. Programming if applicable of all digital components
Scope: The installation and programming of multimedia digital systems. The contractor shall accomplish the installation of new multimedia equipment and all programming as require for all digital component or systems to provide a turn-key end product.
Period of Performance: Not applicable for the PWS.
GENERAL INFORMATION
Quality Control: The contractor shall develop and maintain an effective QCP to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which the contractor assures that the work performance complies with the contract requirements of the contract. After acceptance of the QAP the contractor shall receive the KO’s acceptance in writing of any proposed change to the QC system.
Recognized Holidays: Contractor is not required to perform services on holidays.
| New Year’s Day | Labor Day | ||
| Martin Luther King Jr.’s Birthday | Columbus Day | ||
| President’s Day | Veteran’s Day | ||
| Memorial Day | Thanksgiving Day | ||
| Independence Day | Christmas Day |
Hours of Operation: The contractor is responsible for conducting business, between the hours of 0730 a.m. to 4:30 p.m. Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.
Place of Performance: The work to be performed under this contract will be performed at Naval Medical Center Portsmouth, Mental Health Dept. Bldg. 1
Type of Contract: The government will award a FFP Contract.
PHYSICAL Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.
Key Control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the QCP. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the KO.
In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.
The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.
Lock Combinations: Not applicable. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s QCP.
Special Qualifications: The contractor is responsible for ensuring that employees are Cisco and AMX certified for digital programming.
Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.
Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, 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 KO. 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.
PART 2
DEFINITIONS & ACRONYMS
DEFINITIONS AND ACRONYMS:
DEFINITIONS:
CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.
CONTRACTING OFFICER (KO). A person with authority to enter into, administer, and/or terminate contracts, and make related determinations and findings on behalf of the government. This is the only individual who can legally bind the government.
CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.
DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.
DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.
KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.
PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.
QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.
QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.
QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service meet contract requirements.
SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.
WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.
WORK WEEK. Monday through Friday, unless specified otherwise.
ACRONYMS:
| ACOR | Alternate Contracting Officer's Representative | |
| CFR | Code of Federal Regulations | |
| CONUS | Continental United States (excludes Alaska and Hawaii) | |
| COR | Contracting Officer Representative | |
| COTS | Commercial-Off-the-Shelf | |
| DD250 | Department of Defense Form 250 (Receiving Report) | |
| DFARS | Defense Federal Acquisition Regulation Supplement | |
| DOD | Department of Defense | |
| FAR | Federal Acquisition Regulation | |
| HIPAA | Health Insurance Portability and Accountability Act of 1996 | |
| KO | Contracting Officer | |
| OCI | Organizational Conflict of Interest | |
| OCONUS | Outside Continental United States (includes Alaska and Hawaii) | |
| ODC | Other Direct Costs | |
| POC | Point of Contact | |
| PWS | Performance Work Statement | |
| QA | Quality Assurance | |
| QAP | Quality Assurance Program | |
| QASP | Quality Assurance Surveillance Plan | |
| QC | Quality Control | |
| QCP | Quality Control Program | |
| TE | Technical Exhibit |
PART 3
CONTRACTOR FURNISHED ITEMS AND SPECIFIC TASKS
CONTRACTOR RESPONSIBILITIES AND SPECIFIC TASKS:
The Contractor is responsible to submit a package for the installation of multi-media equipment at Naval Medical Center Portsmouth. This package must include a design plan and equipment listing. This design shall include any changes/ recommendations required to interface with existing government provided equipment. All components installed must be fully operational prior to government testing/acceptance. Listings of requirements are included in the CLIN lines.
Basic Services. The contractor shall plan for and provide all required support for the proper operation of all multimedia equipment. This will include all cabling, connections, computer support and termination of cables/fiber into the required communications closets. Additionally, any electrical installations will be the responsibility of the contractor.
The Contractor shall ensure compatibility between new equipment and existing equipment in use throughout the command. The contractor shall include all required fittings, cables, connectors, and power requirements in the project and shall reflect these requirements in their bid.
Contractor is to provide all equipment, material handling equipment (i.e., pallet jacks); labor, communications and anything else required fulfilling all the requirement of this contract in a turnkey manner to include filling holes in walls, using fire stop if penetrating firewalls, and painting exterior walls. Paint samples and/or order information will be given to the contractor upon award.
All on-site work for this project will be performed in the above mentioned areas. The Government Project Manager is responsible for coordinating all network-related procurement and scheduling of the building for this project. The contractor will ensure timely delivery of all equipment ordered through this contract.
The Communications Office is responsible for providing the contractor with facilities and system access. Communications office will be responsible for handling any and all security-related issues pertained to this project, including providing escorted or unescorted access to the base/building where the team will be working. The contractor is responsible for removing all contractor generated trash and debris from the installation. Trash and debris is defined as boxes, packing, etc., from all new equipment purchased and installed under this PWS.
Communications will provide a Project Manager as the primary point of contact for the contractor’s personnel. They will work to coordinate issues as necessary to include:
· Communications, issue resolution and general project decision making.
· Designated Comms staff will support deployment and training phases
Contractors Work and Workforce must conform in all respects with the requirements of the contract. No incompetence or carelessness, no drugs and/or use of alcohol will be tolerated. The contractor’s workforce shall be identifiable by picture identification badges which shall be worn and visible on the upper body at all times while on site and will be required to fill out a Criminal History Record Request supplied by the Communications Office for each employee. These must be submitted five business days prior to employees reporting on site. After five business days the Government will issue a temporary security badge and car sticker for the period of employment on site. The Navy reserves the right to approve employees working on site. Reasons for disapproval are: Any felony conviction within the last 10 years, any larceny misdemeanor in the last 10 years or any other reasons at the Governments sole discretion.
Care of Government Facilities and Property – The contractor shall be responsible for the care of the premises. The contractor shall not damage Government property or facilities during the performance of this contract. The contractor shall furnish padding and other protective materials as necessary to preclude damage to hallways, doors, door frames, elevators and building fixtures. The Government may reject any moving equipment at its sole discretion.
Cleaning Up – At the completion of work and before acceptance and final payment, the contractor shall remove all related rubbish and equipment including available cartons, packing materials, tools, etc. All Government property shall remain as it was prior to installation beginning. If damage occurs, the contractor is responsible to restore and/or replace in a suitable manner any property both public and private that has been damaged or removed in the performance of this contract.
NMCP and Clinic Command Regulations – All Contractor personnel must abide by the rules and regulations while in the above mentioned areas. These rules include no firearms, no smoking or tobacco chewing in any government building, no food or beverages except in authorized areas, minimal noise levels and allowing corridor access to non-move involved patient/personnel/carts.
Section E - Inspection and Acceptance
INSPECTION AND ACCEPTANCE TERMS
Supplies/services will be inspected/accepted at:
| CLIN |
| INSPECT AT |
| INSPECT BY |
| ACCEPT AT |
| ACCEPT BY |
| 0001 |
| Destination |
| Government |
| Destination |
| Government |
CLAUSES INCORPORATED BY REFERENCE
| 52.246-16 |
| Responsibility For Supplies |
| APR 1984 |
Section F - Deliveries or Performance
DELIVERY INFORMATION
| CLIN |
| DELIVERY DATE |
| QUANTITY |
| SHIP TO ADDRESS |
| DODAAC / CAGE |
| 0001 |
| 30-SEP-2020 |
| 1 |
| NAVAL MEDICAL CENTER |
RECEIVING OFFICER
54 LEWIS MINOR STREET
BLDG. 250
PORTSMOUTH VA 23708-2297
757-953-5770 FOB: Destination N00183
| 52.211-17 |
| Delivery of Excess Quantities |
| SEP 1989 |
| 52.247-34 |
| F.O.B. Destination |
| NOV 1991 |
Section G - Contract Administration Data
CLAUSES INCORPORATED BY FULL TEXT
252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)
(a) Definitions. As used in this clause—
“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.
“Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).
“Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.
“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
(c) WAWF access. To access WAWF, the Contractor shall—
(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and
(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.
(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.
(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.
(f) WAWF payment instructions. The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:
(1) Document type. The Contractor shall submit payment requests using the following document type(s):
(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.
(ii) For fixed price line items—
(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.
____________COMBO FOR SUPPLIES________________________________________________
(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)
(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.
(Contracting Officer: Insert either “Invoice 2in1” or the applicable invoice and receiving report document type(s) for fixed price line items for services.)
(iii) For customary progress payments based on costs incurred, submit a progress payment request.
(iv) For performance based payments, submit a performance based payment request.
(v) For commercial item financing, submit a commercial item financing request.
(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.
[Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]
(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.
Routing Data Table*
| Field Name in WAWF |
| Data to be entered in WAWF |
| Pay Official DoDAAC |
| HQ0248 |
| Issue By DoDAAC |
| N00183 |
| Admin DoDAAC** |
| N00183 |
| Inspect By DoDAAC |
| N/A |
| Ship To Code |
| N00183 |
| Ship From Code |
| N/A |
| Mark For Code |
| N/A |
| Service Approver (DoDAAC) |
| N/A |
| Service Acceptor (DoDAAC) |
| N/A |
| Accept at Other DoDAAC |
| N/A |
| LPO DoDAAC |
| N00183 |
| DCAA Auditor DoDAAC |
| N/A |
| Other DoDAAC(s) |
| N/A |
(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert “See Schedule” or “Not applicable.”) (**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)
(4) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.
(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.
(g) WAWF point of contact. To Be Determined At Time of Contract Award
(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.
_USN.DETRICK.NAVMEDLOGCOMFTDMD.LIST.NMLC-WAWF@MAIL.MIL___
(Contracting Officer: Insert applicable information or “Not applicable.”)
(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.
(End of clause)
Section H - Special Contract Requirements
PHI
BUSINESS ASSOCIATE AGREEMENT
Privacy, Access, Use, and Disclosure of Protected Health Information
1. Introduction. In accordance with 45 C.F.R. §§ 164.502(e)(2) and 164.504(e), and DoDM 6025.18, “Implementation of the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule in DoD Health Care Programs,” March 13, 2019, this document serves as a Business Associate Agreement (BAA) between the signatory Parties for purposes of the HIPAA and the “HITECH Act” amendments thereof, as implemented by the HIPAA Rules and DoD HIPAA issuances (both defined below). The Parties are (1) a DoD Military Health System (MHS) component command such as a Navy Medicine Medical Treatment Facility (MTF) (Naval Medical center or Naval hospital), or special mission command (research, public health, other), acting as a HIPAA covered entity, and (2) another Federal or Government organization, civilian academic institution, or other civilian entity, acting as a HIPAA Business Associate (BA). The HIPAA Rules require BAAs between covered entities and BAs. Implementing this BAA requirement, the applicable DoD HIPAA issuances (DoDM 6025.18) provides that requirements applicable to BAs must be incorporated (or incorporated by reference) into the contract or agreement between the Parties.
2. Definitions:
a. Terms. 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 (DoDM6025.18-): Data aggregation, designated record set, disclosure, health care operations, individual, minimum necessary, notice of privacy practices, protected health information (PHI), required by law, secretary, security incident, subcontractor, unsecured PHI, and use.
b. Breach. means actual or possible loss of control, unauthorized disclosure of or unauthorized access to PHI or other Personally Identifiable Information (PII) (which may include, but is not limited to PHI), where 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.
c. BA. shall generally have the same meaning as the term “BA” in the DoD HIPAA issuances, and in reference to this BAA, shall mean the entity (another Government organization, civilian academic institution, or other civilian organization), entering into agreement with a Navy Medicine MTF or special mission command.
d. Agreement. means this BAA together with the documents or other arrangements under which the BA signatory performs services involving access to PHI on behalf of the MHS component signatory to this BAA.
e. 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 a Navy Medicine MTF or special mission command under the Bureau of Medicine and Surgery.
f. DHA Privacy Office. means the Defense Health Agency (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.
g. DoD HIPAA Issuances. means the DoD issuances implementing the HIPAA Rules in the DoD MHS. These issuances are DoDM 6025.18 Implementation of the HIPAA Privacy Rule in DoD Health Care Programs,” March 13, 2019; DoD Instruction 6025.18, Privacy of Individually Identifiable Health Information in DoD Health Care Programs of December 2009, and DoD Instruction 8580.02, Security of Individually Identifiable Health Information in DoD Health Care Programs of August 2015.
h. DoD Privacy Act Issuances. means the DoD issuances implementing the Privacy Act, which are DoD Directive 5400.11, DoD Privacy Program of 29 October 2014, and DoD 5400.11-R, Department of Defense Privacy Program of 8 May 2007.
i. HIPAA Rules. means, collectively, the HIPAA privacy, security, breach and enforcement rules, issued by the United States (US) Department of Health and Human Services (HHS) and codified at 45 C.F.R. §§ 160 and 164, Subpart E (Privacy), Subpart C (Security), Subpart D (Breach) and 45 C.F.R. § 160, Subparts C-D (Enforcement), as amended by the 2013 modifications to those Rules which implemented the “HITECH Act” provisions of Publication L. 111-5. See 78 Federal Regulation 5566-5702 of 25 January 2013 (with corrections at 78 Federal Regulation 32464 of 7 June 2013. Additional HIPAA rules regarding electronic transactions and code sets (45 C.F.R. § 162) are not addressed in this BAA and are not included in the term HIPAA Rules.
j. HHS Breach. means a breach that satisfies the HIPAA Breach Rule definition of “Breach” in 45 C.F.R. § 164.402.
k. 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.
3. Obligations and Activities of BA:
a. The BA shall not access, use, or disclose PHI other than as permitted or required by this Agreement, the controlling Memorandum of Understanding (MOU) or training affiliation agreement, or as required by law.
b. The BA 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 this Agreement, the controlling MOU, or law.
c. The BA shall report to the covered entity any Breach of which it becomes aware and shall proceed with breach response steps required by paragraph 7 (Breach Response) of this BAA. With respect to electronic PHI, the BA shall also respond to any security incident of which it becomes aware in accordance with any information assurance provisions of the Understanding. If at any point the BA becomes aware that a security incident involves a breach, the BA shall immediately initiate breach response as required by paragraph 7 (Breach Response) of this BAA.
d. In accordance with 45 C.F.R. §§ 164.502(e)(1)(ii)) and 164.308(b)(2), respectively, as applicable, the BA shall ensure that any entities that create, receive, maintain, or transmit PHI on behalf of the BA agree to the same restrictions, conditions, and requirements that apply to the BA with respect to such PHI.
e. The BA 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 C.F.R. § 164.524.
f. The BA shall make any amendment(s) to PHI in a designated record set as directed or agreed to by the covered entity pursuant to 45 C.F.R. § 164.526, or take other measures as necessary to satisfy covered entity’s obligations under 45 C.F.R. § 164.526.
g. The BA 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 C.F.R. § 164.528.
h. To the extent the BA is to carry out one or more of the covered entity’s obligation(s) under the HIPAA privacy rule, the BA shall comply with the requirements of HIPAA privacy rule that apply to the covered entity in the performance of such obligation(s).
i. The BA shall make its internal practices, books, and records available to the Secretary and the covered entity for purposes of audit and in determining compliance with the HIPAA Rules.
4. Permitted Uses and Disclosures by BA:
a. The BA may only use or disclose PHI as necessary to perform the services set forth in the Understanding or as required by law. The BA is not permitted to de-identify PHI under DoD HIPAA issuances or the corresponding 45 C.F.R. § 164.514(a) through (c), nor is it permitted to use or disclose de-identified PHI except as provided by the Understanding or directed by the covered entity.
b. The BA 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 BA 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 BA’s own management and administration and legal responsibilities or for data aggregation services as set forth in the following three paragraphs:
(1) Except as otherwise limited in the understanding, the BA may use PHI for the proper management and administration of the BA or to carry out the legal responsibilities of the BA. The foregoing authority to use PHI does not apply to disclosure of PHI, which is covered in the next paragraph.
(2) Except as otherwise limited in the Understanding, the BA may disclose PHI for the proper management and administration of the BA or to carry out the legal responsibilities of the BA, provided that disclosures are required by law, or the BA 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 BA of any instances of which it is aware in which the confidentiality of the information has been breached.
(3) Except as otherwise limited in the Understanding, the BA may use PHI to provide Data Aggregation services relating to the covered entity’s health care operations.
5. Provisions for Covered Entity to Inform BA of Privacy Practices and Restrictions:
a. The covered entity shall provide the BA with the notice of privacy practices that the covered entity produces in accordance with 45 C.F.R.§ 164.520 and the corresponding provision of the DoD HIPAA issuances (DoDM 6025.18).
b. The covered entity shall notify the BA 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 BA’s use or disclosure of PHI.
c. The covered entity shall notify the BA 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 C.F.R. § 164.522, to the extent that such changes may affect the BA’s use or disclosure of PHI.
6. Permissible Requests by Covered Entity. The covered entity shall not request the BA 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 BA as otherwise permitted by this BAA.
7. Breach Response:
a. General. Breach Response is designed to satisfy the DoD Privacy Act issuances and the HIPAA Breach Rule as implemented by the DoD HIPAA issuances. In general, the BA shall report the breach to the covered entity, assess the breach incident, notify affected individuals, and take mitigating actions, as applicable. Because DoD defines “Breach” to include possible (suspected) as well as actual (confirmed) breaches, the BA shall implement these breach response requirements immediately upon the BA’s discovery of a possible breach. The following provisions set forth the BA’s Privacy Act and HIPAA breach response requirements for all breaches, including but not limited to HHS breaches (defined below). In the event of a breach of PII or PHI held by the BA, the BA shall follow the breach response requirements set forth under paragraphs 7, 8, and 9 of this BAA, which are designed to satisfy both the Privacy Act and HIPAA, as applicable.
(1) If a breach involves PII without PHI, then the BA shall comply with DoD Privacy Act issuance breach response requirements only.
(2) If a breach involves PHI (a subset of PII), then the BA shall comply with both Privacy Act and HIPAA breach response requirements.
(3) If a breach involves PHI, it may or may not constitute an HHS Breach. If a breach is not an HHS Breach, then the BA has no HIPAA breach response obligations. In such cases, the BA must still comply with breach response requirements under the DoD Privacy Act issuances.
b. HHS Breach. If the DHA Privacy Office determines that a breach is an HHS Breach, then the BA shall comply with both the HIPAA Breach Rule and DoD Privacy Act issuances, as directed by the DHA Privacy Office, regardless of where the breach occurs.
c. Non-HHS Breach. If the DHA Privacy Office determines that the breach does not constitute an HHS Breach, then the BA shall comply with DoD Privacy Act issuances, as directed by the applicable Service-Level Privacy Office.
d. Service-Level Privacy Office Point of Contact (POC). Brian Martin, who may be reached at Comm: 904-542-3559, DSN: 312-942-3559, or via E-mail: brian.k.martin4.civ@mail.mil, or usn.ncr.bumedfchava.list.bumed-pii-rpt@mail.mil.
| BRIAN K. MARTIN |
| CODE M31 PRIVACY OFFICE |
| BUMED DETACHMENT JACKSONVILLE |
| H2005 KNIGHT LANE |
| PO BOX 140 |
| NAVAL AIR STATION JACKSONVILLE FL 32212 |
8. Breach Reporting Provisions:
a. The BA shall report the breach within 1 business day 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 BA 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 BA.
b. The BA shall submit the US-CERT report using the online form at https://forms.us-cert.gov/report. Before submission to US-CERT, the BA shall save a copy of the on-line report. After submission, the BA shall record the US-CERT Reporting Number. Although only limited information about the breach may be available as of the 1 hour deadline for submission, the BA shall submit the US-CERT report by the deadline. The BA shall e-mail updated information as it is obtained, following the instructions at: http://www.us-cert.gov/pgp/email.html. The BA 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.
BA questions about US-CERT reporting shall be directed to the DHA or Service-Level Privacy Office, not the US-CERT office.
c. The BA 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) (if the Understanding is not a contract, delete these references to the CO and COR), and the BA’s DoD POC unless the POC specifies another addressee for breach reporting. Encryption is not required, because Breach Report Forms should not contain PII or PHI. The email address for notices to the DHA Privacy Office is provided at the Privacy Office web site 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.
d. 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 BA 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 BA shall proceed and, if appropriate, consolidate separately reported breaches for purposes of BA report updates, beneficiary notification, and mitigation.
e. When a Breach Report Form initially submitted is incomplete or incorrect due to unavailable information, or when significant developments require an update, the BA 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 BA shall report include, but are not limited to:
(1) Confirmation on the exact data elements involved.
(2) Root cause of the incident.
(3) Any mitigation actions to include, sanctions, training, incident containment, follow-up, etc. The BA 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 BA shall provide updates to the same Parties as required for the initial Breach Reporting Form. The BA 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.
f. In the event the BA is uncertain on how to apply the above requirements, the BA shall consult with the DHA privacy office or service-level privacy office when determinations on applying the above requirements are needed.
9. Breach - Individual Notification Provisions:
a. Determine if Notification is Required. If the DHA Privacy Office determines that individual notification is required, the BA shall provide written notification to individuals affected by the breach as soon as possible, but no later than 60 working days after the breach is discovered and the identities of the individuals ascertained. The 60-day period begins when the BA is able to determine the identities (including addresses) of the individuals whose records were impacted.
b. Draft Proposed Notification. The BA’s proposed notification to be issued to the affected individuals shall be submitted to the Parties to which reports are submitted under paragraph 7 (breach response) for their review and for approval by the DHA Privacy Office. Upon request, the BA 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 BA 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 BA’s notification to the individuals, at a minimum, shall include the following:
(1) Identify PII Lost. 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 are involved, it is critical to advise the individual that these data elements potentially have been breached.
(2) Inform. The affected 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.
(3) Protective Actions. The affected individual(s) must be informed of what protective actions the BA 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.
(4) Credit Monitoring. The individual(s) must also be informed of any mitigating support services (e.g., 1 year of free credit monitoring, identification of fraud expense coverage for affected individuals, provision of credit freezes, etc.) that the BA may offer affected individuals, the process to follow to obtain those services, 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.
(5) Labeling. BAs 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 BA 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.
c. Notification within 60 Days. If the BA determines that it cannot readily identify, or will be unable to reach, some affected individuals within the 60-day period after discovering the breach, the BA shall so indicate in the initial or updated Breach Report Form. Within the 10-day period, the BA shall provide the approved notification to those individuals who can be reached. Other individuals must be notified within 60 days after identities and addresses are ascertained. The BA 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 BA shall issue a generalized media notice(s) to that population in accordance with Privacy Office approval.
d. Costs. The BA shall, at no cost to the government, bear any costs associated with a breach of PII or PHI that the BA has caused or is otherwise responsible for addressing.
e. Security Incident versus Breach. 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 or PHI. In the event of a security incident not involving a PII or PHI breach, the BA shall follow applicable DoD Information Assurance requirements under its Understanding. If at any point the BA finds that a cyber security incident involves a PII or PHI breach (suspected or confirmed), the BA shall immediately initiate the breach response procedures set forth herein. The BA 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.
10. Termination:
a. Termination. Noncompliance by the BA (or any of its staff, agents, or subcontractors) with any requirements in this BAA may subject the BA to termination under any applicable default or other termination provision of the Understanding.
b. Effect of Termination.
(1) If the Understanding has records management requirements, the BA shall handle such records in accordance with the records management requirements. If the Understanding does not have records management requirements, the records should be handled in accordance with subparagraphs (2) and (3) below. If the Understanding has provisions for transfer of records and PII or PHI to a successor BA or if DHA gives directions for such transfer, the BA shall handle such records and information in accordance with such Understanding provisions or DHA direction.
(2) If the Understanding does not have records management requirements, except as provided in the following paragraph (3), upon termination of the Understanding, for any reason, the BA shall return or destroy all PHI received from the covered entity, or created or received by the BA on behalf of the covered entity that the BA still maintains in any form. This provision shall apply to PHI that is in the possession of subcontractors or agents of the BA. The BA shall retain no copies of the PHI.
(3) If the Understanding does not have records management provisions and the BA determines that returning or destroying the PHI is infeasible, the BA shall provide to the covered entity notification of the conditions that make return or destruction infeasible. Upon mutual agreement of the covered entity and the BA that return or destruction of PHI is infeasible, the BA shall extend the protections of the Understanding to such PHI and limit further uses and disclosures of such PHI to those purposes that make the return or destruction infeasible, for so long as the BA maintains such PHI.
11. Miscellaneous:
a. Survival. The obligations of BA under the “Effect of Termination” provision of this BAA shall survive the termination of the Understanding.
b. Interpretation. Any ambiguity in the Understanding shall be resolved in favor of a meaning that permits the covered entity and the BA to comply with HIPAA and the DoD HIPAA Rules.
UNCLASSIFIED ACCESS
Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information (Jan 2017)
Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors.
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 .