To build an ABA interprofessional collaboration and referral governance system, define each workflow, client choice, legal authority, professional scope, clinical authorship, privacy route, access support, evidence, decision owner, handoff, and closure rule. Link consultations, conferences, shared goals, and referrals without merging their records or authority. Track open barriers, conflicting advice, urgent action, client communication, follow-through, validation, and recurring system gaps.

Define Kora's interprofessional collaboration and referral governance system

Kora starts with the client and the decision that needs support. A request to consult an SLP, coordinate with a physician, join a school meeting, refer for a vision evaluation, or transfer care can involve overlapping people while creating different services, records, permissions, and duties. The collaboration governance register names the client, purpose, workflow, people, authority, scope, access, evidence, decisions, tasks, open work, validation, retention, and review status.

Build the fields Kora needs

The working record captures case and workflow ID, client and legally authorized representative when applicable, involved people, priorities, assent and dissent when applicable, communication and AAC, language and disability access, purpose, question, urgency, governing sources, professional roles, scope, competence, clinical authorship, privacy route, consent, payer state, evidence, receiving party, deliverable, task owner, due date, disagreement, provisional action, referral state, result, review, communication, barrier, validation, recurrence, retention, 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

Kora 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 Kora's workflow

Kora publishes entry and exit rules for consultation, case conferences, co-treatment, referrals, record exchange, shared-goal coordination, and transfer. Every participant accepts a bounded role. The treating professional keeps case-specific judgment within scope, and the client keeps the choices and rights supplied by the governing source.

Make collaboration governable without making it rigid

The register provides enough structure to prevent lost tasks, silent assumptions, and role drift while leaving qualified professionals room for case-specific judgment. It records what each participant contributed, what remains uncertain, and who decides. Urgent medical, safety, protective, privacy, and reporting routes continue on their own clocks.

Control changes and urgent action

Kora 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 Kora's fictional example

Kora locks 27 collaboration cases. Twenty have a defined workflow, client route, qualified roles, scope, privacy, evidence, task owners, communication, and closure evidence. One lacks a clinical decision owner, one meeting lacks AAC access, two referrals have no receiving status, one payer condition is mistaken for clinical advice, and two tasks lack validation. Four repair. Three 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 Kora's measures honestly

Initial governance integrity is 20 of 27, or 74.1%. Twenty-four cases validate, or 88.9%. Clients, workflows, meetings, recommendations, referrals, tasks, and results retain separate denominators.

Address the main interprofessional collaboration and referral governance system risk

A friendly team can still fail a client when authority, access, authorship, privacy, task ownership, and follow-through remain implicit.

Test Kora's artifact against hard cases

Kora tests a medical concern, AAC consultation, school meeting, mental-health referral, payer request, family disagreement, missing result, urgent safety event, consultant conflict, and transfer. 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

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

Place Kora's work inside accountable ABA operations

Kora 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 collaboration and referral governance system 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. Kora 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. Kora 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. Kora documents the actual route instead of treating collaboration as blanket record access.

Separate representative authority from involved-person communication

Kora 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. Kora 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. Kora 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. Kora 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