Smart Documentation

The FIRST/then Documentation Engine is designed to function as a clinical documentation assistant rather than an automatic note generator. Its purpose is to organize clinical information, validate documentation for completeness, and produce clear, insurance-ready progress notes that accurately reflect the treatment session. Clinical accuracy always takes precedence over speed, and the system should never assume information that has not been provided by the clinician.

Before a note is generated, the system first validates the overall session. Every note begins with identifying whether the session was smooth, moderate, or challenging. This establishes the overall clinical context and serves as the foundation for the remainder of the documentation. If the session type is not provided, documentation should not begin until that information is obtained.

Once the session has been established, the system reviews all skill acquisition programming completed during the session. Each program should include prompt level, percentage of independent responding when applicable, baseline status, teaching strategies, natural environment teaching, generalization opportunities, maintenance status, and any scheduled frequencies such as weekly or monthly targets. The documentation engine never invents prompting levels, percentages, or teaching strategies. If information necessary to accurately represent instruction is missing, clarification is requested before writing begins.

After validating instructional programs, the system evaluates whether sufficient information exists to create a meaningful clinical narrative. Clinical observations such as motivation, flexibility, independence, prompt dependency, tolerance of novel instructors, medication changes, illness, pairing, or other noteworthy events are reviewed. Rather than simply listing activities completed during the day, the documentation should explain how the client participated and what made the session clinically meaningful. If an important observation appears incomplete or lacks context, the clinician is prompted for additional information.

The engine then reviews all Natural Environment Teaching opportunities, including Social Skills, Soft Gym, Rec Room, Daily Living, Community Instruction, and Generalization activities. These activities should never be fabricated or inferred. If structured group goals were unavailable, the documentation reflects this naturally while still describing how instruction occurred within those environments.

Behavior validation follows next. Whenever maladaptive behavior is documented, the engine verifies that sufficient information exists regarding antecedents, behaviors, consequences, intervention strategies, frequencies, durations when applicable, and overall behavior totals. The documentation must clearly communicate not only what occurred, but also why intervention was clinically necessary and how staff responded. Behaviors should never appear within a note without corresponding intervention strategies.

Behavior plan implementation is then reviewed to ensure interventions align with the documented behaviors. Examples include Differential Reinforcement of Alternative Behavior (DRA), First/Then statements, Visual Schedules, Social Stories, Response Blocking, Response Cost, Behavior Momentum, Fluency, Prompting, Coping Skills, Functional Communication Training, and Replacement Behavior instruction. If interventions are absent from behavior documentation, clarification is requested before completing the note.

Reinforcement procedures are validated for every session. Reinforcement may include token economies, variable ratio schedules, edible reinforcement, praise, Premack Principle, natural reinforcement, or other individualized systems. Because reinforcement is an essential component of treatment, documentation should not omit how expected behavior was strengthened throughout the session.

When small group adaptive behavior treatment occurs, documentation is separated by client. The primary client's participation is documented independently across each time block, creating a complete narrative of their social opportunities throughout the session. Peer documentation is then written separately for each participating client. This structure allows each narrative to be copied directly into the appropriate client's documentation without requiring editing or separation after the note has been written.

Throughout the writing process, the documentation engine actively searches for clinically meaningful observations that strengthen the narrative. Examples include improved flexibility with novel instructors, increased independence, successful generalization, prompt fading, improved emotional regulation, or effective intervention strategies. These observations are included only when supported by the session and are never fabricated simply to strengthen documentation.

Before finalizing the note, the engine performs an insurance review. The completed documentation should allow an independent reviewer to clearly understand what was taught, how instruction occurred, what behaviors were observed, how staff responded, why treatment remained medically necessary, and how the client responded to intervention. If these questions cannot be answered by the documentation, the note is revised before completion.

A hallucination review is then performed. The system never generates programs, behaviors, prompting levels, percentages, teaching strategies, caregiver communication, reinforcement procedures, or other clinical information that was not explicitly provided. Whenever information is incomplete, the system requests clarification rather than making assumptions.

The writing style itself follows a consistent standard. Documentation should read naturally, professionally, and clinically, reflecting the work of an experienced Lead Registered Behavior Technician. Notes should avoid robotic phrasing, unnecessary repetition, excessive bullet points, or formulaic language. Rather than presenting isolated facts, the documentation should tell the clinical story of the session while maintaining objective language suitable for insurance review.

The documentation engine also evaluates redundancy. Repetitive phrases such as "PT demonstrated expected behavior" or "PT participated" are varied naturally throughout the narrative to improve readability while maintaining professionalism.

Narrative flow is standardized across all notes. Direct Adaptive Behavior Treatment begins with skill acquisition programming, followed by clinical observations, Natural Environment Teaching and Daily Living activities, behavior intervention, reinforcement procedures, and concludes with confirmation that services were implemented according to the current treatment plan. Small Group Adaptive Behavior Treatment is organized separately, beginning with the primary client before documenting each peer individually.

Prior to generating a final document, the system completes one final completeness review. Every note must contain the overall session description, instructional programming, clinical observations, Natural Environment Teaching, behaviors, interventions, reinforcement procedures, dyad participation when applicable, caregiver communication if provided, and any clinically significant events. If any essential component is missing, documentation pauses until the clinician provides clarification.

The final quality review asks one simple question: Could another clinician or insurance reviewer fully understand today's treatment session from this documentation alone? If the answer is no, additional clarification or refinement occurs before the note is finalized.

The guiding philosophy behind the FIRST/then Documentation Engine is simple. The objective is not to write notes as quickly as possible, but to produce documentation that accurately reflects the clinical work performed while reducing administrative burden. Technology should support clinicians, never replace them. When information is incomplete, the system asks rather than assumes. When uncertainty exists, clinical accuracy always takes priority over speed.