To build an ABA clinical policy and protocol source record, define the purpose, scope, audience, terms, governing sources, decision rights, client and family involvement, communication access, safeguards, required procedures, and exception route. Record evidence, rationale, approval, publication and effective dates, distribution, training, competency, implementation, validation, corrections, supersession, archive, and owner. Keep law, payer terms, professional standards, policy, protocol, and case judgment separately attributable.

Define Faye's clinical policy and protocol source record

Faye creates one controlled source record for each policy family. Forms, scripts, checklists, system rules, training, client notices, and local variants link back to that source rather than becoming independent policies. The record names purpose, scope, source, decision owner, affected people and roles, active version, effective date, access safeguards, evidence, correction path, and proof required before release or closure.

Build Faye's page-specific fields

Faye records policy identifier and title, purpose, scope, audience, excluded scope, definitions, governing sources and dates, evidence and rationale, client and family input, AAC and access, clinical decision rights, organizational authority, payer and jurisdiction boundaries, procedures, hard stops, escalation, exception route, responsible roles, approval, publication, effective and implementation dates, distribution, training and competency, forms and software, monitoring, validation, unwanted effects, correction, next review, supersession, archive, and owner. Every derivative displays the active version and source link.

Connect Faye's policy to real decisions

Faye identifies every decision the policy assigns, the qualified role that owns it, the evidence required, and the point at which work pauses or escalates. Clinical, legal, privacy, payer, employment, safety, and operational decisions remain separately attributable. A policy can guide a role without expanding competence, licensure, contract authority, consent, or case-specific clinical judgment.

Protect client access and ordinary supports for Faye

Faye includes direct client and family input through accessible methods, preserves AAC, and records consent and assent when applicable. Communication, health, safety, mobility, food, water, bathroom access, rest, pain care, prescribed care, and emergency help remain available independent of performance or policy acknowledgment. Client-facing effects receive a usable explanation and response path.

Version Faye's active derivatives

Faye links forms, templates, scripts, checklists, training, software rules, notices, and local variants to the controlled source. Each displays or resolves the active version and effective date. A correction preserves prior content, identifies affected decisions, and creates reconciliation tasks for every site, plan, record, payer package, staff member, client communication, or external report that relied on the earlier version.

Record Faye's deviations and exceptions

Faye records the policy requirement, actual event, reason, immediate safety, person who authorized any deviation, duration, affected clients and work, interim control, and follow-up. A deviation record does not retroactively authorize the action. Repeated deviations trigger policy, training, capacity, access, or system review rather than being treated as isolated paperwork defects.

Reconcile Faye's policy with individual care

Faye checks that policy implementation preserves the active assessment, plan, health and safety information, communication system, client priorities, ordinary supports, and qualified case decisions. A general policy cannot replace individualized clinical evaluation. When the policy and a current case need appear to conflict, the responsible roles pause the affected step, protect immediate needs, preserve the evidence, and route the question without rewriting the client record.

Test Faye's policy in the actual workflow

Faye validates search, interpretation, decision routing, access, system behavior, forms, handoffs, and stop rules under realistic conditions. The test avoids recreating danger or exposing client information unnecessarily. Attendance and acknowledgment are distribution evidence. Performance, safety, accessibility, and outcome require their own measures and denominators.

Work through Faye's fictional example

Faye locks 20 policy source records. Fifteen connect purpose, scope, sources, authority, procedures, approval, dates, implementation, validation, and archive. One lacks client access, one cites an expired payer source, one has no clinical owner, one uses different dates across forms, and one cannot identify which version is active. Four repair; the source-currency file stays held. The example is synthetic and checks source, version, decision, and denominator logic. It does not establish legal compliance, clinical quality, payer approval, competence, safety, client satisfaction, or outcome for another organization.

Calculate Faye's measures honestly

Initial source-record completeness is 15 of 20, or 75.0%. Nineteen validate, or 95.0%. Policies, protocols, forms, sites, staff, clients, and findings use separate counts.

Address Faye's main document-control risk

A polished PDF can hide an uncontrolled rule. Faye traces every active derivative to approval, version, source, owner, and effective date.

Test Faye's record against hard cases

Faye tests new policy, revised protocol, payer rule, local form, software edit, client notice, emergency stop, expired source, archive, and correction.

Review Faye's release handoff

Faye confirms authority, source, scope, version, approval, dates, access, distribution, competency, implementation, local variants, client notice, validation, correction, supersession, archive, owner, and open work before releasing or closing the clinical policy and protocol source record.

Scope Faye's organizational sources

Faye uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management scope. CASP sells the detailed guidelines. The CASP ABA Practice Guidelines public summary is specific to ABA behavioral health treatment for people diagnosed with autism and does not prescribe this policy workflow.

Preserve Faye's professional decision boundary

The BACB Ethics Code applies to covered people and addresses competence, responsibility, client involvement, consent and assent when applicable, confidentiality, documentation, risk, supervision, and evaluation. BACB has no separate organization or corporation jurisdiction. Faye records organizational ownership while preserving each qualified clinician's case-specific duties.

Use Faye's compliance source as guidance

Faye uses the OIG General Compliance Program Guidance to examine governance around the clinical policy and protocol source record. The guidance is voluntary and nonbinding and discusses written policies, training, reporting, response, auditing, corrective action, and oversight. Its framework never validates this specific ABA record or displaces current law, payer terms, contracts, licensing rules, or professional judgment.

Use Faye's implementation tools carefully

Faye uses the AHRQ QI toolkit page for planning, process mapping, PDSA, run-chart, control-chart, and related improvement concepts. The page hosts older primary-care materials. These tools can structure testing, while the practice must validate the policy's fit, sources, clinical safety, accessibility, and effects in its actual settings.

Keep Faye's HIPAA examples within scope

When the clinical policy and protocol source record includes HIPAA-governed material, Faye checks 45 CFR 164.530 for applicable Privacy Rule policy, documentation, complaint, sanction, mitigation, and retention provisions. 45 CFR 164.316 supplies Security Rule policy and documentation duties, including six-year retention for required documentation. Neither provision creates a universal schedule for unrelated clinical, employment, payer, or business policies.

Choose Faye's next review trigger

Faye reopens the clinical policy and protocol source record when a source, law, payer term, clinical finding, client experience, incident, complaint, access need, workflow, site, form, system rule, exception, emergency, unwanted effect, correction, or audit finding changes. The prior version remains available and affected recipients receive the controlled update.

Close Faye's policy record with limits visible

Review the clinical policy and protocol source record with client and family representatives as applicable, qualified clinical and policy owners, and every specialist named in the manifest. Confirm active use, access, safety, source currency, validation, corrections, and unresolved work. Keep the page draft until every named review is complete.

Related resources

Sources