Speaking of their initiative to provide Puget Sound-region physicians health information sharing capabilities, South Sound Health Communication Network's Rick McCormack says, "[W]e don't refer to it as a RHIO because we don't know if the term RHIO will even be around in two years. It's an emerging form." We've commented (here) on the evolution of RHIO - both here in Northeast Ohio and across the nation. Perhaps Mr. McCormack is correct, though, to be skeptical of the term. What we've proposed is even less RHIO-like than SSHCN's project: "a Web site with portals for physicians and patients within secure communications software" with a $40 per month price tag. Rather, as we've said before, IPA and PHO that build communities of users around a single platform, i.e. one EHR application hosted by them or a third-party, are creating a de facto RHIO (again that word!) that will grow organically to share information between physicians, clinics, hospitals, and pharmacies.
This makes good business sense and good healthcare sense. Physician organizations can live up to their mandate by leveraging their members' buying power to get the lowest possible prices for their practices. Physicians can ensure that they - through their chosen affiliations - make the important decisions that impact their practice, rather than have those decisions dictated by the hospitals to which they refer. After all, they are independent physicians for a reason. Finally, patients and physicians alike will benefit from the increased intercommunication within the organization and, ultimately, within the region.
When networks like the SSHCN grow and reach out to other grass-roots organizations, they can interconnect faster, more efficiently, and more economically than individual practices. By being a part of a hosted (or, if you like, ASP) application community, they also create a viable business model for data sharing. As mentioned before, NEO RHIO here in Northeast Ohio lies dead in the water because there is no such model. None of the major health networks has an interest in creating an interoperable data exchange that will also benefit the other networks; no third-party hosts can figure out how to make it economically viable. In the hosted application model, there is an incentive for the third-party host to build inter-communication into the system through software interfaces: the greater inter-communication their model provides, the broader its appeal and the larger their customer base.
As we've said, it is an evolving process. There are always new considerations, new ideas. Undoubtedly this one will change over time. Right now, though, we believe it is the best way for independent physicians to come together to implement the tools HIT has to offer. As always, comments, criticisms, observations are all welcome.
Article Link