An ABA schedule source discrepancy exists when two records disagree about a fact needed to plan or release care. Resolution preserves both values, identifies each source and timestamp, assigns authority by field, protects affected visits, obtains the qualified decision, corrects the owning system, communicates the verified result, and confirms downstream consistency. The workflow keeps uncertainty visible instead of choosing the newest or most convenient value automatically.

Capture the disagreement without overwriting it

Record the field, value A, source A, timestamp A, author or system, value B, source B, timestamp B, affected visit IDs, discovery time, and reporter. An ABA schedule source discrepancy should remain reviewable even after correction. Avoid copying one value over another before the owner sees the evidence. If the discrepancy involves several fields, split them when different authorities or sources apply. A wrong time and a wrong staff assignment may need separate decisions.

Assign authority by field

Build a field-authority map for client preferences, clinical service and risk information, staff qualifications, supervisor assignment, payer status, facility availability, access supports, work availability, and schedule status. One database rarely controls every fact. A source can be authoritative for its own field and still contain a stale copy of another field. Name the role that may decide, the system that should store the result, the evidence required, and the escalation route when sources remain unresolved.

Protect affected visits

Classify the discrepancy by potential consequence. A cosmetic label may allow scheduling to continue, while a client identity, date, service, clinical prerequisite, staff qualification, access support, or location mismatch may require a hold. Define the hold scope narrowly around affected visits and fields. Preserve emergency and mandated-reporting routes. Give the person and staff timely operational information without exposing internal speculation or presenting an unresolved value as confirmed.

Keep clinical decisions attributable

The BACB Ethics Code supports competence, client involvement, documentation, risk management, and qualified professional accountability for covered people. When clinical records disagree with a scheduling copy, route interpretation and any clinical change to the qualified clinician. Operations may correct the calendar after receiving that decision. Software can surface inconsistency, link evidence, and hold release, while it should not infer dosage, risk, goals, or treatment fit.

Treat payer statements as scoped evidence

HealthCare.gov cautions that preauthorization does not promise cost coverage. When a portal, letter, call note, contract, or internal tracker disagrees, record product, member, service, provider configuration, period, units, source date, representative or document, and reference number. Route unresolved payer meaning to the authorized payer-operations owner. Keep coverage, authorization, scheduling, claim acceptance, adjudication, and payment distinct.

Protect the data during investigation

First classify the organization and information. For HIPAA covered entities and business associates, the HHS Security Rule overview frames safeguards for electronic protected health information. Limit case access by role, use approved channels, preserve audit logs, and avoid spreading screenshots across chat or personal storage. A discrepancy ticket can link to restricted evidence and carry only the operational details each participant needs.

Correct the owning source first

Once the authorized owner establishes the value, update the system responsible for that field through its normal correction process. Preserve authorship, date, reason, prior value, and effective time. Then propagate the correction through approved integrations or linked tasks. A direct edit in every downstream system can create ten new sources of truth. If urgent operations require a temporary override, label it, limit its scope, set an expiration, and create a task to reconcile the owner system.

Set evidence standards by discrepancy type

A staff availability conflict may be resolved through the approved workforce record, while a clinical-service conflict needs qualified clinical documentation and a payer-period conflict needs the current payer source. Define the acceptable evidence, responsible reviewer, and expiration for each field class. A phone call, portal screenshot, signed record, interface event, and system timestamp carry different meaning and scope. Avoid declaring one evidence format universally strongest. The field-authority map should explain what establishes the fact for that workflow and when written clarification or specialist review is required.

Manage discrepancies discovered during a session

If staff discover a material mismatch at arrival or during care, route immediate safety and clinical concerns through the applicable procedures. Record actual date, time, location, staff, service, and events accurately. Avoid changing the calendar after the fact to make it match a planned record. The qualified clinical role decides whether care can continue when clinical prerequisites are unclear; operations handles schedule status and follow-up within policy. Create linked correction, incident, payer, or workforce work as applicable. Preserve the difference between what was planned, what was known at the time, and what actually occurred.

Use temporary truth labels carefully

Some workflows need a current operational value while the underlying conflict remains open. Label it as provisional, cite the approving owner and evidence, limit the affected fields and visits, and set an expiration or recheck trigger. Show the unresolved source conflict beside the temporary value to authorized reviewers. Provisional data should never silently feed broad reports or permanent templates. When the final decision arrives, compare it with the temporary value, correct all linked records, notify affected people, and record whether the temporary state caused any service, communication, payroll, or payer consequence.

Create a safe merge rule for duplicates

Two records may describe the same real visit while carrying different identifiers or histories. Confirm identity through the approved matching fields before merging. Choose which record survives, preserve both audit trails, reattach communications and downstream references, and block the retired identifier from reuse. If identity remains uncertain, keep both records held and route the question rather than merging by similar names and times. After resolution, search for linked exports, claims, notes, and staff calendars that may still reference the retired record and reconcile each one.

A fictional discrepancy queue

Blue Heron ABA reviews 16 discrepancies. Six come from stale family availability, four from staff changes, three from payer dates, two from room records, and one from a clinical-service mismatch. Thirteen reach verified correction within two business days, so timely resolution is 13 of 16, or 81.3%. The three open rows remain aged in the original cohort, and the clinical mismatch stays held for qualified review.

Communicate the verified result

Tell affected people the final date, time, service, location, staff configuration, or next step through the appropriate channel. Record sent, delivered, acknowledged, and correction-needed states. Avoid sharing internal blame. When the discrepancy changed a previously communicated schedule, say clearly which version is current and what happened to the prior appointment. Link any client or staff response to the corrected record and reopen the workflow if they identify another conflict.

Measure both resolution and prevention

Report discrepancies received, fields affected, severity, source pair, time to hold, time to verified decision, time to propagated correction, open age, client impact, and recurrence. Measure complete reconciliation as corrected downstream records divided by records due for correction. Review patterns by integration, manual handoff, team, and field. A short resolution time can coexist with recurring defects, so pair speed with root-cause fixes and repeat rates.

Related resources

Sources