HIPAA and Patient Information
How Veriframe protects patient information as a business associate.
Effective November 17, 2026 · Last updated November 17, 2026
Veriframe provides insurance eligibility and benefits verification to behavioral health practices. To do that work, we receive and use protected health information (“PHI”) on behalf of those practices. This page explains how we protect it. It is provided for information and does not replace the Business Associate Agreement (“BAA”) we sign with each practice.
1. Our role under HIPAA
Under the Health Insurance Portability and Accountability Act (“HIPAA”), the practices we work with are covered entities, and Veriframe is their business associate. That means we may use and disclose PHI only as our BAA with the practice allows and as HIPAA permits, and we are directly responsible for complying with the HIPAA Security Rule and the applicable parts of the Privacy Rule and Breach Notification Rule.
Patients’ rights over their health information, and how a practice uses and shares it, are described in that practice’s own Notice of Privacy Practices. Patients should contact their provider with questions or requests about their information.
2. Business Associate Agreements
We sign a BAA with every practice before we receive any PHI. The BAA sets out the permitted uses and disclosures of PHI, the safeguards we maintain, our obligations if an incident occurs, and what happens to PHI when the engagement ends. Any subcontractor that may access PHI to help us deliver our services must first agree in writing to the same restrictions and conditions that apply to us.
3. How we use and disclose PHI
We use and disclose PHI only to perform services for the practice, which include:
- Reviewing the practice’s upcoming schedule and patient insurance details
- Verifying eligibility, benefits, authorizations and network status with payers, their behavioral health administrators and their portals and phone lines
- Documenting verification results in the practice’s EHR or practice management system and flagging issues to the practice
- Quality review of our own work
We may also use or disclose PHI as required by law, or for our proper management and administration where the BAA and HIPAA allow. We follow the minimum necessary standard, limiting PHI to what is needed for the task. We never sell PHI and never use it for marketing.
4. How we protect PHI
Administrative safeguards. We maintain written HIPAA policies and procedures, conduct and update security risk assessments, designate a person responsible for privacy and security, and require every workforce member who may access PHI to complete HIPAA training and sign a confidentiality agreement before access is granted and to refresh that training regularly.
Access controls. Access to PHI is limited by role to the people who need it to perform the services. Wherever possible, we work directly inside the practice’s own systems using individual user accounts that the practice can monitor, restrict and revoke at any time. Access is removed promptly when it is no longer needed.
Technical safeguards. We use encrypted connections, strong passwords and multi-factor authentication where systems support it, and we keep PHI out of ordinary email, text messages and personal devices. Any working records we keep are limited to what the service requires and are protected with the same safeguards.
Physical safeguards. Workstations used to access PHI are secured, screen-locked when unattended, and not shared with people outside our workforce.
5. Incidents and breach notification
We investigate any suspected security incident involving PHI. If we discover a breach of unsecured PHI, we notify the affected practice without unreasonable delay and within the time required by the BAA and HIPAA, and we provide the information the practice needs to meet its own notification obligations. We also take steps to contain the incident and prevent it from happening again.
6. Patient rights requests
If a patient asks us to access, amend or receive an accounting of disclosures of their health information, we forward the request to the practice and support the practice in responding, as the BAA requires. We make our internal practices and records relating to PHI available to the U.S. Department of Health and Human Services when required to determine compliance.
7. When an engagement ends
When our services to a practice end, we return or destroy the PHI we hold for that practice where feasible, and practice-granted system access is closed. If returning or destroying PHI is not feasible, we continue to protect it under the BAA and limit any further use to the reasons that make return or destruction infeasible.
8. Sharing information with us safely
Please do not send PHI through our website forms or ordinary email. During onboarding, we agree with each practice on secure ways to share access and information, which usually means working inside the practice’s own EHR.
9. Questions
Practices that would like a copy of our BAA, or have questions about how we protect patient information, can contact our privacy and security team:
Veriframe LLC
New York, NY
founders@veriframehealth.com
561-400-5375