Put on your seatbelt. The 340B space is about to get even more interesting. The newly filed AbbVie lawsuit against HRSA presents the inverse legal argument advanced in Genesis HealthCare Inc. Both cases center on the same statutory question, who qualifies as a patient under the 340B statute, but reach opposing conclusions about whether HRSA’s interpretation is too narrow or too broad. This new case sets up a legal battle against HRSA’s patient definition unlike anything we have seen before.
Genesis: Court Rejects Narrow Prescription Eligibility Definition
In the Genesis Health Care audit, HRSA concluded the entity dispensed 340B drugs to ineligible patients and failed to maintain documentation supporting compliance with the patient definition. HRSA asserted that a patient must receive a prescription originating from a covered entity encounter.¹
“HRSA would like to clarify that in order for an individual to qualify as a 340B patient, GHI must have initiated the healthcare service resulting in the prescription.”²
The court held that despite HRSA later vacating the audit findings, the controversy remained because the agency continued enforcing the same interpretation of patient eligibility.
“A controversy still exists because HRSA’s unlawful guidance and interpretation of the term patient still exists.”³
The Genesis ruling, that HRSA's interpretation of "patient" definition was too limited, effectively allowed covered entities to revisit narrow patient definition policies requiring referrals, provider employment relationships, and detailed documentation for outside specialist prescriptions.
340B Performance 360 Streamline All Your 340B Data
Seamless Data. Smarter Decisions. Stronger Performance
AbbVie: HRSA Interpretation Too Broad
AbbVie asserts in its new lawsuit, "HRSA’s interpretation is so loose and broad that it permits, for example, two or more different covered entities to each claim that the same prescription was written for its own patient.”⁴
The complaint further states that HRSA’s interpretation captures individuals who may have had only a cursory encounter and allows overlapping patient claims across covered entities. Beyond concerns about referral eligibility, AbbVie’s position also seeks to impose a time limited patient relationship and restrict contract pharmacy attribution, directly targeting replenishment models and longitudinal patient eligibility.
AbbVie Proposed Interpretation of Patient
AbbVie’s proposed audit work plan submitted to HRSA advanced a narrower statutory interpretation requiring:
Direct nexus between care and prescription. The prescription must result from care provided by the covered entity.
Covered entity clinical responsibility. The covered entity must maintain oversight for the condition being treated.
Time limited patient eligibility. Patient status must be tied to a healthcare encounter within 12 months of the prescription.
Restrictions on contract pharmacy and multi entity attribution. Prescriptions cannot be attributed across entities or retroactively assigned.
Together, these elements would move the program toward a prescription based and time limited patient definition rather than a relationship-based model.
Why This Matters:
If AbbVie is successful in its litigation, court findings could
Could limit use of outside specialist prescriptions without direct covered-entity involvement
May impose a strict timeline for patient eligibility tied to recent covered-entity care
May require direct provider responsibility for the condition being treated
Could increase manufacturer audit authority, activity, and documentation expectations
Audit Rejection as Litigation Vehicle
HRSA rejected AbbVie’s proposed audit work plans and indicated it would not enforce findings based on this interpretation. AbbVie argues this effectively denied its statutory audit rights and prompted judicial review.⁵ AbbVie’s lawsuit asks the court to resolve several core legal questions about the 340B patient definition and HRSA’s audit authority, including whether HRSA’s 1996 guidance improperly expands eligibility beyond statutory limits. The structure of AbbVie’s audit proposal also suggests a deliberate litigation path.
Conclusion
Genesis and AbbVie represent opposite ends of the same statutory debate. Genesis rejected HRSA’s narrow interpretation requiring prescriptions to originate from covered entity encounters and allowed entities to revisit restrictive referral based patient definitions. AbbVie now challenges HRSA from the other direction, arguing the agency’s flexible definition has expanded eligibility too far, allowing unchecked growth and enabling diversion.
The resolution of this new competing case may fundamentally redefine 340B patient eligibility, including referral-based prescribing, time limited patient status, and the permissible scope of contract pharmacy utilization.
Ready for expert guidance and support for optimizing your 340B program based on the latest industry events? Contact us today to learn how we can support your entity's success.
HRSA audit findings and patient definition dispute. Genesis decision link.
HRSA March 2019 letter quoted in Genesis decision. Genesis decision link.
Fourth Circuit live controversy finding quoted in Genesis. Genesis decision link.
AbbVie Complaint, interpretation of patient definition. AbbVie complaint link.
HRSA refusal to enforce audit findings. AbbVie complaint link.