Not legal or compliance advice: Child site eligibility determinations are fact-specific and depend on entity type, Medicare cost report treatment (for hospitals), grant scope (for grantees), state law, and current HRSA guidance. Consult your legal counsel, your 340B compliance officer, your external auditor, HRSA Office of Pharmacy Affairs (OPA), your reimbursement and cost report team, and Apexus before registering any site.
Adding a child site is one of the highest-leverage and highest-risk decisions a covered entity makes in 340B. Done well, it extends program reach to patients the entity is already serving under its scope or mission. Done poorly — prematurely, inaccurately, or without operational readiness — it can create audit findings, repayment obligations, reputational risk, and, in some cases, broader program eligibility questions.
This article lays out a durable framework: what qualifies as a child site, how the integral-part / reimbursable-cost standard works for hospitals, how scope-of-project works for grantees, how the OPAIS quarterly registration cadence shapes timing, what readiness looks like before you file, and what happens after.
A hospital child site is generally an outpatient facility of the hospital. Historically, HRSA has looked at whether the site is an integral part of the hospital; listed as a reimbursable outpatient cost center on the most recently filed Medicare cost report; and operating in a manner consistent with 340B program requirements.
The cost report link is not a formality: For hospitals, child-site eligibility is typically anchored to a filed Medicare cost report. A site must appear as a reimbursable outpatient cost center on the most recently filed cost report before registration. Registering in advance is one of the most common and most consequential errors.
For FQHCs, FQHC look-alikes, Ryan White clinics, and similar grantees, child-site eligibility is anchored not to a cost report but to the scope of the grant (or, for look-alikes, the scope of project). Practically, for an FQHC that means the site must be on the Health Center Program scope of project (Form 5B), delivering services consistent with the scope, with patients falling within the entity's 340B-eligible patient definition.
Each hospital subtype has specific eligibility conditions. Child-site rules apply within those overall eligibility frameworks and, for most, rest on the cost-report anchor described above.
Think of the parent hospital as a tree and its outpatient departments as branches. For a branch to be a 340B child site, two things typically must be true: the branch is genuinely part of the tree operationally, financially, and from a patient-care accountability standpoint; and the tree's official record — the filed Medicare cost report — shows the branch as a reimbursable outpatient cost center.
If a site is integrated in practice but not yet on the filed cost report, it is not yet a child site, no matter how much sense it would make operationally.
For FQHCs and similar grantees, the equivalent discipline runs through the grant scope. Keep a current Form 5B. Ensure any proposed 340B child site is a service site on the scope document. Align the patient definition at the site with both the scope and the 340B patient definition. Coordinate changes with both your Health Center Program office and your 340B registration process.
Two systems, two clocks: Your grant scope changes on one timeline. Your 340B OPAIS registration changes on another (quarterly windows). A site cannot be 340B-registered ahead of its scope approval, and a scope approval does not automatically create a 340B registration.
HRSA has historically used a quarterly registration cadence for 340B, with defined registration windows and corresponding effective dates on the first day of the subsequent quarter. Verify current window dates in OPAIS.
Verify current windows: Check OPAIS and Apexus guidance for the current registration window dates and any changes to submission requirements before planning a filing.
Decisions about new child sites must be made well in advance of a window, not inside it. A site's cost report treatment, Medicare enrollment, provider credentialing, and operational readiness must all be in place before the window opens. Missing a window means at least a quarter of delay, which may be the right outcome if readiness is incomplete.
Before a site enters the registration queue, confirm the following are in place.
Registering a site before it is ready tends to produce ineligible dispenses, audit findings, reputational risk, and downstream operational chaos.
When in doubt, wait a quarter: A quarter of delay is almost always less costly than a finding.
In the first 90 days after registration: reconcile the site's activity in the TPA against source systems daily or weekly; sample dispenses for accuracy; watch for exception patterns; confirm Medicaid handling; capture lessons learned. After the first 90 days, the site folds into the ongoing compliance cadence.
Each child site should be able to demonstrate, from its own files and staff, that it understands and follows the same 340B policies and procedures as the parent. Mirroring means current P&Ps are accessible at the site; staff are trained at onboarding and annually; site-specific details are captured as addenda; and any deviation is flagged to the compliance committee.
Annual recertification is especially meaningful for child sites. Maintain a site-by-site change log. Reconcile the OPAIS record against the current cost report or scope of project at least annually. Run a recertification pre-check 60–90 days before the window. Document who recertified, what they verified, and what source they verified it against.
Registering ahead of the cost report. A classic hospital pitfall.
Scope drift without registration update. A grantee adds a service location under its grant and no one updates OPAIS.
Orphan contract pharmacies. A site is deregistered, but contract pharmacy mappings at the TPA still point to it.
Provider roster rot. Dispenses by providers whose status is ambiguous become audit findings.
Copy-paste P&Ps. Ambiguity at the site level becomes the finding.
Treating recertification as a checkbox. A common path to self-inflicted findings.
Before you decide to register a site, ask in order:
- Does the site genuinely fit the covered entity's mission and patient base?
- Does the site satisfy the applicable eligibility anchor right now, with documentation?
- Are policies, procedures, provider rosters, training, drug handling, Medicaid decisions, and data systems all ready?
- Has legal counsel and the compliance committee signed off in writing?
- Is the next OPAIS window far enough away that readiness completes before it opens?
If any answer is "not yet," wait.
Expanding the child site footprint is a test of discipline more than a test of ambition. The covered entities that hold the line on readiness — who wait the extra quarter, who document the extra memo, who mirror P&Ps at every new location — tend to operate programs that audit cleanly and serve patients consistently.
This article is educational and does not constitute legal, tax, regulatory, compliance, or financial advice. Program rules change; verify current guidance with HRSA's Office of Pharmacy Affairs, Apexus, and qualified counsel before acting.