Avoiding Vendor Lock-in: The Single-Tenant Advantage for ABA Practices

You avoid EHR vendor lock-in by getting the exit in writing before you sign. The contract should promise full exports of clinical, billing and operational data, in a documented format, on request at any time. It should also state the notice period, any fees and what happens to your data after you leave.

Lock-in rarely comes from one bad clause. Years of session data, treatment plans, authorization history and claims build up in your EHR. The longer you stay, the more that history is worth, and the harder it is to move. The best time to negotiate portability is the sales process, when the vendor still wants your signature.

How does vendor lock-in happen in an EHR?

Vendor lock-in happens when leaving a system costs more than staying, even when staying is the worse choice. In an EHR, most of that cost hides in the data. A practice can own its records on paper and still find them hard to move. The usual traps look like this:

• Partial exports: demographics come out, while session data, graphs or authorization history stay behind.
• Undocumented files: exports arrive without column names or a data dictionary, so nobody can map them.
• Exit charges: a fee for the export itself, or for the services needed to produce it.
• Short windows: access ends on the termination date, before the new system is ready.
• Broken links: claims arrive without the sessions and authorizations behind them.

Architecture shapes how cleanly a vendor can hand data back. In a shared multi-tenant system, your records sit in a database used by many organizations. An export is a filtered extract from that shared store. Our comparison of single-tenant and multi-tenant EHRs covers the architecture itself, while this post stays on the exit.

What should the contract say about data exports?

The contract should name what you get, in what format, how often and at what cost. A line such as "your data is yours" is a start, not a commitment. Ask for each of these points in writing:

• Scope: clinical, billing and operational data, including session data, treatment plans, authorizations, claims and payments.
• Format: a named file format, with header rows and a data dictionary that explains each field.
• Frequency: exports on request at any time during the contract, not only at termination.
• Exit timing: how much notice you must give and how long access lasts afterward.
• Fees: whether an export or an exit carries any charge.
• The vendor's copies: what happens to the data the vendor still holds once you leave.

Why does the file format matter?

CSV is the common answer, and a sound one, because almost every spreadsheet and database tool reads it. The format is looser than many buyers assume. RFC 4180, the memo that documents CSV, says it does not specify an Internet standard. Under that memo, even the header line that names each column is optional. Ask for header rows, consistent client identifiers across files and a written description of every field.

Billing data has a second layer. Claims travel as standard 837P transactions, so a vendor that can reproduce them gives your next system a clean starting point. In Lumenality, claims go out through the built-in Stedi clearinghouse integration. Claims can also be produced as standard 837 files or a CMS-1500.

What does HIPAA require when a vendor relationship ends?

HIPAA requires your business associate contract to cover the end of the relationship. Under 45 CFR 164.504(e), the contract must require the vendor, if feasible, to return or destroy the protected health information it still holds. The vendor must keep no copies. Where return or destruction is not feasible, the contract's protections extend to that information. Read the termination clause in your BAA next to the export clause in the main agreement.

Return or destruction is about the vendor's copies, not your access. A vendor can meet that rule and still hand you files that are hard to use. Portability terms therefore belong in the service agreement itself.

How long do you need records after you switch?

You need old records for as long as your retention duties run, which usually outlasts any EHR contract. The BACB Ethics Code for Behavior Analysts asks behavior analysts to follow all applicable requirements for retaining and destroying documentation. Code 2.05 says those duties remain with the organization when a behavior analyst leaves. Code 4.05 sets at least 7 years for supervision documentation, and laws or funders can require more.

Plan where the archive will live before you give notice. A complete export, kept under your own access controls, lets you answer a payer audit or a records request long after the old contract ends.

How does a single-tenant deployment help at exit?

A single-tenant deployment helps because your data already sits in its own database. In Lumenality, every practice gets a dedicated deployment with its own database and its own encryption keys. Your records are not mixed with other organizations' records, so the boundary of what belongs to you is clear from day one.

Lumenality's exit terms are written to match that design:

• Full CSV exports of clinical, billing and operational data, on request at any time.
• The same exports when a practice leaves, with 30 days' notice.
• No exit fees.
• 23+ built-in reports with CSV export, for the numbers you check every week.

The terms sit on our pricing page next to the plans. Security controls come with the same deployment: AES-256 encryption at rest, TLS 1.2+ in transit, role-based access control and MFA. Every customer also gets an audit trail of record access and a signed BAA. Our deep dive on single-tenant EHR security explains those controls in more detail.

What does switching into a new EHR look like?

Portability runs in both directions, so ask how a vendor brings data in as well as out. Most practices go live on Lumenality in about 2 to 6 weeks. The path covers the agreement and BAA, a data-migration assessment, 3 to 5 days of staff training and a one-day go-live. Import scope is confirmed after we review sample exports from your current system, and some data may need re-keying.

Hold every vendor to the same standard. Ask which records will move, which will not and who checks the counts before go-live. For the cost side of a future switch, read why single-tenant delivers long-term value. Our guide on how to choose an EHR for a small ABA practice puts these contract questions in order.

A short checklist before you sign

• Export scope covers clinical, billing and operational data.
• The format is named, with header rows and a data dictionary.
• Exports are available on request, not only at exit.
• Notice period, access window and fees are written down.
• The BAA states what happens to the vendor's copies.
• Your retention plan names where the archive will live.

*This article was created with AI assistance and reviewed by the Lumenality team.*