What to Expect from the 2026 COB Solution Data Refresh
Stronger data. Better accuracy.
More reliable COB outcomes.
The 2026 COB Solution Data Refresh is a proactive initiative to remove outdated and inactive records, strengthen data quality, and improve system performance across the platform. This refresh supports more accurate overlaps, clearer primacy determinations, and greater confidence in operational workflows. Below you'll find details on what's changing, what to expect, and how we're supporting you throughout the process.
Content last updated: March 23, 2026
Why is the data refresh needed?
The data refresh will remove outdated and stagnant data from the system, improve the accuracy of overlaps, and improve system performance.
What data will be deleted during the refresh?
To strengthen data quality and ensure only accurate, up to date information remains in the system, the following data will be permanently removed:
- Inactive or termed records that are three years old or older.
- All inquiries, inquiry documents, inquiry details, and overlap attached documents.
To support your internal updates, each Reporting Entity will receive a file containing all deleted records once the refresh is complete.
When is this data refresh taking place?
All dates below are tentative and subject to change. Advance communication will be shared if any updates to the timeline are required.
- June 24: Data refresh begins; membership file intake paused
- June 25: Member Data Portal moves to read-only mode
- July 20: Member Data Portal returns to normal functionality; new files delivered
How much downtime will there be?
There will be approximately three weeks without a COB Return File. The Member Data Portal will be in read-only mode for approximately 25 days, from June 25 through July 20.
Additionally, the Member Data Portal will experience approximately three days of full system downtime, scheduled during overnight and weekend hours to minimize operational impact. Specific downtime dates have not been determined yet and will be communicated in advance once confirmed.
What is meant by “downtime?”
During the data refresh period, weekly membership file intake will be paused beginning June 24, as member records are removed and reprocessed. The Member Data Portal will move to read-only mode on June 25, during which time plans will not be able to submit overrides, overlap documents, inquiries, or group migrations. Member search functionality will remain available, displaying data as of the start of the refresh.
The Member Data Portal will return to normal functionality on July 20, at which time plans will receive refreshed COB data via a full COB Report. Once available, new overrides and inquiries can be submitted, and refreshed data will be accessible through the portal.
Plans may continue submitting their weekly files during the downtime; however, these files will not be processed until after the data refresh is complete.
The Member Data Portal will experience approximately three days of full system downtime, scheduled during overnight and weekend hours to minimize operational impact.
What will communications look like for this initiative?
CAQH will provide ongoing email communications from now through the completion of the data refresh.
To support planning and ensure your questions are answered, we will also host a series of optional Product-led office hours. Each session includes a brief overview of the refresh, key dates, and time for your questions.
Upcoming Sessions:
- Thursday, April 16: 1:00 - 1:30 PM ET
- Thursday, May 21: 1:00 - 1:30 PM ET
- Thursday, June 11: 1:00 - 1:30 PM ET
If you would like to be added to the session invite, please reach out to Jen Boza (JBoza@caqh.org). You are welcome to attend any or all sessions based on your needs.
What can we expect when the Data Refresh is complete?
After the refresh is complete:
- A full COB File will be sent on July 20th.
- The Member Data Portal will return to read/write on July 20th and all functionality will be restored.
- Overlaps will have new reference IDs. A crosswalk will be provided on July 20th in a pipe delimited text file to map old Reference IDs to new ones.
- Each Reporting Entity (RE) will receive a file with all the records that were deleted from their dataset.
If COB data was saved internally with old reference IDs, will it need to be refreshed?
Yes. Overlaps will have new reference IDs once the refresh is complete and a crosswalk will be provided to map old Reference IDs to new ones. If COB data was saved internally using old reference IDs, those old reference IDs will need to be updated using the crosswalk.