SOW Over the Phone.docx
DOCX document 47 KB Posted
- Attached to
- On-the-Phone Translation Services
- Solicitation number
- W91YTZ-22-R-0043
- Issued by
-
Department of the Army Medical Command
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Questions and Comments sources sought.docx | DOCX document | |
| Questions and Comments sources sought.docx | DOCX document | |
| CLIN Breakdown - Meade MEDDAC Over The Phone Interpretation.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATEMENT OF WORK
OVER THE PHONE TRANSLATION SERVICES
FORT MEADE MEDDAC:
Kimbrough Ambulatory Care Center, Fort George G. Meade, Maryland Barquist US Army Health Clinic, Fort Detrick, Maryland Andrew Rader US Army Health Clinic at Joint Base-Henderson Hall, Fort Myer, Virginia Kirk US Army Health Clinic, Aberdeen Proving Ground Maryland Edgewood Clinic, Gunpowder Maryland.
Dunham US Army Health Clinic, Carlisle Barracks, Pennsylvania Fillmore Army Health Clinic, New Cumberland, Pennsylvania Letterkenny Health Clinic, Chambersburg, Pennsylvania
1. 0. INTRODUCTION.
1.0.1. The Contractor shall provide over the phone language interpreter services between clinic personnel and patients as well as translation of vital medical documents and forms, as required for the Fort Meade MEDDAC facilities;
Kimbrough Ambulatory Care Center, Fort George G. Meade, Maryland Barquist US Army Health Clinic, Fort Detrick, Maryland Andrew Rader US Army Health Clinic at Joint Base-Henderson Hall, Fort Myer, Virginia Kirk US Army Health Clinic, Aberdeen Proving Ground Maryland Edgewood Clinic, Gunpowder Maryland.
Dunham US Army Health Clinic, Carlisle Barracks, Pennsylvania Fillmore Army Health Clinic, New Cumberland, Pennsylvania Letterkenny Health Clinic, Chambersburg, Pennsylvania.
The services will be of a nature and scope described in the paragraphs below. The contract employee will work in conjunction with health care providers, professionals, and non-contract personnel. The Contractor HCP shall provide the non-personal services of a certificated linguist to perform services of the nature and scope described in this Statement of Work (SOW).
1.0.1.1. The quality of care provided by the Contractor HCP shall be of a quality meeting or exceeding currently recognized national standards as established by the Joint Commission (JC) and Health Insurance Portability & Accountability Act (HIPAA). Contractor HCP shall give the highest regard to patient dignity and observe the precepts of the American Hospital Association’s Bill of Rights for Patients. The Contractor HCP shall abide by the Medical Treatment Facility (MTF) rules, regulations and by laws, including Medical Staff By laws, as well as applicable Army regulations governing such things as medical records.
1.1. GENERAL.
1.1.1. This contract is a non-personal services contract under which the personnel rendering the services are not subject, either by the contract’s terms or by the manner of its administration, to the supervision and control usually prevailing in relationships between the government and its employees.
1.1.2. Responsibility and Procedures. If any suit or action is filed or any claim is made against the contractor which occurred as a result of work performed by the contractor under this contract, the contractor shall immediately notify the contractor and the Contracting Officer and the chief of the appropriate services and promptly furnish them copies of all pertinent papers received.
1.1.3. The contractor shall cooperate with the government, without further compensation, in the processing, review, settlement, or defense of the suit, action, or claim; and authorize government representatives to settle or defend the claim and to represent the contractor in, or take charge of, any litigation involved in such an action. The Contractor may, at the Contractor’s own expense, participate in defense of such claim or litigation.
1.1.5. Confidentiality / HIPAA. The Contractor shall abide by AR 40-3 and AR 40-66 concerning the nature of limited privileged communication between patient and health care provider for security and personnel reliability programs. The Contractor shall abide by AR 40-66 concerning the confidentiality of patient records, as embodied in federal statutes including the Privacy Act of 1974 and the Drug and Alcohol Act, Public Law 92-129 and HIPAA. The Contractor shall direct all requests for medical information on patients to the Chief, Patient Administration Division. The Contractor shall not release any medical or personal information on a patient without first receiving written approval from the government. Government will provide the regulations upon request by the Contractor.
1.1.6. Removal of Contract. At any time during the performance of this contract, the Contracting Officer or COR may direct the contractor to immediately remove any contract employee whose actions or impaired state raises reasonable suspicion that clear and present danger of physical harm exists to a fellow contract employee, government personnel or to the impaired individual. This provision will be used in emergency situations only and not for the purpose of bringing performance issues or other non-urgent concerns to the attention of the contractor.
1.1.7. Conflict of Interest.
1.1.7.1. Contract employee shall not bill anyone else for services rendered. The Contract employee is prohibited from receiving compensation of any kind except under the terms and conditions of this contract, at the rate specified in the contract.
1.1.7.2. Contractor shall not be an employee of the United States Government if the employment would create a conflict of interest. The Contractor who is an employee of the Department of Defense, either military or civilian, shall not be employed unless such person seeks and receives approval in accordance with DoD 5500.7-R and MEDCOM Reg 600-3.
1.1.7.3. SCOPE OF WORK: The Contractor shall provide qualified personnel, services, materials, equipment, supplies and facilities necessary to perform. The contractor shall meet all terms of this contract. The contractor shall have a complete understanding of the scope of work, and how this requirement will be accomplished from the implementation of the contract, through daily service. The contractor shall understand the size of the project and will provide full service, at high levels of quality, all aspects of this project, including translation services throughout the life of the contract. The contractor shall agree with and will comply with all the requirements needed to provide service.
The contractor shall meet the required start date of 01 April 2017. The contractor shall have the technical expertise to allow any of the Fort Meade MEDDAC facilities to connect through one toll-free number to receive translation services and the available staff to begin working on the start date listed. The contractor has completed detailed and exhaustive training and is up to date on all practices.
1.1.7.4. The Contractor shall comply with all applicable laws, rules and regulations, including but not limited to those included the SOW.
1.1.7.5. MEDIA INQUIRIES. The contractor shall not respond to any media inquiries. Any inquiries from the media shall be immediately relayed to the COR who will relay them to the MTF Commander. There shall be no interviews, comments, or any other response without the knowledge and approval of the MTF commander. Other than routine inquiries for external agencies, all other inquiries and complaints shall be brought to the attention of the contractor and contractor employee.
1.2. STANDARDS OF PERFORMANCE.
1.2.1. The government requires that the contractor shall provide technically competent linguists that will provide services at a standard enabling the Military Treatment Facility to provide a high level of quality health care.
1.2.2 The Contractor shall provide all personnel, tools and equipment to include personnel for over the phone translation services for any language required. Contractor will provide a toll-free number and be available from 0600-1630 Eastern Time Monday through Friday, and answer all calls within 2 rings. Contractor and their personnel will be a US based company.
1.2.3. The government requires that the contractor shall provide qualified, professional, experienced language interpreters who possess a high level of interpretation skills and proficiency in English and the non-English speaker’s language as well as medical terminology, providing professional, complete and accurate interpretation. Specifically, interpreters employed by the Contractor must be United States citizens or lawfully admitted into the United States for permanent residence. Contractor personnel will have valid, current certification in the identified language and medical terminology, anatomy and physiology.
1.2.4. Languages
Interpretation languages are grouped into two (2) categories. The first category is “Common Languages” and the second category is “Uncommon Languages.”
Common languages are defined as those used most often in the previous twelve month period and should not be construed to predict future patterns. The Contractor shall provide over the phone interpreters for any language requested, regardless of category. If the language is not already listed in a category, it will be included in the uncommon category for the current contract period.
At the beginning of each option period, the Government will provide a new listing of Common and Uncommon languages for the contract requirements. Languages that have been utilized by the translation service more than twelve (12) times in the year will be moved to the ‘Common Languages’ category.
Contractors will document the languages required and provide to the government representative monthly, by the fifth of each month for the previous month.
Contractor will provide personnel who are professional and able to provide accurate interpretation in any of the following languages:
Commonly used languages:
Spanish
| Korean |
| Japanese |
Mandarin
| French |
| Arabic |
Portuguese
| Russian |
| Tagalog |
German
Uncommon Languages:
| Acholi |
| Duala |
| Javanese |
| Mnong |
| Somali |
| Afar |
| Dutch |
| Jingpho |
| Mongolian |
| Soninke |
| Afrikaans |
| Dzongkha |
| Jinyu |
| Moroccan Arabic |
| Sorani |
| Akan |
| Edo |
| Juba Arabic |
| Mortlockese |
| Sudanese Arabic |
| Akateko |
| Estonian |
| Jula |
| Napoletano |
| Sunda |
| Albanian |
| Ewe |
| Kaba |
| Navajo |
| Susu |
| Amharic |
| Farsi |
| Kamba |
| Nepali |
| Swahili |
| Anuak |
| Fijian |
| Kanjobal |
| Ngambay |
| Swedish |
| Apache |
| Fijian Hindi |
| Kannada |
| Nigerian Pidgin |
| Sylhetti |
| Armenian |
| Finnish |
| Karen |
| Norwegian |
| Taiwanese |
| Assyrian |
| Flemish |
| Kashmiri |
| Nuer |
| Tajik |
| Azerbaijani |
| French Canadian |
| Kayah |
| Nupe |
| Tamil |
| Bahasa |
| Fukienese |
| Kazakh |
| Nyanja |
| Teluga |
| Bahdini |
| Fulani |
| Kham |
| Nyoro |
| Thai |
| Bahnar |
| Fuzhou |
| Khana |
| Ojibway |
| Tibetan |
| Bajuni |
| Ga |
| Khmer |
| Oromo |
| Tigré |
| Bambara |
| Gaddang |
| K’iché |
| Palauan |
| Tigrigna |
| Bantu |
| Gaelic-Irish |
| Kikuyu |
| Pampangan |
| Toishanese |
| Barese |
| Gaelic-Scottish |
| Kimiiru |
| Papiamento |
| Tongan |
| Basque |
| Garre |
| Koho |
| Pashto |
| Tooro |
| Bassa |
| Gen |
| Kpelle |
| Plautdietsch |
| Trique |
| Behdini |
| Georgian |
| Krahn |
| Pohnpeian |
| Turkish |
| Belorussian |
| Gheg |
| Krio |
| Polish |
| Turkmen |
| Bemba |
| Gokana |
| Kunama |
| Portuguese, Brazilian |
| Tzotzil |
| Benaadir |
| Greek |
| Kurmanji |
| Portuguese, Cape Verdean |
| Ukranian |
| Bengali |
| Gujarati |
| Kyrgyz |
| Pugliese |
| Urdu |
| Berber |
| Gulay |
| Laotian |
| Pulaar |
| Uyghur |
| Bosnian |
| Gurani |
| Latvian |
| Punjabi |
| Uzbek |
| Bravanese |
| Haitian Creole |
| Liberian Pidgin English |
| Putian |
| Vietnamese |
| Bulgarian |
| Hakka-China |
| Lingala |
| Quechua |
| Visayan |
| Burmese |
| Hakka-Taiwan |
| Lithuanian |
| Quichua |
| Welsh |
| Cantonese |
| Hassaniyya |
| Luba-Kasai |
| Rade |
| Wuzhou |
| Catalan |
| Hausa |
| Luganda |
| Rakhine |
| Yemeni Arabic |
| Cebuano |
| Hebrew |
| Luo |
| Rohingya |
| Yiddish |
| Chaldean |
| Hiligaynon |
| Maay |
| Romanian |
| Yoruba |
| Chamorro |
| Hindi |
| Macedonian |
| Rundi |
| Yunnanese |
| Chaochow |
| Hindko |
| Malay |
| Rwanda |
| Zapoteco |
| Chin Falam |
| Hmong |
| Malayalam |
| Samoan |
| Zarma |
| Chin Hakha |
| Hunanese |
| Maltese |
| Sango |
| Zyphe |
| Chin Mara |
| Hungarian |
| Mam |
| Seraiki |
| Chin Matu |
| Ibanag |
| Mandinka |
| Serbian |
| Chin Senthang |
| Icelandic |
| Maninka |
| Shanghainese |
| Chin Tedim |
| Igbo |
| Manobo |
| Shona |
| Chipewyan |
| Ilocano |
| Marathi |
| Sichuan Yi |
| Chuukese |
| Indonesian |
| Marka |
| Sicilian |
| Cree |
| Inuktitut |
| Marshallese |
| Sinhala |
| Croatian |
| Italian |
| Mbay |
| Slovak |
| Czech |
| Jakartanese |
| Mien |
| Slovene |
| Danish |
| Jamaican Patois |
| Mirpuri |
| Soga |
| Dari |
| Jarai |
| Mixteco |
| Wodaabe |
Dewoin
| Mizo |
| Wolof |
Dinka
1.2.5. Other performance evaluation factors will be monitored that are not quantified by numerical measurements which include: contractor providing personnel exceeding the minimum qualification standards; patient customer service comments; provider and contractor relationship with hospital staff/government contracting personnel; compliance with hospital policy and procedures.
1.2.6 The Contractor shall be responsible for the security of all patient information.
1.2.7 Neither the Contractor nor any of its contract service providers shall disclose or cause to disseminate any information concerning operations of military activities. Such action(s) could result in violation of the contract and possible legal actions.
1.2.8. All inquiries, comments or complaints arising from any matter observed, experienced, or learned of as a result of or in connection with the performance of this contract, the resolution of which may require the dissemination of official information, shall be directed to the contracting officer representative (COR) and the contracting officer.
1.2.9. U.S. Government records, copies of original results and reports, verified original data, corrected data, and corrected supporting final reports are maintained by the Contractor, but remain the property of the U.S. Government. These files/results must be surrendered to the COR.
1.2.10. Contractor will provide, at no cost to the government, materials, such as Interpreter access instruction/reference guides, and language identification guides.
1.2.11. Contractor is required to maintain OPSEC training and forward certification to the government representative.
1.2.12. IDENTIFICATION OF PRIVACY ACT. This contract requires the development of a system of records in accordance with the Privacy Act of 1974.
1.2.13. PERFORMANCE QUALITY. The Contractor shall establish and maintain a complete Quality Control Plan that shall ensure the requirements of the contract are provided as specified in Section 5 of the PWS. Within thirty calendar days after contract award, three copies of a comprehensive written QCP shall be submitted to the COR and within 5 working days when changes are made thereafter.
2.0. DEFINITIONS AND ACRONYMS.
2.1. DEFINITIONS:
CONTRACTOR. The term as used in this contract refers to the prime.
CONTRACTING OFFICER. A person with authority to enter into contracts; administer, or terminate contracts. Make related determinations and findings on behalf of the government. Note: 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 monitor contractor performance. 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.
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 ASSESSMENT AND IMPROVEMENT (QA& I): An ongoing program designed to objectively and systematically monitor and evaluate the quality and appropriateness of patient care, to pursue opportunities to improve patient care, and to resolve identified problems.
QUALITY CONTROL (QC): Those actions taken by the Contractor to control and ensure that performance of duties meet the requirements of the contract.
SUBCONTRACTOR: One that enters into a subcontract and assumes some of the obligations of the primary Contractor.
2.2. ACRONYMS.
| ACOR | - | Alternate Contracting Officer's Representative |
| ADP | - | Automated Data Processing |
| AR | - | Army Regulation |
ATS - Application & training Solutions
| CFR | - | Code of Federal Regulations | |
| COR | - | Contracting Officer Representative | |
| COTR | - | Contracting Officer's Technical Representative | |
| CVS | - | Contractor employee Verification System | |
| DA | - | Department of Army | |
| DEA | - | Drug Enforcement Administration | |
| DA | - | Department of the Army | |
| DEA | - | Drug Enforcement Administration | |
| DOD | - | Department of Defense | |
| FAR | - | Federal Acquisition Regulation | |
| FIPS PUB | - | Federal Information Processing Standards Publication | |
| FSO | - | Facility Security Officer | |
| HIPAA | - | Health Insurance Portability & Accountability Act of 1996 | |
| HSPD | - | Homeland Security Presidential Directive | |
| JC | - | Joint Commission | |
| KO | - | Contracting Officer |
MT - Medical Transcriptional
| MTF | - | Military Treatment Facility |
| PWS | - | Performance Work Statement |
| PIPO | - | Phase In/Phase Out |
| PL | - | Public Law |
| POC | - | Point of Contact |
TAT - Turnaround time
| QA&I | - | Quality Assessment & Improvement |
| QA | - | Quality Assurance |
| QC | - | Quality Control |
| QAP | - | Quality Assurance Program |
| QASP | - | Quality Assurance Surveillance Plan |
| QCP | - | Quality Control Program |
3.0. LEGAL HOLIDAYS: The following legal holidays are observed by Kimbrough Ambulatory Care Center.
| New Year's Day | 1 January | |
| Martin Luther King's Birthday | Third Monday in January President's Day | Third Monday in February |
| Memorial Day | Last Monday in May | |
| Independence Day | 4 July | |
| Labor Day | First Monday in September | |
| Columbus Day | Second Monday in October | |
| Veteran's Day | 11 November | |
| Thanksgiving Day | Fourth Thursday in November | |
| Christmas Day | 25 December | |
| Juneteenth | 19 June |
4.0. ATTACHMENT/TECHNICAL EXHIBIT LIST.
ATTACHMENT 1 – PROFESSIONAL QUALIFICATIONS/RESPONSIBILITIES.
ATTACHMENT 2– Quality Assurance Surveillance Plan (QASP)
ATTACHMENT #1
PROFESSIONAL QUALIFICATIONS / RESPONSIBILITIES. The contractor shall meet the qualifications for that specialty and perform essentially the same functions, within the scope of acceptable for their technical professional discipline and standard, as those required by Army or government service technical professionals of similar experience and in similar duty assignments.
a. The contractor shall meet the required start date of 01 April 2017. The contractor shall have the technical expertise to allow any of the Fort Meade MEDDAC facilities to connect through one toll-free number to receive translation services and the available staff to begin working on the start date listed. The contractor has completed detailed training and is up to date on all practices
b. The Contractor will maintain a toll-free number for use by the Fort Meade MEDDAC clinical personnel and ensure there is no disruption of service.
c. The Contractor shall meet the requirement to answer the telephone within 2 rings and provide immediate, accurate over-the-phone translation services between clinic personnel and our patients.
d. The contractor shall ensure their translation staff have the necessary resources to perform translation services to include training. The staff will be qualified, professional, experienced language interpreters who possess a high level of interpretation skills and proficiency in English and the non-English speaker’s language as well as medical terminology, providing professional, complete and accurate interpretation.
e. Contractor will provide personnel who are professional and able to provide accurate interpretation in any of the following languages:
Spanish
| Korean |
| Japanese |
Mandarin
| French |
| Arabic |
Portuguese
| Russian |
| Tagalog |
German
| Acholi |
| Duala |
| Javanese |
| Mnong |
| Somali |
| Afar |
| Dutch |
| Jingpho |
| Mongolian |
| Soninke |
| Afrikaans |
| Dzongkha |
| Jinyu |
| Moroccan Arabic |
| Sorani |
| Akan |
| Edo |
| Juba Arabic |
| Mortlockese |
| Sudanese Arabic |
| Akateko |
| Estonian |
| Jula |
| Napoletano |
| Sunda |
| Albanian |
| Ewe |
| Kaba |
| Navajo |
| Susu |
| Amharic |
| Farsi |
| Kamba |
| Nepali |
| Swahili |
| Anuak |
| Fijian |
| Kanjobal |
| Ngambay |
| Swedish |
| Apache |
| Fijian Hindi |
| Kannada |
| Nigerian Pidgin |
| Sylhetti |
| Armenian |
| Finnish |
| Karen |
| Norwegian |
| Taiwanese |
| Assyrian |
| Flemish |
| Kashmiri |
| Nuer |
| Tajik |
| Azerbaijani |
| French Canadian |
| Kayah |
| Nupe |
| Tamil |
| Bahasa |
| Fukienese |
| Kazakh |
| Nyanja |
| Teluga |
| Bahdini |
| Fulani |
| Kham |
| Nyoro |
| Thai |
| Bahnar |
| Fuzhou |
| Khana |
| Ojibway |
| Tibetan |
| Bajuni |
| Ga |
| Khmer |
| Oromo |
| Tigré |
| Bambara |
| Gaddang |
| K’iché |
| Palauan |
| Tigrigna |
| Bantu |
| Gaelic-Irish |
| Kikuyu |
| Pampangan |
| Toishanese |
| Barese |
| Gaelic-Scottish |
| Kimiiru |
| Papiamento |
| Tongan |
| Basque |
| Garre |
| Koho |
| Pashto |
| Tooro |
| Bassa |
| Gen |
| Kpelle |
| Plautdietsch |
| Trique |
| Behdini |
| Georgian |
| Krahn |
| Pohnpeian |
| Turkish |
| Belorussian |
| Gheg |
| Krio |
| Polish |
| Turkmen |
| Bemba |
| Gokana |
| Kunama |
| Portuguese, Brazilian |
| Tzotzil |
| Benaadir |
| Greek |
| Kurmanji |
| Portuguese, Cape Verdean |
| Ukranian |
| Bengali |
| Gujarati |
| Kyrgyz |
| Pugliese |
| Urdu |
| Berber |
| Gulay |
| Laotian |
| Pulaar |
| Uyghur |
| Bosnian |
| Gurani |
| Latvian |
| Punjabi |
| Uzbek |
| Bravanese |
| Haitian Creole |
| Liberian Pidgin English |
| Putian |
| Vietnamese |
| Bulgarian |
| Hakka-China |
| Lingala |
| Quechua |
| Visayan |
| Burmese |
| Hakka-Taiwan |
| Lithuanian |
| Quichua |
| Welsh |
| Cantonese |
| Hassaniyya |
| Luba-Kasai |
| Rade |
| Wuzhou |
| Catalan |
| Hausa |
| Luganda |
| Rakhine |
| Yemeni Arabic |
| Cebuano |
| Hebrew |
| Luo |
| Rohingya |
| Yiddish |
| Chaldean |
| Hiligaynon |
| Maay |
| Romanian |
| Yoruba |
| Chamorro |
| Hindi |
| Macedonian |
| Rundi |
| Yunnanese |
| Chaochow |
| Hindko |
| Malay |
| Rwanda |
| Zapoteco |
| Chin Falam |
| Hmong |
| Malayalam |
| Samoan |
| Zarma |
| Chin Hakha |
| Hunanese |
| Maltese |
| Sango |
| Zyphe |
| Chin Mara |
| Hungarian |
| Mam |
| Seraiki |
| Chin Matu |
| Ibanag |
| Mandinka |
| Serbian |
| Chin Senthang |
| Icelandic |
| Maninka |
| Shanghainese |
| Chin Tedim |
| Igbo |
| Manobo |
| Shona |
| Chipewyan |
| Ilocano |
| Marathi |
| Sichuan Yi |
| Chuukese |
| Indonesian |
| Marka |
| Sicilian |
| Cree |
| Inuktitut |
| Marshallese |
| Sinhala |
| Croatian |
| Italian |
| Mbay |
| Slovak |
| Czech |
| Jakartanese |
| Mien |
| Slovene |
| Danish |
| Jamaican Patois |
| Mirpuri |
| Soga |
| Dari |
| Jarai |
| Mixteco |
| Wodaabe |
Dewoin
| Mizo |
| Wolof |
Dinka
ATTACHMENT # 2 - QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)
The following minimum Quality Assurance Plan applies. The Government may modify inspection methods in accordance with site specific requirements.
| PERFORMANCE OBJECTIVE |
| PERFORMANCE STANDARD |
| REF PBWS |
| METHOD OF ASSESSMENT |
| CORRECTIVE ACTIONS TO BE TAKEN BY THE GOVERNMENT |
| Customer Service |
| Meet customer service requirements |
| COR/Clinical Staff Input and patient customer service comments |
| Increased monitoring by COR |
| Comply with timeliness of interpretation |
| Meeting 3 ring answer, providing interpretation as required by patient and provider |
| COR monitoring with Clinical Staff input |
| Repeated complaints from clinic staff (more than 3/month) may result in cure notice being process |
H. EXCLUSION FROM PARTICIPATION IN FEDERAL HEALTH CARE PROGRAMS (OCTOBER 2015)
1. The Contractor shall not employ or contract with any individual or entity (hereinafter collectively referred to as “person”) to provide items or services that will be included in invoices submitted to the Government under this contract if such person is listed on the Department of Health and Human Services (HHS) Office of the Inspector General (OIG) List of Excluded Individuals and Entities (LEIE) or the TRICARE Sanctioned Provider List. The Government is legally prohibited from paying for provision of items or services by such persons. The prohibition extends to services beyond direct patient care, such as services of persons in executive or leadership roles and administrative and management services, whether or not such services are billed separately. The LEIE may be found at http://oig.hhs.gov/fraud/exclusions.asp, and the TRICARE Sanctioned Provider list at http://www.health.mil/Military-Health-Topics/Access-Cost-Quality-and-Safety/Quality-And-Safety-of-Healthcare/Program-Integrity/Sanctioned-Providers. The LEIE and TRICARE Sanctioned Provider List are hereinafter collectively referred to as “the Lists.”
2. Prior to start of contract performance, the Contractor shall (a) query the Lists to determine whether the name of any person the Contractor employs or contracts with to provide services or items for which payment may be made under this contract appears on the Lists, and (b) certify to the Contracting Officer that the Contractor has queried the Lists and no such names appear on either of the Lists.
3. During performance of the contract, and prior to persons other than those whose names were queried in accordance with paragraph 2, above, (hereinafter “new persons”) providing services or items under the contract, the Contractor shall (a) query the Lists as in paragraph 2, and (b) certify to the Contracting Officer that the names of such new persons do not appear on either of the Lists.
4. The Contractor is advised that during performance of the contract, MTF personnel will perform a recurrent recheck of the names of contractor personnel working in the MTF against the Lists, as specified in OTSG/MEDCOM Policy Memo 15-037. The Government will notify the Contractor in the event any contractor personnel working in the MTF appear on either of the Lists.
5. Should any person providing items or services under the contract appear on either of the Lists at any time during contract performance, the Contractor shall (a) in cases where the Contractor identified the person, notify the Contracting Officer, and (b) promptly remove that person from the contract.
6. Violation of any aspect of the above paragraphs shall be considered a material breach of the contract and may result in termination of the contract.
7. The Contractor is further advised that, in accordance with Civil Monetary Penalties Law [CMP] (codified at 42 USC § 1320a-7a):
a. There are steep civil monetary penalties associated with billing the Government for providing items or services by a person on either of the Lists, and with failing to return to the Government any overpayments received for provision of such items or services.
b. Billing under the contract for provision of items or services by a person on either List may also result in exclusion of the person that employs or contracts with such person.
8. HHS OIG has issued a Special Advisory Bulletin on the Effect of Exclusion from Participation in Federal Health Care Programs with additional information on the CMP. The Special Advisory Bulletin may be found at http://oig.hhs.gov/exclusions/files/sab-05092013.pdf.
i. NON-DEFENSE HEALTH AGENCY (NON-DHA) HEALTH INSURANCE PORTABILITY
AND ACCOUNTABILITY ACT (HIPAA) BUSINESS ASSOCIATE AGREEMENT (BAA) (7 JULY 2014)
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 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 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 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 [insert name of Business Associate signatory to this BAA].
—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 [insert name of MHS component signatory to this BAA].
—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 Business Associate shall contact the Covered Entity for guidance when the incident is not an HHS Breach.
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 Covered Entity and to the US Computer Emergency Readiness Team (US CERT) -the other parties as deemed appropriate by the Covered Entity. 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 -Covered Entity and the applicable Service-Level Privacy Office, if requested by either. Business Associate questions about US-CERT reporting shall be directed to the Covered Entity or Service-Level Privacy Office, not the US-CERT office.
The additional US Army and the US Army Medical Command (MEDCOM) reporting requirements are addressed in the PII Breach Reporting and Notification Policy. The latest version of this policy can be obtained from the Covered Entity or the MEDCOM Privacy Act/Freedom of Information Act (FOIA) Office at: usarmy.jbsa.medcom.list.medcom-foia-users@mail.mil . 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 Covered Entity as soon as possible if it believes that “single event” breach response is appropriate; the Covered Entity 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 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 Covered Entity 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 Report. The Business Associate is responsible for reporting all information needed by the Covered Entity 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 Covered Entity (or the Service-Level Privacy Office, which will consult with the DHA 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. 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 forth here. 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. Upon mutual agreement of the Covered Entity and the Business Associate that return or destruction of PHI is infeasible, the Business Associate shall extend the protections of the Agreement 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 Business Associate maintains such PHI.
VII. Miscellaneous
(a) Survival. The obligations of Business Associate under the “Effect of Termination” provision of this BAA shall survive the termination of the Agreement.
(b) Interpretation. Any ambiguity in the Agreement shall be resolved in favor of a meaning that permits the Covered Entity and the Business Associate to comply with the HIPAA Rules and the DoD HIPAA Rules.
j. Invoicing, Receipt, Acceptance and Property Transfer (iRAPT) – formerly known as WAWF
k. TOBACCO FREE MEDICAL CAMPUS (TFMC)
In accordance with Army Regulation 600-63, paragraph 7-3, 14 April 2015; Operations Order 15-48 (Army Medical Command (MEDCOM) Tobacco Free Living – USAMEDCOM), 8 May 2015; and any Operations Order, regulation or other instruction implementing, defining or otherwise addressing the Tobacco Free Medical Campus (TFMC) on any military installation or DoD-controlled location, Contractor personnel are prohibited from using any tobacco product on or within any TFMC while performing under this contract. TFMCs are established at each installation or DoD-controlled location and include: (1) any property or non-residential building that is operated, maintained or assigned to support medical activities, including but not limited to, hospitals, medical laboratories, outpatient clinics (including medical, dental, and veterinary facilities), or aid stations operating for the primary purpose of delivering medical care and services for DOD eligible beneficiaries and /or meeting the mission of the Army Medical Command; (2) all other facilities in which medical activities or administration take place, to include HQ MEDCOM and Defense Health Headquarters; (3) all internal roadways, sidewalks and parking…
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 .