Part 03 · Provider Concerns
Two-Hat Provider Guide · Part 03 of 10
Of all the concerns providers raise about the two-hat model, this is the one they raise first. The fear is reasonable, and it deserves an honest answer rather than a reassurance. Operated correctly, the two-hat model does not affect VA Community Care credentialing or DEA registration. Operated incorrectly — with operational bleed-through between the two practices — it can. The difference matters, and it is worth understanding before you start.
The short version
Writing medical cannabis treatments for veterans under a separate state medical cannabis practitioner credential will not cost you your medical license, your DEA registration, or your VA Community Care credentialing. The DEA has not, in more than twenty years since Conant v. Walters, revoked a physician’s registration for cannabis recommendation activity conducted under state authority. State medical boards explicitly credential physicians for medical cannabis practice. VA Community Care credentialing does not ask about, and does not prohibit, holding a state cannabis practitioner credential. The fear is understandable; the actual exposure is operational, not legal — and the rest of this part explains how to manage that operational side.
The DEA question
DEA registration authorizes a provider to handle and prescribe federally controlled substances. Cannabis is a Schedule I controlled substance under federal law, which means no DEA registration authorizes its prescription — not because the registration would not be valid, but because Schedule I substances are not federally prescribable. The DEA registration is irrelevant to state cannabis practice, because state cannabis programs operate under state authority, not federal DEA authority.
The historical concern about DEA action against cannabis-recommending physicians traces back to the late 1990s and early 2000s, when the federal government threatened DEA enforcement against physicians who recommended cannabis. Conant v. Walters in 2002 closed that pathway. The DEA has not, in the two decades since, revoked a physician’s DEA registration solely for cannabis recommendation or certification activity conducted under state cannabis program authority. The legal protection is real, supported by precedent that has held up across multiple federal administrations.
The line that does matter
What can affect DEA registration is conduct that crosses the line from state-authorized cannabis practice into actions outside any legal authority — physician personal cannabis acquisition or distribution, conduct outside the state program framework, or activity that crosses into federal payor billing for cannabis services. The two-hat model contemplates state-authorized clinical practice, not these activities.
The VA Community Care credentialing question
VA Community Care credentialing is governed by the VA’s Community Care Network requirements and by the Third Party Administrators (Optum for Regions 1, 2, and 3; TriWest for Regions 4 and 5) that manage CCN credentialing operationally. Neither the VA nor the TPAs prohibit providers from holding state cannabis practitioner credentials. The two are simply different authorities operating in different domains.
What VA Community Care credentialing does ask about is anything that would call into question the provider’s fitness to deliver federal care. Disciplinary actions. Malpractice history. License restrictions. Federal exclusion lists. None of these is implicated by holding a state cannabis practitioner credential in a state with a legal medical cannabis program. The state credential is itself evidence of being licensed and in good standing under state authority.
The risk to VA credentialing arises not from the existence of the state cannabis practice but from operational failures that affect the federal practice. A two-hat provider who fails to maintain clean operational separation — who issues cannabis certifications in their VA capacity, who bills federal payors for cannabis services, who documents cannabis treatment in VA records as if it were VA-authorized care — creates risk that does not exist when the separation is maintained.
What VA actually permits about veteran cannabis use
The VA’s own published guidance on veteran cannabis use is worth reading before entering the two-hat model. The relevant points:
- Veterans will not be denied VA benefits for cannabis use that complies with state law. This is explicit and statutory.
- Veterans are encouraged to disclose cannabis use to their VA providers. The disclosure has no benefits consequence.
- VA providers may discuss cannabis with veterans in their VA capacity. They may document use, adjust care planning to account for it, screen for drug interactions, and integrate the cannabis use into the federal clinical picture.
- VA providers cannot issue cannabis certifications in their VA capacity. They cannot recommend cannabis, complete state forms, or register veterans for state programs while operating under VA authority. (Pending legislation in 2025 would change this; as of this writing, this constraint remains operative.)
- VA pharmacies do not dispense cannabis. Cannabis use occurs entirely outside the VA system, through state-licensed dispensaries.
- The VA does prohibit cannabis use on federal property, including VA medical centers. This is a property rule, not a benefits rule.
The federal property rule
The federal property prohibition is one of the few places where federal cannabis status intersects with day-to-day VA care. Cannabis cannot be used, possessed, or stored on VA property. Veterans receiving VA care who use cannabis must do so off federal property. This is not a barrier to the two-hat model — the cannabis practice operates outside VA property by definition — but it is the rule that providers and patients sometimes misunderstand. It is a property rule, not a clinical or benefits rule.
Where two-hat providers actually run into trouble
The failures that affect VA credentialing in the two-hat model are operational, not legal. The pattern looks like this:
- Documentation bleed-through. A provider documents cannabis treatment activity in the VA EHR as if it were VA-authorized care, or notes a VA encounter in the state cannabis practice chart. The records mix because the provider treats the two practices as one.
- Billing bleed-through. A cannabis certification gets billed to a federal payor, or a VA-billable service gets billed under the cannabis practice’s structure. Money flows through the wrong channel because the practice has not maintained two channels.
- Scheduling bleed-through. The same booking system is used for both practices, and patients show up for cannabis appointments during scheduled VA Community Care time. The calendar treats both as one practice.
- Capacity bleed-through. The provider issues a state cannabis certification during a VA Community Care visit, under VA authority. This is the most direct failure mode and the one that creates the clearest VA credentialing risk.
None of these are exotic problems. They are the predictable failures of trying to run two distinct practices through one operational infrastructure. The two-hat model exists precisely to prevent them — not as a paperwork exercise, but as the operational discipline that makes the model legally sound.
What the two-hat provider does instead
The two-hat model treats the two practices as actually separate. Separate EHR (or clearly separated sections within one EHR, with access controls). Separate billing infrastructure. Separate scheduling, often using separate names for the practices that make the distinction obvious to patients and staff. Separate documentation patterns. Separate physical spaces, where feasible. Separate financial accounts. The same provider, holding both, but the operational architecture is two practices, not one.
Part 4 of this guide walks through what “kept separate” actually looks like in practice — the operational details that make the legal protections real rather than theoretical.