By Greg Meyer, Senior Director of Development and Infrastructure
With the rollout of the Office of the National Coordinator of Health IT (ONC)’s HTI-5 Final Rule, Direct certification goes away, but Direct compliance doesn’t
As of late October, ONC has released the highly anticipated HTI-5 Final Rule, removing the 170.315(h)(1) “Direct Project” and 170.315(h)(2) “Direct Project, Edge Protocol, and XDR/XDM” certification criteria, effective December 27, 2026.
So, what does this mean for our compliance ecosystem? In short, the testing and certification process that Direct implementers (HISPs and others) have been working through since the 2015 Edition goes away, under the assumption that the functionality is so widely relied upon that the industry will keep doing it whether or not anyone is checking. With that said, Direct also received some encouraging reinforcement: ONC will keep Direct as an indirect requirement for transporting C-CDA documents via the transition of care criteria through January 2030. Even after that, ONC expects that vendors will keep supporting Direct.
What the rule does not do is replace the (h) criteria with anything that ensures a HISP down the road actually behaves the way the Direct specification and accompanying implementation guides say it should. Several members of our community who submitted comments during the review process raised exactly that concern, noting that the burden of verifying conformance would shift to the customers of Health IT Modules. The expectation is essentially that the market will sort it out. This is where we come in to fill that gap, something we have been doing at DirectTrust for over a decade with our accreditation programs.
Our HISP accreditation program ensures that HISPs not only comply with the letter of the law of the Direct specification, but also meet the high bar of security and trust demanded by health IT industry best practices. In its current form, HISP accreditation relies on many of the same tools that ONC required for (h) certification. But with the (h) certification criteria going the way of the dodo, it raises the question of what the future holds for the existing ONC testing tools, and whether they will even exist by the time the rule takes effect. Fortunately, we have been anticipating that question for quite some time, and in response have rolled out the DirectTrust Tools web site.
At its core, DirectTrust Tools is an authenticated workspace where DirectTrust members can execute conformance tests against their Direct implementations, explore and check directory data, and inspect message content. It is also built to grow, with new tools added as needed, and access is gated by the permissions we grant so that users only see the tools that apply to them. Within the framework, users can find HISP accreditation tools for executing familiar tests like certificate discovery, Direct send and receive, and the edge protocols (XDR, SMTP, POP3, and IMAP). When the testing is done, the results are stored in your account and can be rolled into a single formal report delivered to your inbox with the goal of no artifact wrangling.
A skeptic might ask: if ONC is going out of its way to lighten the load on vendors, isn’t a new set of testing tools just the same old pain wearing a different hat? It’s a reasonable question, and one answer comes down to who built them. The DirectTrust Tools development team includes former HISP operators – people who sat in the front row for the (h) certification process. They know exactly where the hours disappear and remember which steps made them question their career choices. Rather than reproduce that experience, they set out to simplify the process itself, starting with evidence collection. Running a test is just one part of the process that also includes the juggling of logs, screenshots, and output files afterward that eats the calendar. DirectTrust Tools now do that bookkeeping whenever possible, managing the workflow, storing every result, and assembling the reporting on your behalf.
Not every HISP will completely fit that tidy pattern, and since Direct allows for variation between implementations, some evidence will still need to be collected by hand. To meet this need, the HISP tools include built-in manual modes where necessary.
There is a less obvious benefit to all of this, and it has to do with control. For years, our HISP accreditation program has been a tenant in someone else’s house, dependent on a testing suite that we did not build, could not change, and had no say in maintaining. Owning the tools means we now control our own destiny, and although we are still in the process of moving our accreditation criteria off the ONC tools and into our own, that is housekeeping on top of control we now have. That control matters most when the Direct ecosystem moves. Instead of waiting for an upstream tool to catch up with a new idea, we can build the testing for it and get it into the hands of the community when they need it rather than when an upstream roadmap allows.
Ownership of the tools also changes the support story. Anyone who has tried to chase down the right contact for a stuck test knows why that is worth mentioning. With the previous accreditation format, answers were not always easy to find or quick to arrive, and more than a few vendors ended up calling us instead, making DirectTrust an unofficial tier 2 support line for tools we didn’t even run. Another common frustration is uptime, because a testing tool that is down on the day you scheduled your accreditation window is a special kind of frustrating. DirectTrust Tools runs on highly available, self-healing Kubernetes infrastructure, so a failed component gets replaced rather than becoming the user’s problem. If something does go sideways, there is now one reliable and responsive place to go for help.
Last, but certainly not least is documentation, a subject that is rarely the star of the show but is almost always the first thing to blame when a test goes wrong. Anyone who has gone looking for the instructions to a testing tool knows the drill: a PDF in one place, a Wiki page in another, a forum thread from 2019 in a third, and a nagging suspicion that the one document you really need was never written down at all. DirectTrust Tools takes the opposite approach, with every tool and workflow fully documented on a single, consolidated doc site that is easy to find and organized the same way the tools themselves are. Whatever test you are running, the documentation that explains it is never more than a click away, which means no scavenger hunts, no tribal knowledge, and no emailing the one person who remembers how it works. Good documentation will never be glamorous, but it is the difference between a tool you can use on your first attempt and one you need a support call to figure out, and we would much rather users spend their time testing their HISP than decoding ours.
So where does that leave us? HTI-5 will take the (h) criteria off the books and leave ONC with the reasonably optimistic expectation that HISPs will stay compliant with the specification on their own. Still, hope is not a conformance strategy, and Direct only works when every HISP in the chain does what the specification says it should – a promise we have long helped the community keep. That commitment does not end with the (h) certification process, and neither does the need for it. DirectTrust Tools represents the next chapter of that work: a purpose-built, DirectTrust-owned suite that helps automate the tedious parts, stores and reports results, stays up when you need it, comes with documentation you can actually find, and is backed by a team that has been in your shoes.
Compliance has never been optional for those who want to be trusted, but it can certainly be a lighter load. ONC may be handing out fewer crosses to bear, but for those of us who still have one, we intend to make it far easier to carry.
