This blog post is part of a DirectTrust series exploring how organizations are implementing 360X to improve referral workflows and support better care coordination. This installment features insights from eClinicalWorks.

It’s a common referral scenario: A primary care provider determines that a patient needs to see a cardiologist. The referral is entered, the patient leaves with a list of specialists, and, from there, much of the responsibility shifts to the patient.

The patient needs to find a specialist who accepts their insurance, determine who can see them within a reasonable timeframe, schedule the appointment, and make sure the right information gets where it needs to go. Months later, the patient may return to the primary care provider having never seen the specialist at all.

That’s where the referral process can begin to break down.

360X, a closed-loop referral standard supported by DirectTrust, gives everyone involved more visibility into what happens to that referral. But that visibility shouldn’t come at the cost of adding another workflow for providers and staff to manage.

The Workflow Shouldn’t Be the Hard Part

When implementing 360X, the goal is straightforward: don’t make users learn an entirely different process.

“We took a look at how we currently send and receive referrals electronically,” said Azim Mohammed, Product Lead at eClinicalWorks. “Whatever they’re doing today, we want to make sure that the functionality is exactly the same. Nothing for the end user to worry about.”

A provider or referral coordinator can continue to initiate the referral through the existing EHR workflow. Behind the scenes, eClinicalWorks recognizes whether the recipient is 360X-enabled and handles the additional exchange.

“As soon as they click that send button, we handle everything for them,” Mohammed said. “Their workflow day in and day out for a PCP office, nothing has changed. It’s the same steps, the same workflow.”

That’s important because new interoperability capabilities have limited value if using them means adding more clicks, screens, or manual processes. In some cases, 360X can actually reduce those steps.

Using the 360X Identifier to Automate the Workflow

A key element of the 360X specification is the unique identifier assigned to each referral. That identifier stays with the referral as status updates and clinical information move between participants, allowing systems to associate subsequent messages with the original referral.

That identifier can also be used to automate work that previously required manual steps.

When a consultation note comes back, for example, the unique 360X identifier allows the system to determine which patient and referral the document belongs to and which primary care provider should receive it. The record can then be routed to the appropriate provider for review and linked back to the original referral.

“We were able to dramatically reduce the number of steps that they had to do previously,” Mohammed said.

The same closed-loop process can give the referring provider visibility into what happened after the patient saw the specialist. New diagnoses, medications, laboratory orders, and other clinical information can flow back to the initiating provider, helping inform the patient’s ongoing care.

Compare that with a traditional referral, where the PCP may not even know whether the patient ever made the appointment, much less what happened during the visit.

Building on Technology That’s Already There

Part of what makes that possible is that 360X does not require an entirely new communications infrastructure.

The specification builds on Direct Secure Messaging and other existing interoperability standards and technologies. As Ayres “Trey” Fortes, Director, Interoperability Product Management at eClinicalWorks explained, 360X uses capabilities that EHR vendors and healthcare organizations already know how to support, adding the structure necessary to track the referral and its status through the process.

“The nice thing about 360X is it truly did not add in any new technology,” Fortes said. “We just took existing technology, existing functionality, and tweaked it and made it work for this really important use case, which is referrals and transparency within the referral process.”

Fortes said 360X is enabled by default for exchanges between participating eClinicalWorks practices. The implementation becomes more complicated when referrals need to move across different EHR platforms.

Those implementations can require organizations and vendors to work together on configuration, testing, routing, and training. A health system may need to determine which department or inbox should receive a referral, who is authorized to respond, and how the workflow should operate once the referral reaches the organization.

Fortes sees a more standardized onboarding and implementation process as an important next step for expanding 360X across the healthcare ecosystem.

Making Closed-Loop Referrals Routine

The goal is to make this kind of exchange routine. Patients can have more clarity about where the referral went and what happens next, while referring providers gain visibility into whether the referral was completed and receive information back from the specialist.

Getting there will require broader adoption across EHR vendors and healthcare organizations, along with a more streamlined approach to implementation and onboarding. Fortes would also like to see more of that work automated so practices aren’t pulled into unnecessary configuration and testing.

Direct Secure Messaging and the other technologies 360X relies on are already widely used. Making 360X easier to implement across different systems and organizations can help closed-loop referrals become a more routine part of care.

Learn more about 360X and closed-loop referrals.