Best Practices When Using Encryption
Full information on Encryption requirements at CUMC can be found within the IT Policies, Procedures and Guidelines area of our website. The information and instructions here are for general use, anyone connecting to Medical Center resources must be aware of all requirements and be sure that they are in compliance.
In compliance with the Columbia University Data Classification Policy you are required to protect any sensitive data with encryption. Methods for file sharing and transfer include:
- Sharing files using a CUMC IT managed network drive. Many departments at CUMC use folders stored on a P: drive for shared access to approved employees.
- Sharing files via email. Remember that University Policy prohibits the use of personal or non-institutional email addresses for University business purposes.
- Sharing files through SharePoint, which allows approved employees granulated access to different areas of a SharePoint site including document libraries.
- Transporting files with hardware encrypted USB keys. These are often the easiest choice for lectures, conferences, and meetings outside of CUMC when you cannot access your normal network resources. However you must comply with all requirements for Data Use and Storage as well as those for Mobile Peripherals.
- If you use Symantec Endpoint Encryption (SEE - formerly called GuardianEdge) please see links in the left navigation column of this page for specific information on using Symantec.
Additional Guidelines and Requirements
- If you are traveling, it is recommended that you email the file to your Columbia.edu account in case you lose your USB key or it gets damaged during travel. Be sure to follow Email Use requirements.
- Files that contain sensitive data that you are emailing to an address outside of Columbia must be encrypted. If you have a CUMC Exchange account please use the Secure Email Gateway; computers with Symantec Endpoint Encryption installed can encrypt files before attaching. Otherwise see Encryption Recommendations for individual file encryption programs.
- The security of data is the responsibility of the owner—YOU. This refers to files that are shared on network resources, transferred to portable drives, or transmitted via email. Please exercise caution and follow all encryption requirements.
Identifying PHI and PII
Electronic forms of Protected Health Information (PHI) and Personally Identifiable Information (PII) must be protected as per federal regulations, and must be encrypted as per the University's Data Classification, Registration and Protection of Systems, and Registration and Protection of Endpoints policies. To properly determine what PHI and PII are, we have summarized information from the U.S. Department of Health and Human Services' Guidance Regarding Methods for De-Identification of PHI and Summary of the HIPAA Privacy Rule below.
What is PHI?
PHI 18 Identifiers
Any information transmitted or maintained in any form (i.e. by electronic means, on paper or through oral communication) that relates to the past, present or future physical or mental health or condition of an individual, the provision of health care to an individual or the past, present or future payment for health care and (a) identifies the individual or (b) with respect to which there is a reasonable basis to believe that the information can be used to identify the individual. Identifying characteristics of the identifier are listed below:
LIMITED DATA SET (which is PHI)
- All geographic subdivisions smaller than a state, including street address, city, county, precinct, zip code and their equivalent geocodes, except for the initial three digits of a zip code
- All elements of dates (except year) directly relating to an individual, including birth date, admission date, discharge date, date of death and all ages over 89 and all elements of dates (including year) indicative of such age, except for ages and elements aggregated into a single category of age 90 or older
- Telephone numbers
- Fax numbers
- Email addresses
- Social security numbers
- Medical record numbers
- Health plan beneficiary numbers
- Account numbers
- Certificate/license numbers
- Vehicle identifiers and serial numbers, including license plate numbers
- Device identifiers and serial numbers
- Web Universal Resource Locators (URLs)
- Internet Protocol (IP) address numbers
- Biometric identifiers, including finger prints and voice prints
- Full face photographic images or any other comparable images
- Any other unique identifying numbers, characteristics or codes (other than unique codes assigned to code the data).
Limited data set is protected health information that excludes the following direct identifiers of the individual or of relatives, employers, or household members of the individual: (1) names; (2) postal address information, other than town or city, State, and zip code; (3) telephone numbers; (4) fax numbers; (5) email addresses; (6) social security numbers; (7) medical record numbers; (8) health plan beneficiary numbers; (9) account numbers; (10) certificate/license plate numbers: (11) vehicle identifiers and serial numbers; (12) device identifiers and serial numbers. (13) web URLs; (14) Internet Protocol (IP) address numbers; (15) biometric identifiers, including fingerprints and voiceprints; and (16) full-face photographic images and any comparable images.
Importantly, unlike de-identified data, protected health information in limited data sets may include the following: city, state and zip codes; all elements of dates (such as admission and discharge dates); and unique codes or identifiers not listed as direct identifiers.
What is PII?
Any information about an individual that could cause harm to such individual, such as medical, financial, employment or criminal records or other information, together with information that can be used to identify or trace an individual's identity, including any other personal information that is linked or linkable to that individual. Examples include social security numbers, driver's license numbers, and credit card numbers.
| TOP |