11_TCRS_Sect_J_Atch_J-1_DHA_PEPR_AARF.pdf

PDF 7 MB Posted

Attached to
TRICARE Claims Review Services
Solicitation number
HT9402-17-R-0002
Issued by

About this file

Section J Attachment J-1

View the file

Other files

File Type Posted
Amendment_8.pdf PDF
RFP_Q&As_01.06.2017.docx DOCX document
Amendment_7.pdf PDF
RFP_Q&As_12.27.16.docx DOCX document
HT9402-17-R-0002_Amendment_000006.pdf PDF
HT9402-17-R-0002_Amendment_000005.pdf PDF
HT9402-17-R-0002_Amendment_000004.pdf PDF
HT9402-17-R-0002_Amendment_000003.pdf PDF
26_TCRS_Section_J_Exhibit_A_CDRLS.pdf PDF
2_TCRS_SF_30_Section_B_11-16-2016.pdf PDF
20_TCRS_Sec_J_Atch_J-10_DHA_Comp_Rvw_Gdlns.pdf PDF
38_TCRS_Sec_L_Exhibit_L-10_Draft_QASP_11-7.16.pdf PDF
35_TCRS_Sec_L_Exhib_L-7_Price_Prop_Tmplt_4-4-16.xlsx XLSX spreadsheet
13_TCRS_Sec_J_Atch_J-3_Smpl_Init_Rnds_Test_Rpt.pdf PDF
5_TCRS_Section_E_11-10-16.pdf PDF
39_TCRS_Section_M_11_10_16.pdf PDF
31_TCRS_Sec_L_Exhb_L-3_Samp_Team_Part_Subcntr_11-7-16.pdf PDF
29_TCRS_Sec_L_Exhibit_L-1_Sample_Client_Auth_Llt_11.7.16.pdf PDF
2_TCRS_Section_B_CLIN_Descriptions_11-4-2016.pdf PDF
30_TCRS_Sec_L_Exhibit_L-2_Past_Performance_Questionnaire_8-19-15.doc DOC document
4_TCRS_Section_D_11-10-16.pdf PDF
21_TCRS_Sec_J_Atch_J-13_Wage_Determinations.pdf PDF
8_TCRS_Section_H_11-10-16.pdf PDF
9_TCRS_Section_I_11-10-16.pdf PDF
18_TCRS_Sec_J_Atch_J-8_Example_of_TADR.pdf PDF
14_TCRS_Sec_J_Atch_J-4_Smpl_Final_Rdns_Test_Rpt.pdf PDF
28_TCRS_Section_L__11_15_16.pdf PDF
37_TCRS_Sec_L_Exhibit_L-9_Hist_TOP_Data_11-7-16.pdf PDF
7_TCRS_Section_G_11-10-16.pdf PDF
27_TCRS_Section_K_11-10-16.pdf PDF
6_TCRS_SECTION_F_11-10-16.pdf PDF
34_TCRS_Sec_L_Exhibit_L-6_TCRS_Hist_Wrkld_Rprt_11-7-16.pdf PDF
3_TCRS_Section_C_as_of_11-10-16.pdf PDF
22_TCRS_Sec_J_Atch_J-14_Cnt_Non_Discl_Agrmnt.pdf PDF
12_TCRS_Sec_J_Atch_J-2_Readiness_Test_Findings.pdf PDF
32_TCRS_Sec_L_Exh_L-4_Grnte_Agmnt_for_Corp_Grntor.pdf PDF
23_TCRS_Sec_J_Atch_J-15_ADP_Req CAC_Instruc.pdf PDF
25_TCRS_Sec_J_Atch_J-17_PCDIS_User_Guide.pdf PDF
17_TCRS_Sec_J_Atch_J-7_ADDP_MDR_Data_File.pdf PDF
19_TCRS_Sec_J_Atch_J-9_Example_of_ADDR.pdf PDF
24_TCRS_Sec_J_Atch_J-16_TA_User_Guide.pdf PDF
10_TCRS_Section_J_List_of_Attachments_11_10_16.pdf PDF
33_TCRS_Sec_L_Exhibit_L-5_Cross_Ref_Table_11-7-16.pdf PDF
15_TCRS_Sec_J_Atch_J-5_DHA_Sampling_Meth.pdf PDF
16_TCRS_Sec-J__J-6_Clm_Review_Schl.pdf PDF
36_TCRS_Sec_L_Exhibit_L-8_TCRS_Hist_Rebut__Rprt_11-7-16.pdf PDF
Responses_to_Questions.pdf PDF
Amendment_000001.pdf PDF
40_TCRS_Section_M_10_3_16.pdf PDF
31_TCRS_Section_L_Exhibit_L-2_Past_Performance_Questionnaire_8-19-15.pdf PDF
Show 40 more

Latest 50 of 87 listed here. See the rest on GovTribe.

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

DHA Form 834 (7/28/2015) All previous versions are obsolete. FOR OFFICIAL USE ONLY

PEPR Account Activation Request Form See Pages 28-30 for Form Instructions and Guidance.

Upon Completion Email to SDD Access: DHA.SDDAccess@mail.mil DCS Users - Upon Completion Email to PAT&IS: dcs@dha.mil

1. System Access (Please check the system for which you have mission/contract related access requirement)

PCDIS & PRDM - Purchased Care Detail Information System & Provider Reporting Data Mart

DCS – Duplicate Claims System

PEPR Satellite Systems – Specify Below

CBM - Consolidated Bad Master

CK - Claims Check

MH - Mental Health

QRDF - Quick Response Data File

RF - Reference File

TA - TED Auditing

2. Employment Category (Please check the category that applies) Government Employee, Uniformed Service Member, Military, or Civil Service working within/for DoD MHS

Contractor working within the DoD Military Health System

Government Employee, Uniformed Service Member, Military, or Civil Service working for other agency or directorate not a part of the DoD Military Health System

Contractor working for Government Agency, not a part of the DoD Military Health System

Other (Please describe) ___________________________________________________________

3. Applicant/Requestor Information

Rank/GS Level/Title:

Name (Last, First, MI):

Complete Office Mailing Address:

Sponsoring Organization Name: (Not Project Name)

If Contractor, Employer Name

Commercial Telephone Number:

DSN:

Email:

Account Validation PIN:

Enter a 4 digit numeric PIN that you will use to validate your identity for account administration purposes.

Applicant/Requestor Digital Signature:________________________________________________________________

4. Action

Check action requested: NEW CHANGE DELETE OTHER _________________________

If you have a User ID, please enter it here: _________________ (If your account has expired, enter your last user ID)

Requested Access (Required for DCS users only): READ ONLY READ/WRITE (supervisor must complete 4.A., below)

Requesting Access to following contractor region number(s)*:______________________________________________ mailto:DHA.SDDAccess@mail.mil mailto:dcs@dha.mil kjohnson Stamp

PEPR Account Activation Request Form

*If access to multiple contractor regions is required, all region contractor numbers must be specified.

4. A. Special Permissions Data for READ/WRITE Users (To be completed by requestor’s supervisor)

Permission to create User Defined Codes? (Requires Prime Contractor approval): YES NO

Permission to unarchive sets? (Requires Prime Contractor approval): YES NO

Supervisor Signature: ______________________________________ Phone#:______________________

Prime Contractor Signature: ______________________________________ Phone#:______________________

5. SDD Rules of Behavior

1. Have you READ the SDD Rules of Behavior appended at the end of this document? YES NO

2. Do you ACCEPT the terms set forth in the SDD Rules of Behavior? YES NO

6. DOD Cyber Awareness Challenge Training

1. Have you successfully completed DoD Cyber Awareness Challenge Training? YES NO

2. Have you signed and emailed the DoD Cyber Awareness Challenge Certificate to SDD? YES NO

6. A. PCDIS Training (Required for all users requesting access to PCDIS) Enter date (mm/dd/yyyy).

Date: ________________ LIVE NO

7. Data Sharing Agreement (DSA) for Contractor If you are an MHS Contractor and/or non-MHS Employee, please provide the following information:

Employer Name:

Project description requiring this access:

What is the DSA # that exists for this project?

Project period of performance:

8. User Security Clearance Level (mark appropriate level):

ADP II/NACLC Notes: 1. A minimum of ADP Level II is required.

2. The use of SECRET is authorized if the requestor’s clearance has been active within 2 years of application date.

ADP I

Other (specify) Type __________________ Date _________________

If SECRET, provide: Date of Birth: __________________ Place of Birth: ____________________________

9. DHA PEPR Account Applicant Signature (All Applicants/Users must read and sign) By signing below, I am acknowledging that (1) all statements made on this form are true and correct; and (2) I am only authorized to use DHA PEPR Systems as designated above for my current position/duty and agree to relinquish my PEPR accounts to the SDD Program Executive Office upon departure from my current position/duty. I understand and accept that my use of the system may be monitored as part of managing the system, protecting against unauthorized access and verifying security problems. I further acknowledge that substantial civil and criminal penalties and/or administrative sanctions may be levied against those who violate the provisions of the Privacy Act of 1974 and/or the Health Insurance Portability and Accountability Act (HIPAA) of 1996.

Signature _________________________________________________ Date ________________________

10. Use of Mobile Computing Equipment Mobile computing equipment (Laptop computer, external hard drive, CDs/DVDs, floppy disks, PDA, cell phone, or other movable media) WILL BE USED to connect to this SDD product.

Certification on Attachment B MUST BE COMPLETED.

Mobile computing equipment will not be used to connect to this SDD product.

11. Commander, Supervisor, or Security Officer Certification of Citizenship

By signing below, I am certifying that _______________________ (applicant) is a U.S. Citizen and has a mission essential or contract-driven requirement to access PEPR, and that the DSA referenced, if any, is applicable. I further acknowledge that substantial criminal penalties including fines and imprisonment, and/or administrative sanctions may be levied against those who violate the provisions of the Privacy Act of 1974 and/or HIPAA. I shall notify the SDD Program Executive Office upon departure of this applicant from their current position/duty or when access is no longer required.

Commander/Supervisor/Security Officer Name

Title or Position

Organization, Office, Company

Office Mailing Address

Email Address

Commercial Telephone

DSN

Verification of Need to Know: I certify that this user requires access as requested. YES NO

Signature _________________________________________________ Date _________________________

12. Government Sponsor

Sponsoring Organization Name

Commander / Supervisor / Sponsor Name (Last, First, MI)

Title

Office Mailing Address

Email Address

Commercial Telephone

DSN

Required for DCS and TA users only

Access Level Approved READ ONLY READ/WRITE R/W/ADMIN

Required for DCS users only

Unarchive Sets? YES NO

Create User Defined Codes? YES NO

Contractor Region Numbers Granted

Government Sponsor Signature: _____________________________________ Date _____________________

13. BOXI/BCS Application and Level of Access – To be completed by Government Sponsor POC or Supervisor

The official duties of this individual require the following BOXI/BCS application and level of access (select one of the following):

Application Access: User requires access to BOXI/BCS Application (Not applicable for DCS or TA Applications)

YES NO

Level of Access

Viewer: User can access only predefined reports published to a public folder. User will not be able to create ad hoc reports.

Reporter: User can access predefined reports, create ad hoc reports, and save to personal folders.

Publisher: User can access predefined reports, create ad hoc reports, save to personal and public folders. This access will require approval from PEPR Functional Sponsor and SDD PO Approving Authority.

Government Sponsor POC or Supervisor Signature: ____________________________________Date _________

SDD PO Approving Authority Signature: _____________________________________________ Date ________

(Required for Publisher access only)

14. Protected Health Information Access – To be completed by Government Sponsor POC or Supervisor

The official duties of this individual require access to patient identifying data? YES NO

If YES, please complete Attachment A.

Government Sponsor POC or Supervisor Signature: _________________________________ Date _________

DO NOT WRITE BELOW THIS BOX

15. SDD Certification (For SDD use only)

Form EDIPI PIN RoB DoD IA Trng AppSigned CertSigned SponSigned PHI/PII SDDAccess______

I certify that SDD requirements have been validated. Specified access is recommended.

SDD PO Approving Authority Name: ____________________________________

Signature _________________________________________________ Date _______________________

Attachment A

Justification for Access to Protected Health Information (PHI)

Generally speaking, only healthcare providers involved in the treatment of patients are allowed access to patient-identifying data regarding patients under their care. Such access could also extend to healthcare managers and administrative support personnel with specific, defined roles regarding paying or receiving reimbursement on medical claims and essential activities in support of health care operations. The use or disclosure of protected health information outside these parameters and without the patient’s consent may violate the Privacy Act of 1974 and/or the Health Insurance Portability and Accountability Act of 1996

(HIPAA). A more detailed description regarding the required protection of individually identifiable data is available at http://www.tricare.mil/tma/privacy/hipaa.aspx.

Please identify your requirements for access to patient identifiable data.

Privacy Act

Some data are protected under the provisions of the Privacy Act of 1974. The data contains patient and provider identity information and thus requires safeguards from unauthorized access and use. I agree to comply with the

Privacy Act of 1974 and to be responsible for the use of this data to properly safeguard patient and provider identifying data in accordance with the 30 Oct 2001 OASD (HA) memorandum signed by Major General

Randolph, Deputy Executive Director TMA, subject “Supplemental Guidance for the Management and Control of Patient Sensitive/Medical Record Information in the Military Health System.” In addition, I acknowledge that

I may be subject to civil suit under the Privacy Act or 1974 for damages which occur as a result of willful or intentional actions which violate an individual’s rights under the Privacy Act of 1974.

PHI

I accept responsibility for the PHI data in PEPR that is in my possession and will ensure that all reasonable efforts are made in order to protect the data from unauthorized access and misuse.

HIPAA

I acknowledge that under HIPAA (P.L. 104-191), Congress has established criminal penalties for knowingly violating patient privacy. Criminal penalties are up to $50,000 and one year in prison for obtaining or disclosing protected health information; up to $100,000 and up to five years in prison for obtaining protected health information under “false pretenses”; and up to $250,000 and up to ten years in prison for obtaining or disclosing protected health information with the intent to sell, transfer or use it for commercial advantage, personal gain or malicious harm.

User Signature __________________________________________________________Date _____________________

Printed Name ___________________________________________________ http://www.tricare.mil/tma/privacy/hipaa.aspx

Attachment B Encryption of Sensitive Unclassified Data at Rest on Mobile

Computing Devices and Removable Storage Media DoD Policy Memorandum, “Encryption of Sensitive Unclassified Data at Rest on Mobile Computing Devices and Removable Storage Media”, July 3, References (a) DoDI 8500.2, “Information Assurance (IA) Implementation,” February 6. 2003, (b) DoDD 8100.2, “Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG),” April 14, 2004, as supplemented by ASD Nil/DoD CIO memorandum, same subject, June 2, 2006, (c) DoD Policy Memorandum, “Department of Defense Guidance on Protecting Personally Identifiable Information (P11),” August 18, 2006, and (d) DoD Policy Memorandum, “Protection of Sensitive DoD Data at Rest on Portable Computing Devices,” April 18, 2006 require that:

(1) All unclassified DoD data at rest that has not been approved for public release and is stored on mobile computing devices such as laptops and personal digital assistants (PDAs), or removable storage media such as thumb drives and compact discs, shall be treated as sensitive data and encrypted using commercially available encryption technology. Minimally, the cryptography shall be National Institute of Standards and Technology (NIST) Federal Information Processing Standard 140-2 (FIPS 140-2) compliant and a mechanism shall be established to ensure encrypted data can be recovered in the event the primary encryption system fails or to support other mission or regulatory requirements. DoD information that has been approved for public release does not require encryption.

(2) The requirement to encrypt sensitive unclassified data at rest on mobile computing devices and removable storage media is in addition to the management and access controls for all computing devices specified in references (a) through (c).

Handling and Storage

During travel, laptops and PDAs must be hand carried and never checked as baggage. If possible, carry diskettes or removable hard drives separate from the laptop.

If a laptop or PDA is stored in a hotel locker room, it must be kept out of plain view. A laptop or PDA may not be left unattended in a vehicle.

Incident Handling

In the event of any suspicious activity, breach in security of the remote device, or upon the detection of a virus, Trojan Horse, or malware disconnect from the VPN connection, cease all operation on the device, and report the incident to the SDD IAM, Mr. Joseph Ibanez, joseph.g.ibanez.civ@mail.mil.

Please identify which mobile computing devices/removable storage media you will be using to access or obtain PHI (protected health information) from this SDD product: (check all that apply)

Laptop External Hard Drive CDs/DVDs Floppy Disks

PDA Cell Phone Other

If other, please describe:

User Certification: I understand the requirement for encryption of sensitive unclassified data at rest (in particular, PHI) on mobile computing devices and removable storage media. I certify that a data at rest encryption product, meeting the DOD specifications has been installed and is operating on any such mobile computing devices that I will use to access data from this SDD product. Further, I certify that I will ensure that this data at rest encryption product shall be maintained at the most recent version and shall be kept updated according to manufacturers’ latest available patches, service packs or other product updates. Further, I will keep this product installed and operational as long as my SDD product account is active.

User Signature ______________________________________________Date ________________________

User Printed Name___________________________________________

Information Assurance/Information Security Officer Certification: I certify that I have personal knowledge of the installation and proper operation of data at rest encryption product on the above named user’s computer. I will ensure that required updates are applied as available.

Make and model of mobile computing device(s):

Make Model Serial Number

IA/ISO Signature ______________________________________________Date ________________________

IA/ISO Printed Name___________________________________________

IA/ISO Email Address__________________________________________Phone ( ) __________________

Attachment C Solutions Delivery Division (SDD)

Rules of Behavior

Instructions and Guidance for

PEPR Account Activation Request Form

1. System Access. Select one or more PEPR tools you wish to access. If you request access for PCDIS and later need access to HA/TA or PEPR Satellite Reports a separate PEPR Account Activation Request Form is required at that time.

Overview of the PEPR Systems

CBM CBM (Consolidated Bad Master) allows the Government to monitor and report on TED records that have validity or relational edit errors and have not been fully corrected by the contractor. CBMprovides the most current information on outstanding TED record by maintaining and reporting the outstanding claims with missing or invalid information [System contains Personal Health Information (PHI)]

CK CK (Claim Check) produces monthly reports from the netted TED Master de-duped files identifying add-back and denial records by state and region in order to determine the total amounts saved as a result of reconciling duplicate claims.

CRDM CRDM (Common Reporting Data Mart) uses the Purchased Care Data Warehouse (PCDW) to extracts the necessary subset of data, performing derivations where needed to provide the various downstream applications with a complete set of data.

DCS The DHA Duplicate Claims System (DCS) was developed by the DHA to automate the resolution of duplicate claim payments. The system facilitates the identification of actually duplicate claim payments, the initiation and tracking of recoupments, and the removal of duplicate records from the Health Care Record (HCSRs) or TRICARE Encounter Data (TED) database. The system also generates operational and management reports.

MH MH (Mental Health) calculates average charge per day for inpatient mental health diagnoses for specified high volume providers, and compares it to similar data for a base period to determine amount of change.

PCDIS &

PRDM

PCDIS (Purchased Care Detail Information System) functions as a “search window” into the DHA Purchased Care Data Warehouse (PCDW). This data includes all HCSR and TED claims for care received outside MTFs by DHA beneficiaries, as well as active duty Supplemental Care, DHA Europe, and DHA Prime Remote. With PCDIS, you can:

Use the online retrieval paths to view summary and detail data contained in Health Care Service Records (HCSR) and TED claims for both institutional (i.e., hospital) and non-institutional (i.e., professional service, provider, medical group care)

Run pre-formatted and ad-hoc reports from within the PCDIS web-enabled application

QRDF QRDF (Quick Response Data File) produces “as-requested” health record information products by beneficiary or provider from TED data sources. The information can be acquired for a time period from FY 1985 to the present date. (System contains PHI)

RF RF (Reference Files) used for coding or classification purposes in analysis and event reporting. Reference Files maintained by PEPR include Defense Information Medical System (DMIS), Domestic and Foreign Zip Codes (CAD), Zip Code Exceptions, Contract Region File (CRF), Procedure Codes (CPT-4 and HCPCS), Diagnosis and Operation/Non-Surgical Procedure Codes (ICD-9-CM), Hospital Departments, Do Not Load/ Do Not Pay (Procedure Code), and General Reference Data.

TA TA (TED Auditing) provides a mechanism for the Claims Audit Review Services (CARS) contractor and Defense Health Agency Activity (DHA) to track and monitor the claim-processing performance of Managed Care Support Contractor (MCSC), Managed Care Support Services (MCSS) and TRICARE Dual Eligibility Fiscal Intermediary (TDEFIC) contractors. Provides an audit trail with the appropriate error code, facilitates the input of detailed explanations for assessing errors and error amounts, and determines the contractor payment error and occurrence error performance standard.

2. Employment Category. Check category that applies.

3. Applicant/Requestor Information. Please fill in all applicable fields. You must select a 4-digit Account Validation PIN. It may be any 4-digit number that you will remember if needed to verify your identity for account administration purposes (i.e. password reset). For instance, you may use the last 4-digits of your social security number or month and day of birth, etc.

4. Password Action/Access Authorization Requested. Check to indicate whether this is a request for a new PEPR user account or an account or password change, account deletion or reactivation. If you have a user ID, please provide it. If your account has expired, please provide your last user ID if known.

4.A. Special Permissions Data for Read/Write Users (Required for only DCS users). Select the various special permissions required for your mission or contract related work. These special permissions must be approved by your supervisor and prime contractor.

5. SDD Rules of Behavior. The SDD Rules of Behavior is appended to the end of this document for your review and acceptance to the terms and conditions set forth by SDD Program Executive Office.

Instructions PEPR AARF

6.A. DoD Cyber Awareness Challenge Training. DoDD 8570.1 “Information Assurance Training, Certification, and Workforce Management”, August 15, 2004 requires that information system users complete Cyber Awareness Challenge Training on an annual basis. In accordance with this directive, the SDD Program Executive Office must have a copy of your DoD Cyber Awareness Challenge Certificate on file.

If you have not completed online Cyber Awareness Challenge Training in the past year, you will need to take the training, complete the test, download the form, sign it and send it via fax to SDD Access at 866-551-1249 or email at DHA.SDDAccess@mail.mil. The DoD Information Assurance training can be accessed on the Defense Information Systems Agency’s (DISA) website: http://iase.disa.mil/eta/online-catalog.html. Select Cyber Awareness Challenge.

6.B. Product Training. The SDD Program Executive Office (PEO) requires that users of PCDIS complete either classroom or web-based training (WBT). The WBT training and tests are located at the MHS Learn website:

https://mhslearn.csd.disa.mil. Select “MHS Staff Training” to log in. Once logged in, enter “PCDIS” under Search Catalog. Select “SDD- (PCDIS) Purchase Care Detail Information System” to begin training. Once complete, enter the date of course completion or scheduled date (in the case of live training) in mm/dd/yyyy format and the type of training (live or web-based training (WBT), as appropriate, on Page 1 of this form.

7. Data Sharing Agreement (DSA) Number. Non-MHS personnel (generally other DoD employees) and/or contractors working for the MHS/DoD requiring access to PEPR data are required to have a current Data Sharing Agreement on file with the DHA Privacy and Civil Liberties Office. Please include PEPR and BCS/BOXI in the Project Title field of your Data Sharing Agreement Application (DSAA). BCS/BOXI is a SDD application that provides reporting and analytical services to the user communities of the Patient Encounter Processing and Reporting (PEPR) systems. For information pertaining to Data Sharing Agreements, please refer to the DHA Privacy and Civil Liberties Office website at http://www.tricare.mil/tma/privacy.

8. Security Clearance Level. All users of PEPR must have a minimum security clearance of ADP Level II. Users should contact their organization’s Security Officer or Personnel Office for assistance.

9. PEPR Account Applicant Signature and Electronic Data Interchange Personal Identifier (EDIPI). All applicants must digitally sign this form to verify the truth and accuracy of the information presented herein. In order to access PEPR, each applicant must have a valid CAC or PIV card. To verify your CAC/PIV is valid please digitally sign the form.

To receive current e-mail notifications on PEPR or BCS/BOXI updates, news, and/or system outages, please register at https://public.govdelivery.com/accounts/USMHSSDD/subscriber/new

10. Encryption of Sensitive Unclassified Data at Rest on Mobile Computing Devices and Removable Storage Media

Government and commercial vendors are required to provide data at rest encryption products for all mobile computing devices used to connect to SDD products. If a PEPR applicant will be connecting to PEPR using a mobile computing device, the PEPR applicant is required to complete and submit Attachment B.

Encryption Standards/Approved Software

A FIPS 140-2 approved file encryption algorithm (i.e., AES) must be used for full disk encryption to encrypt data on the remote device. Products that may be utilized include but are not limited to:

PGP – https://www.pgp.com/products/wholediskencryption/index.html

Mobile computing equipment users encrypt all temporary folders (e.g., C:\temp, C:\windows\temp, Temporary Internet Files, etc.) so that any temporary files created by programs are automatically encrypted.

DoD Components shall purchase data at rest encryption products through the DoD Enterprise Software Initiative (ESI), that substantially reduce the cost of common-use, commercial off-the-shelf software. For additional details, please log on to http://www.esi.mil and at http://iase.disa.mil.

11. Commander, Supervisor or Security Officer Certification of Citizenship. The requestor’s commander, supervisor, or security officer (the requestor’s employer) must certify that the requestor is a U.S. Citizen and has a mission or contract related requirement to access PEPR. All fields must be completed. Signature is required.

12. Government Sponsor. Please fill in all applicable fields.

13. Level of Access. The official duties of this individual require the following level of access (select one of the roles).

Publisher role should only be chosen if absolutely needed to perform work functions. This access will require approval from PEPR Functional Sponsor and SDD PO Approving Authority.

14. Protected Health Information Access. If the official duties of this individual require access to patient identifying data, please complete Attachment A: Justification for Access to Protected Health Information (PHI).

http://iase.disa.mil/eta/online-catalog.html https://mhslearn.csd.disa.mil/ http://www.tricare.mil/tma/privacy https://public.govdelivery.com/accounts/USMHSDHSS/subscriber/new https://www.pgp.com/products/wholediskencryption/index.html http://www.esi.mil/ http://iase.disa.mil/

Instructions PEPR AARF

Upon completion of Block 14, fax this form to SDD Access at 866-551-1249 or email to DHA.SDDAccess@mail.mil.

(Include Attachment A, if required.) If you are OCONUS and having trouble with the fax, please contact the Defense Health Agency (DHA) Global Service Center at servicecenter@dha.mil or 1-800-600-9332 for an alternate number.

15. SDD Certification. For SDD use only.

Attachment A. Justification for Access to Patient Identifiable Data.

All users require justification for access to the protected health information contained in PEPR.

User justification and signature is required.

Attachment B. Encryption of Sensitive Unclassified Data at Rest on Mobile Computing and Removable Storage Media

All users require justification for access to the protected health information contained in PEPR.

The form must be filled out by both the user and the user’s Information Assurance or Information Security Officer.

Attachment C. SDD Rules of Behavior

All users must read and ACCEPT the terms set forth in the SDD Rules of Behavior.

IMPORTANT: KEEP A COPY OF THIS FORM IN A SAFE PLACE FOR YOUR RECORDS AND FUTURE

REFERENCE.

3 ApplicantRequestor Information:
RankGS LevelTitle:
Name Last First MI:
Complete Office Mailing Address:
Sponsoring Organization Name Not Project Name:
If Contractor Employer Name:
Commercial Telephone Number:
DSN:
Email:
undefined_5:
undefined_6:
If you have a User ID please enter it here If your account has expired enter your last user ID:
Requesting Access to following contractor region numbers:
Phone:
Phone_2:
Date:
Employer Name:
Project description requiring this access:
What is the DSA that exists for this project:
Project period of performance:
ADP IINACLC:
ADP I:
Other specify Type:
Date_2:
If SECRET provide Date of Birth:
Place of Birth:
Date_3:
Mobile computing equipment Laptop computer external hard drive CDsDVDs floppy disks PDA cell phone or: Off
undefined_11: Off
By signing below I am certifying that:
CommanderSupervisorSecurity Officer Name:
Title or Position:
Organization Office Company:
Office Mailing Address:
Email Address:
Commercial Telephone:
DSN_2:
Date_4:
Sponsoring Organization Name:
Commander Supervisor Sponsor Name Last First MI:
Title:
Office Mailing Address_2:
Email Address_2:
Commercial Telephone_2:
DSN_3:
YES NOContractor Region Numbers Granted:
Date_5:
Date_6:
Date_7:
Date_8:
PHIPII SDDAccess:
Form: Off
EDIPI: Off
PIN: Off
RoB: Off
DoD IA Trng: Off
AppSigned: Off
CertSigned: Off
SponSigned: Off
undefined_18: Off
SDD PO Approving Authority Name:
Date_9:
Please identify your requirements for access to patient identifiable data 1:
Please identify your requirements for access to patient identifiable data 2:
Please identify your requirements for access to patient identifiable data 3:
Date_10:
Printed Name:
Laptop: Off
External Hard Drive: Off
CDsDVDs: Off
Floppy Disks: Off
undefined_19: Off
undefined_20: Off
Other:
undefined_21: Off
Date_11:
User Printed Name:
Make 1:
Make 2:
Model 1:
Model 2:
Serial Number 1:
Serial Number 2:
Date_12:
IAISO Printed Name:
IAISO Email Address:
Employee Name:
Title_2:
Organization Name and Address:
Telephone Number:
Email_2:
Check Box5: Off
Check Box6: Off
Check Box7: Off
Check Box8: Off
Check Box9: Off
Check Box10: Off
Check Box11: Off
Check Box12: Off
Check Box13: Off
Check Box14: Off
Check Box15: Off
Check Box16: Off
Check Box17: Off
Check Box18: Off
Text19:
Signature20_es_:signer:signature:
Signature21_es_:signer:signature:
Signature22_es_:signer:signature:
Signature23_es_:signer:signature:
Check Box24: Off
Check Box25: Off
Check Box26: Off
Check Box27: Off
READ ONLY READWRITE RWADMINRequired for DCS users only:
Signature28_es_:signer:signature:
Group29: Off
Signature30_es_:signer:signature:
Signature31_es_:signer:signature:
Signature32_es_:signer:signature:
Signature33_es_:signer:signature:
Signature34_es_:signer:signature:
Signature35_es_:signer:signature:
Signature36_es_:signer:signature:
Text37:
Signature38_es_:signer:signature:
Signature39_es_:signer:signature:
Signature40_es_:signer:signature:
Group3: Off
Group4: Off
Group5: Off
Group6: Off
Group7: Off
Group8: Off
Group9: Off
Group10: Off
Group11: Off
Group12: Off
Group13: Off
Group14: Off
Group15: Off
Group16: Off
Group17: Off
Text1:
Text2:
Text3:
Text4:

File details come from the government source that posted it. Updated .