Treatment Center Admissions Disposition Codes: A Practical Taxonomy
Build treatment center admissions disposition codes that distinguish access outcomes, barriers, person choice, fit, coverage, capacity, referrals, unresolved work, closure, correction, and re-entry.
On this page: Direct answer
Direct answer
Treatment center admissions disposition codes: what operators need to know
Build treatment center admissions disposition codes that distinguish access outcomes, barriers, person choice, fit, coverage, capacity, referrals, unresolved work, closure, correction, and re-entry. Separate current state, terminal outcome, barrier, and next action. Use neutral observable labels rather than motivated, bad lead, or noncompliant.
Treatment center admissions disposition codes should explain what happened without blaming the person, hiding unresolved work, or collapsing clinical, coverage, capacity, and preference decisions. The taxonomy supports follow-up, access improvement, source feedback, staffing, conversion analysis, and quality review only when every code has a definition, required evidence, owner, timing, and correction rule.
Use a small top-level outcome set with governed reason and subreason fields. Preserve chronology and allow correction; do not overwrite a prior barrier when another issue appears. Codes are operational metadata, not diagnoses, legal conclusions, payer guarantees, or a substitute for narrative evidence where qualified review requires it.
Key takeaways
The short version
- Separate current state, terminal outcome, barrier, and next action.
- Use neutral observable labels rather than motivated, bad lead, or noncompliant.
- Distinguish person choice, program decision, payer information, capacity, and contact failure.
- Require source and qualified owner for clinical, coverage, privacy, or safety-related codes.
- Audit code use and reopen records when new information changes the outcome.
1. Treatment center admissions disposition codes taxonomy
| Top-level disposition | Meaning | Example subreasons |
|---|---|---|
| Access completed | Person reached the defined accepted next service | Admitted, first visit arrived, accepted external connection |
| Scheduled or handed off | Next step is accepted but not yet completed | Scheduled, receiving team accepted, referral pending connection |
| Open or waiting | Work remains active with an owner | Payer wait, clinical review, documents, capacity update, person callback |
| Alternate path | A different service or provider is the appropriate next step | Other level, geography, specialty, preference, coverage path |
| Person declined or paused | Person communicated a choice | Not now, selected another option, requested pause, cost concern |
| Unable to connect | No two-way contact after the approved process | Invalid destination, delivery failure, attempts completed, wrong party |
| Closed administrative | Record does not represent active access work | Duplicate inquiry, test, spam, entered in error, transferred episode |
2. Define evidence and fields for every code
- Definition, included and excluded scenarios, examples, top-level outcome, reason, subreason, and allowed combinations
- Current versus terminal use, entry event, minimum evidence, authoritative source, and qualified decision owner
- Required next action, due time, receiving owner, communication expectation, and escalation when unresolved
- Effective date, state or program variation, code owner, version, review date, and retired-code mapping
- Reopen trigger, correction authority, original-value preservation, downstream notification, and reporting treatment
- Sensitivity, role access, minimum-necessary display, export, partner-reporting, and small-group suppression
3. Keep important decision boundaries visible
| Question | Store separately |
|---|---|
| Was the person reached? | Contact status and evidence |
| Is the program administratively plausible? | Routing rule and source |
| What did a qualified reviewer decide? | Clinical or program decision, role, time, and evidence |
| What did the payer source report? | Eligibility, network, benefit, authorization, uncertainty, and verified-at time |
| Was capacity available? | Service, site, modality, capacity state, source, and timestamp |
| What did the person choose? | Stated preference, reason if volunteered, safe follow-up, and timing |
4. Implement codes without corrupting history
- 01
Map
Inventory current labels, free text, reports, workflows, incentives, and downstream dependencies.
- 02
Design
Create a small hierarchy with definitions, required evidence, owner, allowed transitions, and unknown or unresolved states.
- 03
Back-test
Have multiple reviewers code representative historical scenarios and examine disagreements and lost nuance.
- 04
Migrate carefully
Map only defensible legacy values; mark uncertain history unknown rather than fabricating precision.
- 05
Monitor
Review missingness, catch-all use, sudden mix changes, correction, staff variation, source variation, and incentive effects.
5. Use dispositions for access improvement, not blame
- Report count, denominator, cohort maturity, current open work, terminal outcomes, and changed definitions together.
- Segment by program, site, channel, source, payer constraint, time, owner, and barrier only with appropriate privacy safeguards.
- Review movement between states and time in each state, not only final reason frequency.
- Sample source evidence and person-facing communication before acting on a trend.
- Do not compensate teams on favorable disposition mix or let staff hide difficult cases in duplicate, unqualified, or unreachable codes.
Common questions
Answers before you build.
How many admissions disposition codes should there be?+
Use the smallest hierarchy that distinguishes meaningful next actions and outcomes. Keep top-level codes limited, then add governed reasons or subreasons. Too many peer-level codes create inconsistent selection and misleading reports.
Is unqualified a good disposition code?+
It is usually too ambiguous. Distinguish the administrative rule, qualified clinical decision, payer or network constraint, capacity, geography, person preference, other service path, and unresolved information with sources and owners.
Should disposition codes be editable?+
Allow authorized correction and reopening with original value, actor, time, reason, source, version, and downstream notification preserved. Silent overwrite destroys lineage and can corrupt trend analysis.
How should unreachable inquiries be coded?+
Record valid destination, attempts by approved channel and timing, delivery results, safe-contact rules, completed cadence, last action, closure reason, and re-entry route. Keep wrong party and invalid destination separate.
Practical closeout
Use this operator checklist.
- Separate current state, terminal outcome, barrier, and next action.
- Use neutral observable labels rather than motivated, bad lead, or noncompliant.
- Distinguish person choice, program decision, payer information, capacity, and contact failure.
- Require source and qualified owner for clinical, coverage, privacy, or safety-related codes.
- Audit code use and reopen records when new information changes the outcome.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on July 22, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 01Collect and Use Data for Quality Improvement AHRQ Academy for Integrating Behavioral Health and Primary CareOperational measurement guidance covering behavioral-health referrals, warm-handoff completion, time to first appointment, and no-show rates.Accessed or rechecked July 22, 2026
- 02Behavioral Health Navigation Services Offered by Health Insurers HHS Office of the Assistant Secretary for Planning and EvaluationFebruary 2026 environmental scan describing behavioral-health access barriers, navigation models, provider-directory problems, and connection to available care.Accessed or rechecked July 22, 2026
- 03Track Patients and Monitor Their Outcomes AHRQ Academy for Integrating Behavioral Health and Primary CareBehavioral-health guidance on systematic follow-up, registries, no-shows, unscheduled follow-up, nonresponse, outreach channels, and understanding barriers.Accessed or rechecked July 22, 2026
- 04Warm Handoff: Intervention Agency for Healthcare Research and QualityAHRQ implementation resources for transparent, patient-engaged transfers between members of a care team.Accessed or rechecked July 22, 2026
- 05Minimum Necessary Requirement U.S. Department of Health and Human ServicesHIPAA guidance on limiting uses, disclosures, and requests for protected health information when the standard applies.Accessed or rechecked July 22, 2026
- 06Health Plan Eligibility Benefit Inquiry and Response Centers for Medicare & Medicaid ServicesOfficial overview of the HIPAA-adopted X12 270/271 eligibility and benefit transaction.Accessed or rechecked July 22, 2026
- 07Know what your insurance covers Substance Abuse and Mental Health Services AdministrationConsumer-facing overview of behavioral health insurance coverage questions and plan variation.Accessed or rechecked July 22, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
July 22, 2026
Initial publication, source review, and operational editing.