For Federally Qualified Health Centers (FQHCs), telehealth can expand access to primary care, behavioral health, and other in-scope services. It can also create a documentation nightmare if your entity cannot prove that a 340B prescription came from a qualifying patient encounter.
The core rule is straightforward: a virtual visit is not automatically excluded from 340B eligibility. However, your documentation must demonstrate that the encounter satisfies the same HRSA patient definition that applies to an in-person visit.
HRSA’s Program Assistance Letter (PAL) 2020-01, Telehealth and Health Center Scope of Project, explains that telehealth is a mechanism for delivering an in-scope health service: not a separate service requiring its own Form 5A approval.[^1] The compliance responsibility remains the same.
The 340B Patient Definition Applies to Virtual Encounters
HRSA’s patient definition uses a three-part test. For an individual to qualify as a 340B patient of your FQHC, all three conditions must be satisfied:
- Your entity maintains records of the individual’s health care.
- The individual receives care from a provider employed by or under contract with your entity.
- The service is consistent with the entity’s approved scope of project.
These requirements come from HRSA’s patient definition guidance and continue to guide HRSA audit activities.[^2]
Telehealth changes the delivery method. It does not eliminate any part of the three-part test.
1. Your FQHC maintains the patient’s health care records
The patient’s medical record should be maintained in your entity-controlled electronic health record or another approved health information system. The record must show more than a prescription order.
At a minimum, the telehealth encounter should identify:
- Patient name, date of birth, and medical record number.
- Date and time of the encounter.
- Reason for the visit.
- Clinical history and evaluation appropriate to the modality.
- Assessment, diagnosis, or clinical impression.
- Treatment plan and medications prescribed.
- Rendering provider.
- Follow-up instructions and referrals, when applicable.
A refill request, portal message, or prescription transmitted without a documented clinical evaluation creates a serious eligibility risk. The prescription should be traceable to a bona fide health care encounter, not merely to an administrative transaction.
2. The provider works for or on behalf of your entity
Your documentation must establish that the provider is:
- Employed by the FQHC; or
- Providing care under a valid contract or other arrangement with the FQHC.
For contracted providers, maintain evidence that the FQHC retains responsibility for the care. Your records should allow an auditor to connect the provider to:
- The executed agreement.
- Credentialing and privileging records.
- The applicable FQHC service line or program.
- The patient’s encounter and prescription.
A national telehealth platform may facilitate the visit, but the platform itself does not automatically establish 340B patient eligibility. Your entity must be able to demonstrate the provider relationship and responsibility for care.
3. The service falls within the approved scope of project
The service must align with the FQHC’s approved scope of project and the applicable Form 5A service documentation.
For example, if primary care is within scope, delivering that primary care by video may be permissible under PAL 2020-01. Telehealth itself generally does not need to be separately listed on Form 5A as a service delivery method.[^1]
However, a virtual visit involving an off-scope service, an unrelated business line, or an arrangement outside the health center’s responsibility may not support 340B eligibility.
Location Matters More Than Many FQHCs Realize
Telehealth creates a second documentation challenge: where was the patient located, and where was the provider located at the time of the encounter?
PAL 2020-01 distinguishes between the location where the patient receives care and the location of the health center provider. A patient may be at an in-scope service site, at home, or at another telehealth-enabled location. The provider may be at an in-scope site, at home, or elsewhere.
A patient’s home is not automatically an FQHC service site. PAL 2020-01 also explains that a location used exclusively for telehealth may not satisfy the face-to-face criterion for designation as a service site under existing scope policy.[^1]
That does not mean every home-based encounter is outside scope. It means your policy and records must clearly document the arrangement.
Record, at a minimum:
- Patient location at the time of service.
- Provider location at the time of service.
- FQHC site or program associated with the encounter.
- Whether the provider was employed, contracted, or operating under a referral arrangement.
- Applicable state licensure and scope-of-practice compliance.
- Whether the service was delivered directly by the FQHC or through another arrangement.
If a patient is located outside your usual service area, review the arrangement carefully. Service-area requirements, state telehealth rules, provider licensure, payer rules, and scope-of-project requirements may all apply. A patient’s location does not replace the three-part 340B test.
What Auditors Will Probe in Telehealth-Related Claims
A telehealth prescription should survive a simple audit trail: encounter → provider → medical record → prescription → dispensing or billing record.
Auditors may examine the following areas.
Patient-provider relationship
Can you show that the provider delivered care on behalf of your FQHC? Is the provider’s employment, contract, credentialing, and service-line relationship documented?
Medical record existence and completeness
Does the medical record contain a genuine clinical assessment? A prescription without an encounter note is a weak foundation for patient eligibility.
Scope-of-project alignment
Does the service correspond to an in-scope Form 5A service? Is the encounter correctly associated with the FQHC site, program, or service line?
Patient and provider location
Does the record identify where the patient and provider were located? Are the locations consistent with your telehealth policy, state law, and PAL 2020-01?
Telehealth modality
Does the record specify whether the visit used:
- Audio-video technology.
- Audio-only technology.
- An approved asynchronous or other modality, where permitted.
Document technology limitations when they affect the clinical evaluation.
Informed consent
PAL 2020-01 identifies patient consent as an important telehealth planning consideration.[^1] Your record should show that the patient was informed about telehealth and consented to receive care through that method, consistent with applicable law and your policy.
Provider licensure
HRSA encourages health centers to address provider licensure and scope of practice, including services delivered across state lines.[^1] Maintain the evidence needed to show that the provider was authorized to deliver the service where required.
Billing and payer records
The encounter record, claim, payer record, and prescription should tell the same story. Review:
- Date of service.
- Rendering provider.
- Place-of-service or telehealth indicators.
- Payer and billing status.
- Medication order date.
- Dispensing date.
- Patient identifiers.
Differences do not always mean noncompliance, but unexplained differences are audit risks.
Sliding fee discount and UDS reporting
For services within the Health Center Program scope, your entity must address applicable sliding fee discount requirements. PAL 2020-01 also highlights billing, third-party payments, medical records, and UDS reporting as implementation considerations.[^1]
A telehealth workflow should not bypass your ordinary eligibility, financial-assistance, or reporting controls.
Prescription linkage
The prescription must connect to the documented encounter. Be cautious with:
- Automatic refills.
- Standing medication orders.
- Portal-only requests.
- Prescriptions from unaffiliated clinicians.
- Medication orders entered after the visit without a clear clinical explanation.
A medication may be clinically appropriate and still lack sufficient 340B documentation if the originating encounter cannot be verified.
A Practical Telehealth Documentation Checklist
Use the mnemonic VIRTUAL to standardize your workflow:
V : Verify identity and location
- Confirm patient identity.
- Record the patient’s physical location.
- Record the provider’s physical location.
- Confirm any location-specific legal or operational requirements.
I : Identify the provider relationship
- Confirm employment or contract status.
- Verify credentials and licensure.
- Associate the provider with the FQHC service line or program.
R : Record the clinical encounter
- Document the reason for the visit.
- Record evaluation, assessment, diagnosis, and treatment.
- Identify the telehealth modality and any limitations.
T : Tie the service to scope
- Confirm the service is within the approved scope of project.
- Associate the encounter with the correct FQHC site or service.
- Apply applicable sliding fee and billing procedures.
U : Understand consent and privacy
- Document informed consent consistent with policy.
- Maintain privacy and confidentiality.
- Record any interpreter, caregiver, or technical-support involvement when relevant.
A : Associate the prescription
- Link the medication order to the encounter.
- Confirm the prescribing provider.
- Match the patient, date, diagnosis, and medication across systems.
L : Look back and audit
- Retain the encounter, billing, and dispensing records.
- Review exceptions.
- Correct incomplete documentation before the claim proceeds through the 340B workflow.
Pre-Visit, During-Visit, and Post-Visit Controls
Before the visit
- Confirm the patient is established or document the process for initiating the relationship.
- Verify provider employment or contract status.
- Confirm the service is in scope.
- Configure the encounter type as telehealth.
- Verify state licensure and consent requirements.
During the visit
- Confirm patient and provider locations.
- Document the modality.
- Complete a clinically meaningful evaluation.
- Record assessment and treatment.
- Apply sliding fee and billing procedures as required.
- Document informed consent.
After the visit
- Link the prescription to the encounter.
- Reconcile the EHR, billing, and pharmacy records.
- Validate payer and Medicaid billing treatment.
- Include the visit in applicable UDS reporting.
- Route exceptions for compliance review.
Build an Audit-Ready Framework, Not a Collection of Notes
HRSA’s 340B Compliance Improvement Guide emphasizes leadership commitment, education and training, integrated systems, auditable records, data-driven improvement, and regular auditing.[^3]
Apply that framework to telehealth by creating one controlled evidence package for each sampled claim:
- Patient demographic and eligibility record.
- Complete telehealth encounter note.
- Provider employment, contract, and credentialing evidence.
- Patient and provider location data.
- Consent and modality documentation.
- Scope-of-project mapping.
- Billing, payer, and sliding-fee records.
- Prescription and dispensing data.
- Internal review or exception resolution.
- Corrective action documentation, if needed.
Your compliance team should test these records routinely rather than waiting for an HRSA audit. For a broader risk-management approach, review Compliance Quick-Start: One Simple Step to Avoid False Claims Act Liability.
GapRx 340B Consultants can help your FQHC map telehealth workflows, validate patient-eligibility logic, connect encounter data to pharmacy claims, and develop audit-ready reporting. Our HRSA Audit & 340B Compliance services are designed to identify gaps before they become findings.
The Bottom Line
A virtual visit can support 340B eligibility when your FQHC can demonstrate:
- A maintained health care record.
- Care from an employed or properly contracted provider.
- An in-scope service.
- Clear patient and provider location data.
- A documented telehealth encounter.
- A prescription directly linked to that encounter.
Do not treat telehealth as a documentation shortcut. Treat it as a delivery method that requires disciplined controls.
For more audit preparation guidance, read Going Through a HRSA Audit: A Step-by-Step Guide to 340B Compliance With Zero Findings, 8 Best Practices for 340B Claims Management, and Building a 340B Compliance Team for Audit Readiness.
Ready to pressure-test your telehealth 340B workflow? Schedule a 30-minute strategy call with GapRx.
Sources
[^1]: Health Resources and Services Administration, PAL 2020-01: Telehealth and Health Center Scope of Project.
[^2]: Health Resources and Services Administration, 340B Patient Definition Resources.
[^3]: Health Resources and Services Administration, 340B Compliance Improvement Guide.