How does a weekend switch from Atlas MD work?

By ZunovaMD editorial team. Clinical review: pending.

Published . Updated . 5 min read.

All posts
A medical assistant works on a laptop at the front desk of an empty clinic waiting room, with file boxes stacked beside her

Illustrative image, AI-generated

The short answer

In the ZunovaMD pilot plan, a clinic switches in four days: export Friday, review Saturday, cut over Sunday, live Monday. Demographics, problems, medications, allergies, immunizations, inventory and memberships move. Payment tokens move vault to vault, so no patient re-enters a card. Notes kept only as PDF files stay documents, and a pre-import snapshot is held for seven days.

The reason clinics stay on software they have outgrown is rarely the software. It is the switch: a lost month, a receptionist re-keying charts, and six hundred patients asked to re-enter a credit card. So we designed the switch first and are building the product around it. This is the plan for clinics joining the ZunovaMD pilot from Atlas MD or any other system.

What has to be in place before the weekend?

Two things, and both are about your data.

First, a business associate agreement (BAA) with us, signed before any export moves. Under the HIPAA Privacy Rule, a contract with a business associate, such as a software vendor that holds your records, must require it to return or destroy the protected health information it still holds when the contract ends, where that is feasible 1. The same rule in 45 CFR 164.504 covers the vendor you are leaving, so ask how it will return your data and confirm what it destroys.

Second, an export. If your current system is certified for electronic health information (EHI) export under the federal health IT certification program, that criterion requires the software to export all of one patient's EHI, or the whole patient population's, in a computable format, with a public link that explains the format 2. The text is in 45 CFR 170.315(b)(10). Developers of certified health IT are also "actors" under the information blocking rules of the 21st Century Cures Act, along with health care providers and health information networks 3. Not every system a DPC clinic uses is certified, so ask your vendor what its export includes.

What happens on Friday?

You run the exports from your current system. We send step-by-step instructions for the system you are leaving, because the clicks change. The import is designed to take demographics, problems, medications, allergies, immunizations, inventory counts and memberships.

In the pilot plan, your workspace is ready before Friday. It applies your state's dispensing rule profile, where your state allows dispensing, and it holds your templates and your clinic phone number. A dry-run import is designed to report every row it could not place and why.

What happens on Saturday?

The plan budgets about two hours for your medical assistant in the reconciliation queue. Each flagged row is a small decision: accept, merge with an existing record, or reject. Nothing enters the chart without that pass.

The plan moves recurring payment tokens vault to vault between payment processors. Card numbers are designed never to touch our systems, and no patient is asked for anything. We also print a few test labels on your thermal printer and adjust the label template before anything is dispensed.

What happens on Sunday and Monday?

On Sunday you forward the clinic number and tell patients that nothing changed except the app. Aria, the triage agent we are building, is planned to take the first overnight; why DPC doctors still get texts at 2 a.m. explains what it is designed to do with that queue.

The plan holds a snapshot from before the import for seven days, and one click is designed to revert to it. You keep your old system until you cancel it. The HIPAA Security Rule already requires a data backup plan that keeps retrievable exact copies of electronic protected health information, and a disaster recovery plan to restore lost data 4. The cutover snapshot is one more copy for the weekend. It does not replace either plan.

On Monday you open the cockpit to a triage queue, sign what needs you, and dispense from the note where your state allows it. The plan keeps someone from our team on a shared channel with you all week.

What does not move?

Old notes that exist only as PDF files stay as documents. Where you want them, the plan extracts problems, medications and allergies from those PDFs into a review queue, and your team accepts or rejects each one. We do not silently turn a scanned page into structured data.

Your duties to patients do not pause for the move. Under the HIPAA right of access, a clinic must act on a patient's request for their records no later than 30 days after it arrives, with one extension of up to 30 more days allowed 5. Records requests and lab results: the deadlines a clinic must meet covers the details.

What is ZunovaMD building?

ZunovaMD is in pilot and enrolling direct primary care and rural clinics in Arkansas, Texas and Kansas, and this switch plan is how pilot clinics are designed to come aboard. Imported records are used to run your clinic. They are never used to train AI models, de-identified data included. The full switch plan, day by day has the checklist, the comparison page sets the systems side by side with dated citations, and our security page covers how the data is held.

Questions

Do patients have to re-enter their credit cards when a clinic switches?

Not in the ZunovaMD plan. Recurring payment tokens are designed to move vault to vault between payment processors, so card numbers never touch ZunovaMD's systems. No patient is asked to re-enter a card.

What if something goes wrong after cutover?

The ZunovaMD plan holds a snapshot from before the import for seven days, and one click reverts to it. The clinic also keeps its old system until it cancels it.

Do old PDF notes become structured data?

Not on their own. Notes that exist only as PDF files stay as documents. If the clinic wants, problems, medications and allergies are pulled into a review queue, and staff accept or reject each item.

Does the old software vendor have to give our data back?

Under HIPAA, a business associate agreement must require the vendor to return or destroy the protected health information it holds when the contract ends, where feasible. If the vendor's software is certified for electronic health information export, it must be able to export all of one patient's data, or the whole patient population's, in a computable format.

Will imported records be used to train AI models?

No. ZunovaMD does not train models on patient data, and that includes de-identified data.

Sources

  1. Legal Information Institute, Cornell Law School: 45 CFR § 164.504, Uses and disclosures: Organizational requirements (business associate contracts), checked 2026-10-26
  2. Legal Information Institute, Cornell Law School: 45 CFR § 170.315, ONC certification criteria for Health IT (paragraph (b)(10), electronic health information export), checked 2026-10-26
  3. ASTP/ONC (HHS), Information Blocking, checked 2026-10-26
  4. Legal Information Institute, Cornell Law School: 45 CFR § 164.308, Administrative safeguards (contingency plan), checked 2026-10-26
  5. Legal Information Institute, Cornell Law School: 45 CFR § 164.524, Access of individuals to protected health information, checked 2026-10-26

Not medical advice. This post is general information about running a clinic and the software behind it. For a question about your health or a patient's care, ask a licensed clinician.

You've tried the workarounds.This one runs itself.

Thirty minutes on a clinic like yours: the overnight queue, a visit with the scribe on, a dispense from the note and a state report. Bring an export and we run the dry-run import while we talk.