In 2025, HHS opened rulemaking on the next major EDI standards migration in healthcare. The proposal moves the industry from X12 version 5010 (in force since 2012) to version 8060. There is no compliance deadline yet. The proposed rule is still working through public comment and interagency review.
For practice management and EHR software vendors, the temptation is to file the news under ‘watch this’ and move on. That is exactly the mistake the industry made last time. The 4010-to-5010 migration compressed into a shorter window than most vendors planned for, and platforms that had not started preparing spent 2011 and 2012 doing forced remediation instead of shipping product.
What 8060 Actually Changes
The 8060 transaction set updates several of the fundamental data structures healthcare has been operating on for more than a decade. The specifics will continue to evolve through the rulemaking process, but the direction is clear on a few points.
- Expanded data elements. Additional fields for clinical documentation, attachments, and payer-specific information that were previously handled through workarounds or supplemental transactions.
- Structural updates to the 837 claim, 835 ERA, and 270 and 271 eligibility transactions. The core transaction types remain, but their internal structure changes meaningfully.
- Backward compatibility challenges. 5010 and 8060 are not interchangeable. Platforms will need to maintain both during the transition window, then cut over.
- Modernization for interoperability. 8060 is designed to interoperate more cleanly with FHIR-based transactions, reflecting the industry’s slow migration toward hybrid EDI and FHIR workflows.
The 4010-to-5010 Precedent
The last major EDI migration is worth studying because the pattern is likely to repeat.
- The compliance timeline compressed. What initially looked like a multi-year runway became an 18-month scramble once the final rule was published.
- Vendors that had not started early spent the compliance window doing panicked remediation, missing product roadmap commitments and stressing customer relationships in the process.
- Clearinghouse partners with strong EDI operations absorbed most of the technical complexity for their platform customers. Platforms that had built payer connectivity in-house did the work themselves, often at meaningful cost.
- Testing environments and payer readiness lagged behind the deadline, forcing many organizations to complete integration work under time pressure with incomplete payer participation.
What PM and EHR Vendors Should Do Now
Even without a firm deadline, three specific things are worth doing in the next 12 months.
- Add the migration to your multi-year product roadmap. Not as a specific delivery date, but as a placeholder for the engineering work that will eventually be required. Roadmap visibility drives decisions on where to invest engineering capacity in the interim.
- Ask your clearinghouse partner (or in-house team) for their 8060 preparation posture. Have they mapped the specific transaction changes? Are they in the rulemaking comment process? What is their expected timeline for supporting 8060 in parallel with 5010?
- Evaluate the reversibility of your current payer connectivity approach. If you are running on portal-based submission or a lightweight EDI implementation, the 8060 migration may be the moment when the maintenance cost becomes untenable. That is a build-vs-partner decision worth revisiting now, not after the deadline is published.
Questions to Ask Your Clearinghouse Partner
Whether you are currently working with a clearinghouse or evaluating one, a few specific questions surface preparedness.
- What is your current position in the X12 8060 rulemaking process? Are you participating in comment cycles?
- What is your projected timeline for supporting 8060 transactions in parallel with 5010?
- How did you handle the 4010-to-5010 migration for your platform customers? What did you learn?
- What impact should we expect on our integration during the transition window? Is your API layer designed to abstract the underlying EDI version from us?
- How do you charge for major standards migrations? Is 8060 support included in the existing partnership, or does it come as a separate cost?
How Harris Secure Connect Approaches Standards Migration
Harris Secure Connect has operated through every major EDI standards migration in healthcare, including the 4010-to-5010 transition. Our position is that standards migration is our job, not our platform partners’ problem. Our API abstraction layer is designed so that platform partners see minimal disruption during transitions, even when the underlying transaction structure changes materially.
If your platform’s multi-year roadmap has 8060 preparation as an open question, our team is happy to walk through what a partnership approach would look like for absorbing the technical complexity of the migration.