HIPAA & Compliance

Your patients’ data stays
in your systems. Full stop.

OcuPine Practice Services is built around a non-negotiable principle: we work inside your existing EHR and PMS — we never replicate, export, or store PHI on our infrastructure. Here’s exactly how we operate, documented for your compliance records.

Request a BAA
0
Patient records stored on OcuPine Practice Services infrastructure
Day 1
BAA executed before any onboarding work begins
60-day
Breach notification SLA (HIPAA maximum, honored strictly)

How OcuPine Practice Services handles protected health information

Our operational model is designed so that PHI never needs to leave your systems. Compliance isn’t a feature we added — it’s how the service is architected.

Zero PHI on Our Servers

OcuPine Practice Services does not store, replicate, or back up patient health information. We log in to your EHR/PMS (Crystal PM, RevolutionEHR, EyeMD EMR, etc.) via secure remote access and work entirely within your existing systems.

Work Inside Your Systems

Every authorization, billing task, and scheduling action happens inside your practice’s own software environment. Your audit logs, your access controls, your compliance posture — we operate under your rules.

Aggregated KPIs Only

Your OcuPine Practice Services client dashboard shows operational metrics exclusively: prior auth approval rates, billing turnaround times, denial rates, scheduling utilization. No patient names, dates of birth, or diagnosis codes.

Minimum Necessary Access

Each team member is granted only the access required for their specific work — scheduling staff access scheduling modules, billing staff access billing modules. Access is reviewed and revoked at offboarding.

Documentation on Request

Need our compliance documentation for your own audit or accreditation? We provide BAA templates, access logs for your systems, and team certification records upon request — no waiting period.

Internal Compliance Audits

We conduct quarterly internal reviews of access logs, session records, and role assignments to verify ongoing compliance with the minimum necessary standard. Results are available to clients on request.

BAA signed before Day 1.
No exceptions.

A fully executed Business Associate Agreement is a prerequisite for onboarding — not an afterthought. Here’s our process from first contact to signed agreement.

1
First Contact

Intake call & scope review

During your initial call, we document which systems you use (EHR, PMS, clearinghouse) and which services you need. This determines the scope of PHI access required for your BAA.

2
Within 24 hours

BAA sent for review

We send a HIPAA-compliant BAA drafted to reflect your specific service scope. It covers permitted uses, safeguarding obligations, breach notification timelines, and termination procedures. Your attorney is welcome to review it.

3
Before onboarding begins

Both parties execute

We do not accept access credentials or begin any operational work until the BAA is signed by both parties. This is enforced without exception.

4
Ongoing

Annual review & renewal

We proactively schedule BAA reviews annually and whenever your service scope changes materially (e.g., adding a new EHR, adding team members with different access needs).

HIPAA compliance isn’t a one-time box to check.

Our team receives structured HIPAA training with an eye care focus — covering the specific workflows and systems used in optometry and ophthalmology practices.

Annual HIPAA Certification

Every team member completes annual HIPAA Privacy and Security Rule training with a passing exam score before their credentials are renewed. No certification = no active access.

Eye Care–Specific Scenarios

Training includes practice scenarios specific to ophthalmic billing (prior auth workflows, EHR navigation, insurance portal access) — not generic healthcare examples.

Security Awareness Training

Quarterly phishing simulation and security awareness updates covering social engineering, credential hygiene, and safe remote access practices for healthcare environments.

Incident Response Drills

Annual tabletop exercises simulate breach scenarios — including compromised remote access credentials — so our team knows exactly what to do and who to notify within the required timeline.

New Hire HIPAA Onboarding

Before a new team member accesses any client system, they complete a structured HIPAA onboarding module and sign a workforce member confidentiality agreement.

Training Records Available

Completion records for every team member working on your account are available upon request — useful for your own HIPAA compliance documentation and audits.

How we access your systems safely.

Every remote access session follows a structured security protocol. We follow your security policies and supplement them with our own controls.

VPN-Encrypted Connections

All remote access sessions are conducted over encrypted VPN tunnels. Team members connect to client systems only through designated, monitored access pathways — no direct public internet access to your EHR.

Multi-Factor Authentication

MFA is required for every system login — our own internal tools and every client system we access. Hardware tokens or authenticator apps. SMS-only MFA is not accepted for HIPAA-covered systems.

Role-Based Access Control

Access permissions are scoped to job function. A scheduling coordinator cannot access billing modules. Access is provisioned on request, documented, and removed immediately upon role change or offboarding.

Credential Management

Client credentials are stored in an encrypted vault with access limited to named individuals. Credentials are rotated when team assignments change. We never share credentials via email or unencrypted channels.

Session Monitoring

Remote access sessions are logged with timestamps and session metadata. Unusual access patterns (off-hours logins, high-volume data queries) trigger automatic review by our compliance lead within 24 hours.

Offboarding Protocol

When a team member leaves, all client system access is revoked within 2 hours of their last day. Access to shared credential vaults is rotated within 24 hours. No trailing access. We confirm completion in writing.

We operate in OR, WA, ID, and AK.
Each state has its own requirements.

Federal HIPAA sets the floor. Several states where OcuPine Practice Services serves practices have enacted additional privacy and health data laws that we comply with.

OR
Oregon
Oregon Health Records Law • OCPA
  • Oregon Health Records Law (ORS 192.553–.581) imposes stricter patient access rights than federal HIPAA — patients may request records within 30 days.
  • Oregon Consumer Privacy Act (effective July 2024) adds consent and data minimization obligations for health-related consumer data. OcuPine Practice Services’s zero-PHI-storage model satisfies OCPA requirements by design.
  • Oregon breach notification: covered entities must notify affected individuals promptly and no later than 45 days after discovering a breach — stricter than the federal 60-day standard.
  • OcuPine Practice Services operates under Oregon’s requirements for all practices based in or serving Oregon patients.
WA
Washington
My Health MY Data Act • HCRA
  • Washington My Health MY Data Act (effective June 2024) is among the most stringent health data laws in the US — applies to any entity collecting Washington residents’ health data, regardless of HIPAA status.
  • The Act requires explicit consumer consent before collecting, sharing, or selling health data. OcuPine Practice Services does not collect or share Washington patient health data on its own systems.
  • Washington breach notification: 30 days for healthcare-related breaches under the Washington Data Breach Notification Law (RCW 19.255.010).
  • Washington Health Care Records Act (RCW 70.02) mandates that health records be disclosed only for permitted purposes — our minimum-necessary access model is structured accordingly.
ID
Idaho
Idaho Code Title 39 • IPIPA
  • Idaho closely tracks federal HIPAA for healthcare privacy requirements. Idaho Code § 39-1303 governs medical records confidentiality for licensed providers.
  • Idaho Personal Information Protection Act (PIPPA, Title 28, Chapter 51) requires breach notification within 30 days of discovery for incidents involving Idaho residents’ personal information.
  • Idaho does not have a comprehensive consumer health data law beyond HIPAA as of 2025, but OcuPine Practice Services applies HIPAA-compliant practices as the baseline for all Idaho engagements.
  • Idaho’s Medicare Advantage penetration (~51%) means prior auth workflows are high-volume — all MA portal access follows the same secure access protocols as EHR access.
AK
Alaska
Alaska Health Records • APIPA
  • Alaska Stat. § 18.23.065 governs health records confidentiality, requiring that records be used only for purposes consistent with providing care and practice administration.
  • Alaska Personal Information Protection Act (AS 45.48.010–.090) requires expedient breach notification. OcuPine Practice Services applies the 60-day federal HIPAA timeline as a maximum; Alaska practice is to notify within 30 days.
  • Alaska’s low Medicare Advantage penetration (~2%) means the practice mix skews toward commercial and Medicaid — OcuPine Practice Services maintains payer-specific compliance procedures for AK Medicaid (DPA) portals.
  • Remote/rural Alaska practices: OcuPine Practice Services has experience with telehealth billing considerations and limited-connectivity secure access configurations specific to Alaska ODs.

If something goes wrong,
you’ll hear from us first.

HIPAA requires covered entities and their business associates to notify affected individuals of a breach within 60 days. We treat that as a ceiling, not a target.

24 hrs
Internal escalation
Any suspected breach is escalated to our compliance lead within 24 hours of discovery for risk assessment and documentation.
72 hrs
Client notification
We notify your practice within 72 hours of confirming a breach — well ahead of HIPAA’s 60-day requirement. You get the facts, not a delay.
60 days
Maximum SLA (HIPAA)
The federal ceiling. In practice, our goal is individual patient notification within 30 days of discovery, matching the stricter Oregon and Washington standards.
Our breach notification commitment: OcuPine Practice Services provides written breach notification to affected practices within 72 hours of confirming an impermissible use or disclosure of PHI. Our notification includes: (1) a description of the incident, (2) the PHI involved, (3) steps individuals can take to protect themselves, (4) a description of our remediation actions, and (5) contact information for our compliance officer. This commitment is written into every BAA we execute.

Compliance shouldn’t be the reason you delay getting help.

We’ve built the compliance infrastructure so you don’t have to worry about it. Request a BAA and we’ll have it to you within 24 hours.