ABAFREQUENTLY ASKED QUESTIONS
Clear answers before you connect anything.
Understand what ABASyncPoint coordinates, where it fits, and how evaluation and protected-data boundaries work.
What does ABASyncPoint help an ABA organization run?
ABASyncPoint coordinates referral-to-care work, authorization readiness, capacity and staffing signals, constraint-aware scheduling, reports, meetings, priorities, decisions, commitments, and accountable follow-through across markets.
Does ABASyncPoint replace our EMR?
No. The EMR remains the authoritative clinical record and official schedule. ABASyncPoint is the operating layer that makes cross-functional constraints, readiness, decisions, ownership, exceptions, and follow-up visible.
Can our team evaluate the platform before connecting protected systems?
Yes. The evaluation workspace uses fictional scenarios and synthetic records so teams can validate workflows, stages, assignments, forms, timers, scheduling decisions, reports, and operating rhythms without entering patient information.
Where can patient information be processed?
Patient-level workflows belong only in the separately controlled protected environment after contractual, security, identity, infrastructure, and release gates are approved. The public site and synthetic workspace must never receive protected health information.
How are integrations activated?
Approved connections are enabled customer by customer only after purpose, vendor capability, authorization, credential handling, data boundaries, testing, and release controls are verified. A listed integration is not a claim that it is live.
Does ABASyncPoint connect to or control Blossom’s Monday or Make systems?
No. Those are Blossom-managed external comparison systems. ABASyncPoint has no credentials, API, webhook, import, export, configuration, scenario-control, health-check, or shutdown capability for either system.
Is scheduling automatic?
ABASyncPoint can build and explain proposals using authorization, qualification, availability, supervision, travel, continuity, and pairing constraints. A designated person still approves, rejects, or overrides a proposal before an official scheduling change.
Do customers buy individual modules?
No. Customers purchase the complete ABASyncPoint operating layer. Activation is sequenced through controlled implementation waves so the organization can validate each workflow without fragmenting the operating model.
Who is ABASyncPoint built for?
The initial focus is growing and multi-state ABA organizations with established source systems, multiple markets or clinics, meaningful intake volume, staffing pressure, and leaders seeking consistent operating accountability.
Who uses the Coverage Map?
Coverage Map is available for guided pilots with operations leadership, intake, scheduling, recruiting, authorization teams, and approved administrators. BCBAs may receive limited approved views, while broad RBT access is excluded initially.
Is artificial intelligence making clinical or scheduling decisions?
No. ABASyncPoint applies explicit constraints and explainable ranking to operational proposals. Named people approve decisions, and the EMR remains authoritative for the official clinical record and schedule.