HQB’s role and the limits of this page
Medical billing, claims administration, and related revenue cycle services can involve protected health information (PHI). When HQB creates, receives, maintains, or transmits PHI on behalf of a HIPAA covered entity or another business associate for a covered function, the applicable business associate requirements govern that work.
A business associate’s obligations arise under applicable law and the relevant relationship; the absence of a signed document does not eliminate obligations that already apply. The Business Associate Agreement (BAA) defines the parties’ permitted activities and responsibilities, alongside applicable legal requirements.
This page explains website boundaries and engagement considerations. It is not a BAA, a HIPAA authorization, a provider’s Notice of Privacy Practices, a security audit report, or a certification. HQB is not representing that HHS or another agency has certified this website or every system referenced on it.
Keep patient information out of public inquiries
Public forms, chat, consultation booking, and ordinary email are intended for practice-level business discussions. You may describe your specialty, systems, service needs, or an administrative issue without identifying patients.
Do not send patient names, charts, claim images, insurance/member identifiers, diagnoses associated with an individual, Social Security numbers, passwords, or other sensitive material through those channels. This website is not a patient portal, a patient payment portal, or an emergency-reporting service.
If sensitive information has already been sent through an inappropriate channel, contact HQB promptly without resending it. Explain the type of issue and ask how to provide any necessary supporting information through a suitable channel.
Before arranging PHI access
Do not grant new access or transfer patient records until the parties have confirmed the appropriate engagement arrangements. These should address:
- The services, responsible parties, and information necessary for the work.
- An executed BAA and other required agreements before the applicable access is arranged.
- Authorized individuals, systems, access permissions, and secure transfer methods.
- Client, HQB, and any applicable subcontractor responsibilities.
- Incident reporting contacts, escalation expectations, and applicable response obligations.
- Retention, return, destruction, and post-termination handling requirements.
A marketing statement, website form, ordinary email exchange, or cookie choice does not replace these arrangements.
Permitted uses and minimum necessary information
PHI may be used or disclosed only as permitted or required by applicable law and the relevant BAA. The agreement must not authorize a use that would violate HIPAA if undertaken by the covered entity, except as law permits. Applicable minimum-necessary requirements limit the information used, disclosed, or requested for the purpose.
A website statement does not create permission to use patient information for unrelated marketing, model training, advertising, or another independent purpose. Any proposed use must be evaluated under the governing legal permissions and engagement documents.
Providers remain responsible for their clinical decisions and clinical records. Responsibilities for billing, coding, payer communications, authorizations, and records access must be defined for the engagement; no allocation relieves either party of legal duties that apply directly to it.
Safeguards and access arrangements
HIPAA requires appropriate safeguards for PHI and applicable Security Rule protections for electronic PHI. The controls relevant to an engagement should be assessed against its systems, access methods, risk assessment, and contractual requirements.
Topics for review include authorized access and role restrictions, authentication, transfer and storage protections, workforce responsibilities, activity review, incident management, availability, and changes to permissions when a role or engagement ends. Specific controls, certifications, hosting locations, and technical capabilities should be supported by current documentation rather than inferred from this website.
Ask HQB to review requirements before access is enabled. Do not share a clinician’s or another user’s password as a substitute for an authorized access arrangement.
Subcontractors and processing locations
Where a subcontractor creates, receives, maintains, or transmits PHI on behalf of a business associate, applicable HIPAA business associate requirements extend to that relationship. Required written assurances and appropriate restrictions must be established before the relevant disclosure or access.
Personnel locations, subcontractor involvement, approved systems, and any client restrictions should be addressed during contracting and onboarding. This page does not promise that every engagement uses the same personnel, operates only in the United States, or has an identical technology configuration.
Website analytics are separate from client billing
General website measurement, chat, CRM, and scheduling tools are different from systems approved for contracted patient-data processing. Public website tools should not be treated as approved PHI channels merely because they appear on an HQB webpage.
Cookie consent is not a HIPAA-compliant authorization. Where a tracking provider receives PHI, disclosures require an applicable legal permission and the required business associate arrangements or authorization. Describing a disclosure in a website privacy policy does not itself make that disclosure permissible.
The Privacy Policy describes public website tools and the available analytics choices. It does not expand permitted uses of patient information.
Privacy concerns, incidents, and notifications
Report a suspected issue involving HQB to compliance@healthquestbilling.com or (415) 508-6537. Describe the concern without attaching PHI, passwords, or other sensitive records; request an appropriate channel for supporting material. Existing clients should also use their agreed escalation contacts.
Security incidents and breaches must be assessed and reported as required by applicable law and the relevant agreements. Required notices and assistance are not replaced or waived by this website page. This public contact route does not establish a guaranteed response time or a substitute emergency service.
Retention and the end of an engagement
The relevant agreements should define records ownership, retention duties, available exports, transition support, and how access ends. HIPAA business associate contract provisions address return or destruction of PHI at termination where feasible and continued protection and limited uses where return or destruction is not feasible.
Do not assume that closing a website inquiry, ending a consultation, or deleting a CRM contact deletes patient records, legally required records, or backups held under a separate client engagement.
Patient requests and further information
If you are a patient seeking records, an amendment, a privacy accounting, or an explanation of a bill, begin with the healthcare provider identified on the record or statement. That provider can identify the responsible party and the appropriate request process. HQB’s assistance is subject to its role, the relevant BAA, and applicable law.
You may report a concern to the appropriate regulator, including the U.S. Department of Health and Human Services Office for Civil Rights where HIPAA applies. Nothing on this page limits a right to raise a lawful concern or complaint.
Engagement or privacy questions: privacy@healthquestbilling.com · (415) 508-6537
Health Quest Billing LLC, 611 S Dupont Hwy, Suite 102, Dover, DE 19901, United States.