ChartSwap medical records to Clio named for demand day
Personal injury firms request records from providers, hospitals, imaging centers, and billing departments through services like ChartSwap, and download the fulfilled records from a web portal when the notification arrives. The failure mode isn't the retrieval; it's what happens next: records land in a Downloads folder under whatever name the portal assigned, and three months later nobody can say which chart belongs to which client. Send to Case files portal downloads straight into the right Clio matter the day fulfillment lands, so every production is in the case file — named by provider, date range, and record type — long before you sit down to build the demand package.
The records-portal-to-matter problem
The fulfillment notification arrives. What happens in the next ten minutes decides whether the records are findable at demand time.
The request was fulfilled weeks ago. Here's where the records went:
With Send to Case, the day the notification arrives:
The service gets you to fulfillment — the filing is still yours
A records service solves the first half of the records problem. Whether it's a full-service retrieval company that chases providers on your behalf or a request-and-delivery platform like ChartSwap, the service's job ends the same way: the request is fulfilled, and a notification tells you the records are ready to download from the portal. What no records service does is put the production into your practice management system with a name your team will recognize — that last step happens in your browser, at download time, and it's the step this page is about.
The discipline that makes the whole system work is filing on fulfillment. When the notification arrives you know exactly which client, which provider, and which date range the production answers — the request is right there. Send to Case turns that moment into the filing moment: send the download to the matter, pick the destination folder once, and give the file its permanent name while the context is in front of you.
- ✓ Request goes out through the retrieval service; fulfillment lands as a portal notification
- ✓ Open the production and file it to the Clio matter directly from the browser
- ✓ Rename at upload — provider, date range, record type — while you still know what it is
Not just ChartSwap
The workflow is the same regardless of which service fulfilled the request, because it operates on the download step every portal shares. Firms mix vendors by region and provider network:
- ✓ MRO — release-of-information service used by many hospital systems
- ✓ Datavant — the retrieval network that absorbed Ciox Health
- ✓ YoCierge — records retrieval built for legal teams
- ✓ Provider patient portals and direct HIPAA-request responses
Portal layouts vary by vendor and account configuration — install the extension free and test against a real production before a deadline depends on it.
Name records for the demand package, not the download
Portal file names describe the fulfillment, not the case. A records production typically downloads under the service's internal naming — a request number, an export ID, a generic label — which tells you nothing when it's one of forty documents in the matter. The name that earns its keep at demand time has three parts: the provider, the date range of treatment covered, and the record type.
Provider-first means the matter's documents list groups the way a records index does. The date range is what lets you spot the treatment gap — or prove there isn't one — without opening a single PDF. And separating records from billing in the name matters because they usually arrive separately and get cited separately.
| What downloaded | What to file it as |
|---|---|
Request_48213_Export.pdf |
Mercy Hospital 2025-01 to 2025-04 - ER and Inpatient Records.pdf |
records-download (3).pdf |
Dr Alvarez Ortho 2025-02 to 2025-08 - Office Visit Notes.pdf |
billing_export_final.pdf |
Northside Imaging 2025-03 - Itemized Billing.pdf |
The convention itself is a firm decision — the pattern above is one that works, and a broader system for dates, types, and versions is laid out in our guide to Clio document naming conventions, with folder placement covered in the Clio folder structure guide. What's not negotiable is the timing: Send to Case lets you set the file name at upload, which makes the rename a five-second step in the filing motion instead of a cleanup project nobody schedules.
Built for the multi-provider production
A serious injury claim means records requests to every treating provider — the ER, the hospital, the surgeon, the physical therapist, the imaging center, each billing department. Fulfillments arrive on their own schedules, some as single PDFs, some as many-file sets, some as one large zip. Filing that volume one upload at a time is how productions end up half-filed.
- ✓ Batch scan finds the file links on a portal page so you can select and upload in one pass
- ✓ Zip uploads extract automatically — the bundled production becomes individual matter documents
- ✓ Everything in a batch lands in the matter and folder you choose once
An honest note on size
Clio accepts uploads up to 5 GB per file, which covers essentially every records PDF and most imaging exports. A raw imaging study that exceeds it should stay in your imaging archive, with the radiology report and a manifest note filed in the matter recording what exists and where.
The batch mechanics here are the same ones covered in depth in our Clio bulk upload guide — and if your firm also handles incoming litigation productions, the discovery documents workflow applies the same discipline to Bates-numbered sets.
Whatever the split, the rule holds: a production you haven't filed is a production you'll be reconstructing later.
Records portals are outside your firm — that's the point
Sync integrations cover the firm's own storage; records arrive from everywhere else. Clio's first-party document integrations do a good job of keeping the firm's own drives and folders connected to matters — and Clio's native upload itself handles multi-file and folder uploads well once files are on your machine. But a records production doesn't start in your storage. It starts on a retrieval service's portal, behind a login, on their infrastructure — the same shape as a discovery share from opposing counsel or a court's document system.
That's the gap Send to Case occupies: it works in the browser, at the moment of download, on files arriving from outside the firm — records portals like ChartSwap, discovery platforms, court sites, Gmail attachments. It never has access to the records service's systems and doesn't need a per-vendor integration; it files what you are already authorized to download, into the matter you choose, under the name you give it.
The extension is free to install and is listed in the Clio App Directory. Test it against your next fulfillment notification — the ten minutes between "records are ready" and "records are in the matter" is the whole workflow.
Built for security-conscious firms
Your client data deserves protection. Here's how we keep it safe.
Direct upload
Files travel straight from your browser to Clio. They never touch our servers.
Official OAuth
We use Clio's official authentication. Your password is never visible to us.
Local storage
Your matter list stays in your browser. A few settings sync through your browser account, never to our servers.
Privacy first
File names are replaced with codes in error reports, and your files never reach us.
Every record type, one matter file
A fulfilled request rarely arrives as one tidy PDF. The constant: it all needs to land in the client's matter.
Treatment records
Office visit notes, hospital charts, operative reports, therapy notes — the clinical core of the claim, usually PDFs, sometimes hundreds of pages per provider.
Billing & itemized statements
Itemized bills, ledgers, and lien statements that drive the specials calculation. Often produced separately from the chart, by a different department, on a different date.
Imaging & multi-file productions
Radiology reports, imaging files, and productions split across many files or bundled as a zip. High file counts that make one-at-a-time filing painful.
Common questions about filing records-portal downloads into Clio
Got more? Email [email protected].
Does ChartSwap have a Clio integration?
+Not that we're aware of — ChartSwap is a platform for requesting and receiving records, and to our knowledge it doesn't push fulfilled records into Clio automatically. The bridge is the download step: when a request is fulfilled, someone at the firm downloads the records from the portal and files them into the matter. Send to Case works at that step, in the browser, so the download and the filing become one motion instead of a download now and a filing whenever someone gets to it.
How do I get medical records from ChartSwap into a Clio matter?
+The workflow is the same for records portals generally: when the fulfillment notification arrives, open the portal, and instead of downloading records to your desktop and re-uploading them later, use Send to Case to send each file to the client's Clio matter — picking the matter and destination folder once, and renaming the file on the way in. If the production arrives as a zip or a set of many files, the batch tools handle the whole set in one pass. The record goes from the portal to the matter without a stop in the Downloads folder.
How should I name medical records in Clio?
+Lead with the provider, then the date range of treatment the records cover, then the record type — something like 'Mercy Hospital 2025-01 to 2025-04 - ER and Inpatient Records.pdf'. Provider-first grouping means a matter's records list reads like the demand package's records index, and the date range answers the question you'll actually ask later: does this production cover the treatment gap? Whatever convention you pick matters less than applying it at upload time — renaming a hundred files after the fact is the task nobody does.
What if the records arrive as one huge zip file?
+Multi-provider or long-treatment productions often download as a single zip. Send to Case extracts zip uploads automatically on the way into Clio, so the bundle becomes individual matter documents instead of an archive someone has to remember to unpack. You still want a naming pass — files inside a production zip typically carry the service's internal names, not yours — but extraction plus batch filing turns an afternoon of clicking into one upload.
Can I upload large imaging files to Clio?
+Clio's documented limit is 5 GB per file, which covers nearly all records PDFs and most imaging exports. If a raw imaging study exceeds that, keep the original in your imaging viewer or archive and file the radiology report plus a note in the matter recording where the full study lives. The matter should always answer 'what do we have and where is it' even when a specific file lives elsewhere.
Does this work with MRO, Datavant, Ciox, or YoCierge?
+The workflow does, yes. Send to Case operates at the browser level on downloadable file links, not through a per-vendor integration, so the same download-and-file motion applies to fulfilled records from MRO, Datavant (which absorbed Ciox), YoCierge, and records produced directly by a provider's own patient portal or a HIPAA-request response. Portal layouts differ by service and configuration, so test against a real production before relying on it for a deadline.
Should medical records live in Clio or somewhere else?
+For most personal injury firms the matter is the right home: records are case documents, the people building the demand work in Clio, and a records set scattered between a portal, a shared drive, and someone's desktop is how gaps get missed. The exceptions are oversized raw imaging and any firm-level records archive your retention policy requires — for those, file the reports and a manifest in the matter and note where the originals live. The test is simple: at demand time, can one person find every production without leaving the matter?
Do records stay available on the portal after fulfillment?
+Treat portal availability as the service's policy, not yours — retention windows vary by vendor and account, and a portal is a delivery surface, not your case file. The safe discipline is the same one that applies to expiring discovery links: download and file the production when the fulfillment notification arrives, while you still have the request context — which client, which provider, which date range was requested — fresh in front of you. Reconstructing that later from a portal listing is the bad version of this workflow.
Keep going
Clio bulk upload
Batch page scanning, drag-and-drop, and automatic zip extraction for big productions.
Read guide →Clio document naming conventions
A firm-wide naming system — date, type, description — that makes the documents tab an index.
Read guide →Discovery documents to Clio
Production workflows for litigation teams — folder structure, organization, incoming and outgoing sets.
Read guide →Clio folder structure
Matter folder templates that give records, pleadings, and correspondence a predictable home.
Read guide →File the records the day they're fulfilled
Join personal injury firms who file records-portal productions straight to Clio.
Free tier includes 10 uploads/month. See pricing