Build an ABA Clinical Documentation Data Dictionary and Controlled Vocabulary

Define Hana's versioned clinical data dictionary

Hana starts with decisions users must make, then defines the minimum fields needed to support them. She avoids collecting a field simply because another system has one with a similar label. The unit names the person, event, source, purpose, responsible role, effective period, downstream systems, unresolved work, and closure evidence. This prevents a complete status from hiding an identity, access, clinical, privacy, or payer gap.

Build Hana's page-specific control record

Hana records field name, human label, definition, purpose, record class, source, authoring role, data type, unit, format, allowed values, null meanings, required conditions, validation, default, clinical owner, technical steward, privacy class, access roles, effective version, deprecated value, replacement, transformation, API and export mapping, display language, correction route, and test case. Unknown, not asked, declined, not applicable, and unavailable remain different states.

Put Hana's control into daily use

Hana publishes the dictionary as a versioned product with an approval history and test library. Every proposed field change includes the decision it supports, affected workflows, migration rule, display copy, API mapping, training need, and rollback plan. A change from optional to required identifies how older records and legitimate unavailable states will behave. A renamed value keeps its earlier meaning for historical reports unless an authorized transformation is documented. Hana pilots new definitions with clinicians, direct users, records staff, and people who rely on accessible or translated displays. She checks that different users classify the same examples consistently and that the choices preserve client language. The release notes state which calculations, forms, templates, reports, integrations, and exports changed. Monitoring looks for unusual nulls, invalid combinations, sudden category shifts, free-text workarounds, and mapping failures. Retirement occurs only after active records, offline forms, imports, downstream reports, and external recipients have a supported replacement. Corrections reference the definition version that governed the original record and the version used for the repair.

Protect client access and clinical meaning in Hana's workflow

Hana keeps accessible communication, AAC, language and disability access, consent and assent when applicable, dissent, privacy, health, safety, client priorities, ordinary supports, and source attribution visible. Administrative, technical, payer, or audit completion does not determine clinical appropriateness. Immediate safety action and mandated duties follow their own current routes.

Work through Hana's fictional example

Hana reviews 52 shared fields. Forty-one have approved definitions and tests. Five use the same label for different concepts, three have undocumented null behavior, two mix minutes and hours, and one active value has no current owner. She blocks a new export mapping until the eleven gaps are resolved. This fictional cohort teaches evidence and denominator discipline. It does not set a treatment, privacy, payer, coding, billing, legal, retention, accessibility, or technical standard.

Keep Hana's denominator honest

Dictionary readiness is 41 of 52 fields, or 78.8%. After eight validate, readiness is 49 of 52, or 94.2%. Three open fields remain visible by defect and downstream use. A field with two defects still counts once in the field-level denominator and twice in the issue count.

Assign Hana's decisions to the right roles

Qualified clinicians approve clinical terms, response definitions, and interpretation boundaries. Clients and families help test understandable labels and meaningful options. Privacy and compliance leaders govern sensitive purpose and access. Engineers implement constraints and mappings. A vendor's code list is evidence, not automatic clinical authority.

Address Hana's main failure mode

A controlled vocabulary can erase nuance when it forces one category on changing, contextual, or self-described experience. Provide an attributable narrative or client-language field and review whether a code supports the intended decision.

Validate Hana's control with real transitions

Hana tests every value, null, unit, boundary, retirement, import, export, correction, and display. She gives the same cases to two trained users and checks whether the definition produces consistent classification without suppressing important context.

Place Hana's clinical and organizational sources correctly

Hana uses the CASP public overview only for high-level organizational context. The BACB Ethics Code applies to BCBA and BCaBA certificants and applicants as defined by the Code; BACB has no separate jurisdiction over organizations or corporations. These sources support accountable roles, documentation, confidentiality, client involvement, assessment, intervention, supervision, and correction boundaries. They do not approve this workflow, create legal authority, or replace state, payer, employer, and role-specific rules.

Apply Hana's payer evidence boundary carefully

Hana treats the current CMS Program Integrity Manual, Chapter 3 and Medicare signature guidance as Medicare medical-review materials. Chapter 3 currently says services are expected to be documented when rendered; delayed or corrected entries may occur; the date and author should be identifiable; and a change or addendum should be clearly and permanently noted. These materials do not establish one universal ABA documentation, signature, payer, or state rule.

Use Hana's privacy purpose and access routes separately

Hana applies HHS minimum-necessary guidance to applicable uses, disclosures, and requests while preserving its treatment exceptions and entity scope. The HHS access guidance addresses an individual's HIPAA access right to a designated record set, subject to the rule. HHS TPO guidance and 45 CFR 164.508 describe distinct disclosure pathways. Verify covered-entity or business-associate status, purpose, authority, recipient, data, and other law rather than making one generic release form the answer.

Protect Hana's data and communication context

Hana uses the current HHS Security Rule overview for regulated ePHI safeguards and the HHS de-identification guidance for its two HIPAA methods and residual-risk boundary. The DOJ Title III overview covers equal opportunity, effective communication, and reasonable modifications for covered public accommodations. ASHA's AAC portal says AAC users should always have access to their tools or devices. Entity scope, state law, professional duties, contracts, and the particular data use still require separate review.

Choose Hana's review triggers

Hana reopens the versioned clinical data dictionary after a new system, field, record class, interface, vendor, site, role, payer, law, policy, access request, client preference, identity conflict, correction, outage, disclosure, incident, or audit finding. The review records the changed fact, affected people and records, immediate safeguard, accountable owner, due date, corrected source, downstream propagation, communication, and independent validation.

Finish Hana's review without losing open work

Review the versioned clinical data dictionary with the people whose records and communication are affected, qualified clinicians, health-information and privacy leaders, and the specialists named in the manifest. Confirm source, identity, encounter, author, version, purpose, authority, access, client message, downstream use, exception, and validation evidence. Keep unresolved work visible and keep this page draft and noindex until every required external review is complete.

Related resources

• Normalize ABA Clinical Dates, Times, Time Zones, Locations, and Identifiers.
• Merge, Unmerge, and Correct Duplicate ABA Client Records Safely.
• Govern Photos, Audio, Video, Screenshots, and Recordings in ABA Clinical Records.
• Prevent Wrong-Client, Wrong-Encounter, and Duplicate ABA Clinical Records.

Sources

• Council of Autism Service Providers, Organizational Guidelines public overview.
• Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
• Centers for Medicare & Medicaid Services, Medicare Program Integrity Manual, Chapter 3.
• Centers for Medicare & Medicaid Services, Complying With Medicare Signature Requirements.
• U.S. Department of Health and Human Services, Minimum Necessary Requirement.
• U.S. Department of Health and Human Services, Individuals' Right Under HIPAA to Access Their Health Information.
• U.S. Department of Health and Human Services, Guidance Regarding Methods for De-identification of Protected Health Information.
• U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
• Electronic Code of Federal Regulations, 45 CFR 164.508.
• U.S. Department of Health and Human Services, HIPAA Security Rule.
• U.S. Department of Justice, Businesses That Are Open to the Public.
• American Speech-Language-Hearing Association, Augmentative and Alternative Communication.