A health system with three hospitals does not have one DEA date. It has a registration per site, a state registration beside each one, and a list of practitioners who prescribe under the hospital's number with their own suffix codes. The list goes stale faster than any certificate expires.
This page owns hospital and health-system tracking: campus registrations, practitioner internal codes, and the roster review. The general expiration and renewal-window clock lives on DEA registration expiration tracking. The Form 224 and Form 224a document record lives on DEA Form 224 and 224a tracking. Separate pharmacy locations outside the hospital are covered on multi-location pharmacy DEA tracking. (General information only - not legal or regulatory advice. See Sources.)
Remindax tracks site registration dates, practitioner code assignments, owners, status, and documents you upload. It does not file, contact DEA or a state board, look up or verify numbers, or decide who may use the hospital's registration. Your medical staff office, pharmacy leadership, and advisors own those decisions.
1. What is hospital DEA registration tracking?
It is two linked records. The first is a campus roster: each hospital site and hospital pharmacy, its DEA registration expiry, the day its renewal window opens, its state controlled substance registration, and the person responsible. The second is a practitioner code roster: every resident, intern, fellow, or staff practitioner authorized to work under a hospital registration, the internal code assigned to them, and the dates the code starts and ends.
Under 21 CFR 1301.12, a separate registration is required for each principal place of business where controlled substances are handled, so a system with several campuses tracks one row per registered site. Under 21 CFR 1301.22(c), a hospital may authorize individual practitioners who are its agents or employees to administer, dispense, or prescribe under the hospital's registration, using a specific internal code as a suffix to the hospital's number, and keeps a current list of those codes. Remindax keeps both lists dated, owned, and reminded. Your team decides what they require.
1.1 What sits on each roster
Site, address, and registration
The registered location - main hospital, satellite campus, or inpatient pharmacy - with its certificate uploaded.
DEA expiry and window date
The end date on the site's certificate and the day the first reminder should fire.
State CSR expiry
The site's state controlled substance registration, where the state issues one. A separate calendar.
Practitioner, code, and dates
Who holds the code, which site registration it hangs off, role, start date, planned end date, and status.
2. What does a health-system campus roster look like?
One row per registered site, two clocks per row, an owner, and a count of active practitioner codes tied to that registration. The example is illustrative - sites, addresses, and dates are made up.
| Site | Type | DEA expiry | Window opens | State CSR expiry | Active codes | Owner | Status |
|---|---|---|---|---|---|---|---|
| North Campus | Main hospital | Dec 31, 2026 | Nov 1, 2026 | Jun 30, 2027 | 142 | Director of pharmacy | Window opens soon |
| North Campus | Inpatient pharmacy | Mar 31, 2027 | Jan 30, 2027 | Jun 30, 2027 | - | Pharmacy manager | Current |
| South Campus | Community hospital | Nov 30, 2026 | Oct 1, 2026 | Feb 28, 2027 | 38 | Site pharmacy lead | Window open - not submitted |
| East Campus | Specialty hospital | Aug 31, 2027 | Jul 2, 2027 | Dec 31, 2026 | 21 | Site pharmacy lead | State CSR due first |
| West Campus | New site | Pending | - | Pending | 0 | System compliance lead | Opening - registrations pending |
Illustrative roster only. Window-open dates in the example assume the 60-day reregistration window summarized on DEA registration expiration tracking. Confirm current rules in Sources.
South Campus is inside its window with nothing logged. East Campus has a distant DEA date but a state registration due first - the reason both clocks sit on the same row. The "active codes" column links each site to its practitioner roster, so a lapse at North Campus is visibly a problem for 142 people, not one certificate. Keep each site's DEA biennial inventory date and any CSOS signing certificate for electronic ordering on linked rows rather than extra columns.
3. How should practitioner internal codes be tracked?
Each code is a dated assignment, not a permanent fact. A resident gets a code when training starts and should lose it when training ends. A fellow moves sites. A staff physician gets an individual registration and no longer needs the hospital code. Track each code as a row with a start date, a planned end date, and an owner who closes it out.
| Practitioner | Role | Site registration | Internal code | Start | Planned end | Status |
|---|---|---|---|---|---|---|
| Resident A | PGY-1 | North Campus | -R101 | Jul 1, 2026 | Jun 30, 2027 | Active |
| Fellow B | Fellow | North Campus | -F014 | Jul 1, 2025 | Jun 30, 2027 | Active |
| Intern C | Intern | South Campus | -I022 | Jul 1, 2026 | Jun 30, 2027 | Active |
| Staff D | Staff practitioner | East Campus | -S007 | Mar 1, 2024 | Sep 30, 2026 | End date passed - close out |
Illustrative only. Names and codes are placeholders. Real code formats follow your hospital's own scheme and the rule in Sources.
3.1 Events that touch a code
- ✓Training year starts: new residents and interns get code rows with start and planned end dates.
- ✓Rotation to another campus: log which site registration the code now sits under, with a date.
- ✓Graduation or departure: the planned end date fires a reminder to close the code row.
- ✓Own registration obtained: log the change and end the hospital code, keeping the history.
4. How often should the internal code roster be reviewed?
The rule calls for a current list, so the review is a recurring task, not a one-time cleanup. Your team sets the cadence. For example:
Ended-date sweep
Every code past its planned end date is listed for close-out.
Full roster sign-off
Medical staff office and pharmacy confirm the list and upload the signed review.
Training-year turnover
The busiest week: outgoing codes closed, incoming codes opened.
5. Why staggered campus dates make health-system tracking hard
Sites joined at different times
Mergers and new builds bring registrations on their own calendars.
DEA and state clocks drift apart
The state registration for a site can come due a year before its DEA date.
Ownership is spread out
Pharmacy, medical staff office, and compliance each hold part of the picture.
Codes depend on the site
A lapse at one campus affects every practitioner coded to it.
6. Which owner model works for hospitals and health systems?
Split the work by roster, then give the system one view of both:
Site pharmacy lead
Owns the campus row and its two clocks. Gets the first reminder.
Medical staff or GME office
Owns code start and end dates and the recurring review.
Compliance or pharmacy director
Sees every campus and code. Handles late escalations.
6.1 An example escalation ladder
- ✓Window opens: reminder to the site pharmacy lead by Email, SMS, or WhatsApp.
- ✓Mid-window checkpoint: nothing logged, so the system director is copied.
- ✓Code end date passed: the code owner is reminded, then the system lead if it stays open.
- ✓Review overdue: the quarterly sign-off escalates until the signed list is uploaded.
Compliance tracking works best when escalation lives in the tool, not one director's inbox.
7. How Remindax tracks DEA registrations across a health system
Remindax is date-and-status tracking - not a portal, filer, or lookup tool:
Every campus on one roster
DEA and state CSR per site, certificates uploaded, grouped by campus.
Practitioner code rows
Who holds each code, under which site, from when to when.
Recurring review tasks
Monthly, quarterly, or July reviews with owners and signed lists attached.
Exports by site or status
Pull active codes per campus or upcoming windows for the next quarter.
Remindax does not submit Form 224a, contact DEA or a state board, assign codes, or look up or verify numbers. It holds registration documents, code assignments, and dates - not patient data - on AWS hosting with encryption. GDPR-ready.
8. Why spreadsheets fail for hospital DEA tracking
Pharmacy and the medical staff office keep separate sheets. Neither reminds anyone, and July turnover breaks both.
- xSite and code lists live in different departments
- xNo alert when a campus window opens
- xDeparted practitioners stay on the code list
- xState CSR dates sit on another tab
- xReviews happen when someone remembers
- ✓Campus and code rosters linked in one place
- ✓Per-site reminders when each window opens
- ✓Code end dates trigger close-out reminders
- ✓DEA and state CSR side by side
- ✓Recurring reviews scheduled and escalated
9. Key takeaways
- ✓Track one row per registered hospital site and hospital pharmacy.
- ✓Pair each site's DEA registration with its state controlled substance registration.
- ✓Treat every practitioner internal code as a dated assignment with a start, an end, and an owner.
- ✓Schedule the code roster review and plan for July turnover.
- ✓Remindax tracks dates and status and reminds by Email, SMS, and WhatsApp. It does not file, look up, verify, or give legal advice. Free to start.
10. Frequently Asked Questions
21 CFR 1301.22(c) lets a hospital authorize certain practitioners to work under its registration with an assigned internal code, under the conditions in the rule. Your medical staff office and advisors decide who qualifies. Remindax tracks the assignments.
The practitioner, role, the site registration the code sits under, the internal code, start date, planned end date, owner, and status.
The rule calls for a current list, so set a recurring review. Many teams sweep ended codes monthly, sign off quarterly, and plan a full pass for July turnover.
21 CFR 1301.12 calls for a separate registration for each principal place of business. Systems with several campuses usually track one row per registered site. Confirm specifics with your advisors.
This page covers hospital sites, hospital pharmacies, and practitioner codes. Separately registered pharmacy locations are covered on multi-location pharmacy DEA tracking.
No. Remindax tracks dates, status, owners, and documents. Filing and code decisions stay with your team. The submission record is covered on DEA Form 224 and 224a tracking.
No. It holds registration documents, code assignments, dates, and owners - not patient records. Data sits on AWS hosting with encryption, and Remindax is GDPR-ready.
Yes - a forever-free plan, no credit card required.
Sources & References
Public educational material on DEA registration for hospitals - not legal or regulatory advice. Confirm with DEA and your state authority. Fees are not restated here. This page does not provide filing instructions.
- *DEA Diversion - Registration (hospital/clinic, Form 224 and Form 224a)
- *21 CFR 1301.12 - Separate registrations for separate locations (Cornell LII)
- *21 CFR 1301.13 - Application for registration; time for application; expiration date (Cornell LII)
- *21 CFR 1301.22 - Exemption of agents and employees; affiliated practitioners (Cornell LII)
Never lose track of a campus DEA date
Track every hospital site's DEA registration, state CSR, and practitioner codes - automatically.
GDPR-ready | AWS secure cloud | Encrypted storage | Setup under 5 minutes