Thank you for your commitment to always protecting patient privacy.
The Ohio State President’s Cabinet approved a new Protected Health Information (PHI) and HIPAA Policy. The policy unifies current PHI and HIPAA efforts in departments and programs across the university and the medical center, as well as builds efficiencies and increases compliance. If patient confidentiality is compromised, it must be promptly reported. More details about the policy, including FAQs and diagrams can be found below.
Relevant Diagrams
FAQs
-
What data classification is RHI considered?
The data classification of RHI is S4 (restricted) institutional data, which requires the highest levels of protections outlined in the Information Security Control Requirements (ISCR). Protections include, but are not limited to: Multifactor authentication, encryption, unique user accounts, minimum necessary access, access auditing, etc. Many departments using RHI will have IT support that is familiar with the requirements that are necessary for the use and storage of S4 (restricted) institutional data or will be able to seek assistance from one of the security teams associated with OSU or OSUWMC. Reach out to your IT contacts for consultation to ensure you are properly protecting RHI.
I don’t know whether my research data protection plan meets S4 requirements. Who do I ask for help?
Many departments using RHI will have IT support that is familiar with the requirements that are necessary for the use and storage of S4 data or will be able to seek assistance from one of the security teams associated with OSU or OSUWMC. Reach out to your IT contacts for consultation to ensure you are properly protecting RHI.
-
What is the HIPAA compliance plan or guidance that healthcare components must follow?
Covered components use the university's Compliance and Integrity established reporting templates to document their HIPAA compliance plans and annual reports. The covered components report their compliance efforts to the Covered Healthcare Component Committee (CHCC) at least annually, as well as to the covered components business unit leadership. Annually, the CHCC reports to the University Integrity Compliance Council (UICC) on the activities of the covered components and university service units.
Who do I contact if I have HIPAA-related questions?
If you work in the Wexner Medical Center, contact the Office of Compliance and Integrity at Compliance@osumc.edu.
If you are part of a Health Care Component and Service unit and have a question about HIPAA, identify your specific contact from this IT webpage.
If you want to report a privacy concern, visit the HIPAA Privacy and Security contacts webpage for details.
If you are not an employee of the Wexner Medical Center and don't know who to contact for questions about HIPAA, send your questions to Security@osu.edu.
Does this policy apply if a college unit is a business associate of an outside entity?
The BAA applies when the unit is acting as a business associate of an outside entity, to the extent the unit performs functions or services involving protected data.
-
Where do I report an incident involving PHI?
Many departments have designated IT, Information Security, and/or Privacy contacts through whom potential PHI incidents can be reported. Regardless of the initial reporting path, all potential PHI incidents are ultimately routed to the OSUWMC Privacy Office for review. If your department does not have an established reporting process, or if you are unsure where to report a concern, you can contact the OSUWMC Privacy Office directly at 614-293-7802 or privacyoffice@osumc.edu.
What kind of incident classifies an inappropriate disclosure of data? How do I know when I need to report an inappropriate disclosure?
An inappropriate disclosure occurs when information is shared with someone who is not authorized to receive it, or when it is used or disclosed in a way that is not permitted by policy, HIPAA, or other applicable requirements. A suspected inappropriate disclosure should be reported even if you are not yet sure whether it rises to the level of a breach.
An inappropriate disclosure of data occurred. I am unsure of whether the data is PHI or RHI and where to properly report the disclosure. What do I do?
This policy does not change your department’s existing reporting structure. Many departments have designated IT, Information Security, and/or Privacy contacts, and you should continue to work through those established channels for questions related to data disclosures, data classification, and incident reporting. If you are uncertain how data should be classified or whether an incident should be reported, reach out to your department contacts for guidance. Ultimately, potential incidents are routed to the appropriate response team, whether that is the OSUWMC Privacy Office or OTDI Security.
If you do not have an established contact or are unsure where to report a concern, please contact whichever office is most appropriate for your situation:
- OSUWMC Privacy Office: 614-293-7802 or PrivacyOffice@osumc.edu
- Office of Technology and Digital Innovation (OTDI) Security: 614-688-4357 (HELP) or Security@osu.edu
These teams work closely together and will ensure your concern is directed to the appropriate resources for review and response.
For incidents involving research data or concerns related to patient confidentiality within a research study, a Reportable New Information (RNI) submission in Huron may also be required. Additional information about RNI reporting requirements can be found on the Office of Responsible Research Practices website.
What happens if there is an unauthorized disclosure of PHI held by a service unit or their subcontractor?
Any actual or suspected unauthorized use or disclosure of sensitive information by a service unit or its subcontractors must be reported promptly to the OTDI Security or the Medical Center Privacy Office.
Noncompliance with university policies, contractual obligations, or HIPAA requirements may result in corrective actions ranging from education and remediation to recommendations for disciplinary action or contract termination. Each situation is reviewed individually and evaluated based on the specific facts and circumstances involved.
-
Why would a covered healthcare component decline to honor a HIPAA waiver?
Under the HIPAA regulations, disclosures of PHI for research purposes is permissive, not mandatory. An IRB's approval of an authorization, waiver, or alteration of authorization means that the applicable HIPAA criteria have been satisfied, but it does not necessarily require a covered health care component to disclose PHI. Data will be disclosed based on the minimum amount of information that is needed for the intended purpose. Covered health care components remain responsible for protecting PHI and ensuring compliance with HIPAA, institutional policies, and other applicable legal requirements. As a result, a covered component may decline or delay a disclosure if it identifies concerns regarding information security safeguards, the scope of the requested disclosure, compliance with applicable policies or laws, or other privacy and security considerations. Covered components will work with investigators and appropriate institutional offices to facilitate compliant access to PHI.
What are partial and full waivers of HIPAA authorization? How do they relate to the data that can be disclosed for research purposes?
Under the Privacy Rule, HIPAA research authorization is an individual's signed permission to allow a covered entity to use or disclose the individual's PHI that is described in the authorization for the purpose(s) and to the recipient(s) stated in the authorization:
- Information to be accessed, used, or disclosed
- Identification of those authorized to use/disclose
- Potential for re-disclosure; right to revoke
The requirement for an authorization may be waived (full or partial) or altered.
Partial Waiver of Authorization: Allows PHI access/retention for the purposes of identifying potential subjects. Information collected under partial waiver must be destroyed after recruitment is complete unless authorization or additional waiver/alteration is obtained.
Full Waiver of HIPAA Authorization: Allows PHI access/retention without authorization for the entire research study (collection and data analysis).
- The fact that the research is retrospective or that the data to be used will be created regardless of the research are not sufficient justifications for granting a full waiver under the regulations.
- In general, research studies involving prospective access/collection of PHI should include a plan to obtain authorization.
De-Identified data sets do not require HIPAA waivers. Investigators are encouraged to use de-identified data.
What is the role of the Privacy Board?
A Privacy Board is a committee established to review requests for a waiver or alteration of the authorization requirement for uses and disclosures of PHI in a particular research study. A Privacy Board may waive or alter all or part of the authorization requirements. Under the Privacy Rule, an IRB may serve as a Privacy Board. At The Ohio State University, the Privacy Board reviews requests for waivers or alterations of authorization in exempt research. ORRP facilitates the review process; no additional action by the investigator is necessary. The Institutional Review Board (IRB) serves as Privacy Boards for non-exempt research.
What is the role of the IRB?
All non-exempt research activities involving human subjects must be reviewed and approved by an Institutional Review Board (IRB).
The IRB reviews non-exempt human subjects research proposals to ensure risks have been minimized and assessed against the potential for benefit before human subjects participate in the research. The IRB also ensures, when required, that human subjects only volunteer to participate in research after providing legally effective informed consent.
Learn more information about exempt studies using PHI.
Does this policy change the way researchers can identify and recruit patients from Ohio State’s covered components?
No. Recruitment of participants from these sources is governed by IRB policy on recruitment and the OSUWMC HIPAA Research policy, both of which require partial waivers of HIPAA authorization and prohibit cold calling of potential research participants. IRB policy and OSUWMC policy prohibit cold calling of potential research participants. Before any contact occurs, the investigator must coordinate with the individual's clinician, who must grant permission for the outreach in accordance with OSUWMC HIPAA Research Policy. All recruitment communications (including phone scripts, emails, letters, text messages, and similar materials) must clearly indicate the connection between the clinician and the research team and IRB approval must be obtained prior to use of recruitment documents. The script must make it clear that the potential participant is being contacted because of their relationship with their treating physician or clinical provider, and that the clinician has authorized the researcher to reach out regarding the study.
See the IRB Policy on Recruitment and Research Recruitment Tip Sheet.
Why would a covered component require a university researcher to receive HIPAA training if the data they are receiving is RHI?
There are two reasons why a covered component may require a university researcher to complete HIPAA training prior to disclosing patient data for research:
- To ensure the researcher understands that the health information they receive is derived from a person whose information must be safeguarded and honored as private regardless of its classification as PHI or RHI.
- To provide additional assurance to the covered component, as steward of patient data, that privacy and confidentiality will be protected after disclosure to the researcher.
Who can de-identify patient data?
Under HIPAA, de-identification is the process of removing or altering identifiers so that the identity of individuals cannot be reasonably determined and re-identification is not possible.
At OSU certain groups, honest brokers, have authorization to de-identify data.
Data is considered de-identified by one of the following methods:
- Remove all of the 18 elements of PHI from a dataset and having no keys or identifiers that can link back to PHI or that are derived from PHI; or
- Obtain expert determination certifying that the statistical risk is miniscule that the data could be re-identified. Expert determination requires a qualified third party.
Researchers may de-identify datasets as described in 1), but the de-identification must be validated by Information Security and the process of de-identification must have IRB approval.
Researchers may not de-identify their own data. Contact the Privacy Office for additional information and support.
Can I store RHI in HIPAA approved systems?
Yes, you should store RHI in data systems that meet S4 requirements.
-
Research Health Information (PDF)
-
Which units are the designated healthcare components subject to HIPAA?
The university’s designated healthcare components can be found in The Hybrid Entity Designation Statement. (need website)
The university’s designated healthcare components can be found in The Hybrid Entity Designation Statement. The components are: The Ohio State University Wexner Medical Center (University Hospital, University Hospital – Pavilion, University Hospital – Rhodes Hall, University Hospital – Doan Hall, East Hospital, Richard M. Ross Heart Hospital, Harding Hospital, Dodd Rehabilitation Hospital, Ambulatory Clinics and Services); Arthur G. James Cancer Hospital and the Richard J. Solove Research Institute - Comprehensive Cancer Center; College of Dentistry; College of Optometry; Nisonger Center; OSU Health Plan; OSU Physicians Inc.; Wilce Student Health Center.
What is a service unit? Which Ohio State units are service units subject to HIPAA?
A university unit that creates, receives, maintains or transmits PHI on behalf of a healthcare component. The service unit is subject to HIPAA only as it is performing functions on behalf of a covered component.
Service Units:
- College of Medicine (including Government Resource Center)
- College of Nursing
- Office of Administration and Planning
- Office of Technology and Digital Innovation
- Office of Business and Finance
- Department of Internal Audit
- Office of the University Bursar
- University Risk Management
- Office of Human Resources
- Office of Innovation and Economic Development
- Civil Rights Compliance Office
- Office of Legal Affairs
- Office of University Compliance and Integrity
- University Office of Advancement
Updated: February 2025
Example: UniPrint is only subject to HIPAA when producing documents related to a covered component's treatment, payment or operations, but not when providing services to units for non-healthcare purposes.
What is a Covered Entity?
A Covered Entity includes the following types of organizations if they conduct certain types of transactions in electronic form: health plans, healthcare clearinghouses, and healthcare providers. HIPAA addresses Protected Health Information (PHI) that is created, received, maintained or transmitted by a Covered Entity.
What is OSU’s designation?
The Ohio State University (University) conducts both Covered and Non-Covered Functions and elects to be a Hybrid Entity under HIPAA. As a Hybrid Entity, the University is responsible for designating the Components that are Healthcare Components within the University.
What is a Hybrid Entity?
A Covered Entity that is a single legal entity and conducts both Covered and Non-Covered Functions may elect to be a Hybrid Entity. To be a Hybrid Entity, a Covered Entity must identify its components that perform Covered Functions and designate these components as Healthcare Components. HIPAA compliance obligations apply only to designated Healthcare Components; a Covered Entity that does not make the Hybrid Entity designation is subject to HIPAA in its entirety.
-
What are examples of use and disclosure under HIPAA?
Use: A hospital may use protected health information about an individual to provide healthcare to the individual and may consult with other healthcare providers about the individual's treatment.
Disclosure: A primary care provider may send a copy of an individual’s medical record to a specialist who needs the information to treat the individual.
Research-related disclosure: A covered component may disclose PHI pursuant to a HIPAA authorization or waiver for retrospective chart review.
What do we do to protect the privacy of a patient's medical information?
We believe that every piece of a patient's medical information is private and deserves protection. Long before there were HIPAA regulations, OSU developed policies to safeguard the confidentiality of patient medical records. In 1996, HIPAA brought broader reaching guidelines that added security to handling of electronic health records. Use of medical information at OSU undergoes regular ongoing inspection (or review) by privacy and information security units to assure a patient's confidentiality is constantly maintained.
I am a researcher who is also a clinician. How does the policy apply to me?
In your role as a workforce member of a covered component, you are subject to existing policies and procedures of the covered component (e.g. OSUWMC, College of Dentistry, College of Optometry, etc.).
If you are conducting research activities unrelated to your clinical role, you are acting as a non-covered component workforce. Generally, the PHI is contained in the electronic medical record. If the PHI is subsequently disclosed (released) from the EMR (as would occur with a request via the Honest Broker protocol), pursuant to a valid HIPAA research disclosure, such as a valid authorization, waiver, or alteration of authorization, PHI would be reclassified as Research Health Information (RHI). The Investigator is responsible for safeguarding the RHI to the S4 level of information security protections.
Learn more about the RHI policy and see FAQs.
Learn more about PHI and HIPAA policy.
PHI used in therapeutic trials (i.e., clinical treatment) is subject to all HIPAA protections, including safeguarding the information to the S4 level of security.

