To run an ABA interdisciplinary case conference with client and family participation, prepare the client in an accessible format, confirm who should attend and why, verify authority and privacy, circulate a focused agenda, and make communication and AAC available. During the meeting, separate observations, recommendations, payer states, and decisions. Record authorship, dissent, tasks, owners, due dates, client questions, and follow-up. Meeting attendance alone creates no consent, shared scope, or clinical authority.

Define Orla's interprofessional case conference

Orla designs the conference around decisions the client wants help making. She asks how the person prefers to participate, whether a smaller pre-meeting would help, which topics feel private, who may receive which information, and how the team will pause when clarification is needed. The accessible case-conference record names the client, purpose, workflow, people, authority, scope, access, evidence, decisions, tasks, open work, validation, retention, and review status.

Build the fields Orla needs

The working record captures conference ID, client, representative authority when applicable, participation preference, consent and privacy route, communication and AAC, language and access support, purpose, agenda, decisions needed, attendees and roles, conflicts, evidence links, pre-reading, definitions, facilitator, timekeeper, client advocate or support, observations, recommendations and authors, payer information, decision owners, dissent, unknowns, urgent actions, tasks, due dates, communication, minutes approval or correction, follow-up date, validation, and closure. Structured fields keep people, roles, decisions, dates, tasks, and states searchable. Narrative preserves clinical reasoning, client perspective, uncertainty, disagreement, and context while source records, communications, recommendations, corrections, and audit history remain attributable.

Keep each decision with its qualified owner

Orla separates client and representative choices, clinical recommendations, professional scope, organizational work assignment, payer coverage, privacy, record access, education, employment, reporting, and legal review. A meeting, shared document, coordinator, software rule, or majority vote can route work; it cannot manufacture authority.

Apply Orla's workflow

Orla sends a plain-language agenda and role list. The facilitator names the decision owner before each item, invites the client first when appropriate, checks understanding, and records recommendations in each author's scope. Unresolved questions become assigned tasks rather than vague discussion notes.

Protect participation from meeting mechanics

A crowded video call, inaccessible documents, rapid jargon, missing interpreter, muted AAC user, or surprise attendance can defeat participation. Orla tests access before the meeting, permits breaks and alternative contribution, provides readable materials, honors dissent, and follows the applicable consent process if the person's response changes.

Control changes and urgent action

Orla routes immediate danger, medical emergency, suspected abuse or neglect, privacy incident, and other time-sensitive duties through current authorized paths while coordination continues. A changed client state, preference, role, credential, source, payer action, recommendation, setting, or recipient reopens only affected gates. Interim work carries an owner, authority, start, expiry, communication, and reassessment.

Work through Orla's fictional example

Orla locks 24 case conferences. Eighteen have accessible preparation, appropriate attendees, role clarity, decision boundaries, client input, attributed recommendations, tasks, and follow-up. One lacks AAC backup, one adds an unapproved attendee, one merges payer and clinical decisions, two tasks have no owner, and one set of minutes erases dissent. Four repair. Two remain open. This synthetic example tests workflow and denominator logic. It supplies no clinical, privacy, payer, professional-scope, licensing, reporting, education, contract, or legal conclusion for a real person or organization.

Calculate Orla's measures honestly

Initial conference integrity is 18 of 24, or 75.0%. Twenty-two conferences validate, or 91.7%. Clients, attendees, agenda items, recommendations, decisions, tasks, and follow-ups retain separate denominators.

Address the main interprofessional case conference risk

A meeting can look collaborative while inaccessible participation, hierarchy, vague ownership, or unattributed consensus leaves the client with less control.

Test Orla's artifact against hard cases

Orla tests AAC breakdown, interpreter delay, client decline, family disagreement, school attendee, payer representative, urgent health concern, conflicting advice, and unfinished task. Each case records client choice, access, workflow, authority, professional roles, privacy route, evidence, decision, task, barrier, result, communication, validation, and next review.

Close work with barriers and uncertainty visible

Orla confirms accessible client communication, accepted roles, attributed recommendations, privacy, decisions, open referrals, returned results, task evidence, validation, and residual uncertainty. The interprofessional case conference remains draft until every named reviewer finishes. Open work retains an owner, age, affected people, interim safeguard, and next action.

Place Orla's work inside accountable ABA operations

Orla uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. The ABA Practice Guidelines Version 3.0 public summary concerns ABA behavioral health treatment for people diagnosed with autism and places planning, implementation, and evaluation within standards of care. CASP licenses the details. This interprofessional case conference is an editorial model, not a CASP protocol.

Apply behavior-analyst ethics within its stated scope

The current BACB Ethics Code applies to BCBA and BCaBA certificants and people who completed an application. It addresses competence, understandable communication, client and stakeholder involvement, consent and assent when applicable, confidentiality, assessment, intervention, referrals, service relationships, supervision, risk, and evaluation. BACB has no separate organization or corporation jurisdiction. Orla verifies the law, payer, employer, setting, and other professions separately.

Classify treatment and coordination before sharing PHI

Current 45 CFR 164.501 defines treatment to include specified coordination or management of healthcare and related services, consultation among providers, and referral. 45 CFR 164.506 permits specified treatment, payment, and healthcare-operations uses and disclosures. Orla first confirms entity status, relationship, purpose, and applicable conditions; these provisions do not create professional scope, client consent for care, payer coverage, or a duty for another provider to accept a referral.

Apply minimum necessary with its treatment exception accurately

HHS minimum-necessary guidance says the standard generally applies to covered PHI uses, disclosures, and requests, subject to defined exceptions. Disclosures to or requests by a healthcare provider for treatment are generally exempt, while role-based access rules still govern workforce access. Orla documents the actual route instead of treating collaboration as blanket record access.

Separate representative authority from involved-person communication

Orla uses HHS personal-representative guidance, which says applicable law determines representative authority and scope and describes minor-specific and endangerment rules. Separate HHS family-involvement guidance describes conditions for directly relevant disclosures to a family member, friend, or other person involved in care or payment. Receiving information from someone does not authorize disclosure back or transfer decision authority.

Use interprofessional guidance without transferring authority

ASHA's IPE and IPP resource describes collaboration and teaming for audiologists and speech-language pathologists across health and education settings. Orla uses it as profession-specific collaboration context. It does not define ABA scope, create authority for another profession, guarantee an outcome, or replace client-specific decisions and current governing sources.

Keep communication and AAC available

The ASHA AAC Practice Portal says AAC users should always have access to their tools or devices. Orla records the person's communication form, positioning, vocabulary, partner response, wait time, charging, and backup. Speech, eye contact, or one motor response never becomes the price of participation, and a partner does not author the person's answer.

Use care-coordination measurement as a broad framework

The AHRQ Care Coordination Measures Atlas Update was updated in 2014, notes that no single consensus definition had fully evolved, and organizes coordination activities and measures across patient or family, professional, and system perspectives. Orla uses that dated federal resource for broad measurement orientation, not as a current ABA mandate, legal standard, or proof that coordination improves an outcome.

Related resources

Sources