Billing requires access to protected health information. We treat that responsibility seriously — contractually, technically and in daily habits.
Photo: Sora Shimazaki / PexelsBefore any system access, Dental Billing Community signs a HIPAA Business Associate Agreement. The BAA should define permitted uses, safeguards, reporting duties, subcontractor requirements and termination responsibilities.
We use individual logins, MFA where supported, least-privilege permissions and prompt de-provisioning when a role changes or access is no longer needed. Shared logins create audit and accountability problems.
Billing work should not require broad clinical or administrative access. We limit PHI use to what is needed for verification, claims, attachments, AR follow-up, denial work, payment posting and patient billing.
HIPAA is not a one-time checkbox. Our workflows rely on trained staff, documented procedures, clear escalation paths and experienced biller review of AI-assisted work before it affects a claim or account.
Every practice should know who to contact, what to preserve and how quickly concerns must be escalated. We maintain a defined process for reporting and responding to suspected privacy or security incidents.
Compliant billing starts with documentation. Codes must reflect the service actually provided and supported in the record. We decline requests to change codes only to improve payment or bypass payer policy.
Thirty minutes on a screen share. A written action plan afterward. No obligation.
Coding changes, payer alerts and new case studies — straight to your inbox.
Join the community