Аймақтық денсаулық саққтау ақпараттық ұйымдары: қалыптасу және міндеттері

A Regional Health Information Organization (RHIO, pronounced rio), also called a Health Information Exchange Organization, is a multistakeholder organization created to facilitate a health information exchange (HIE) – the transfer of healthcare information electronically across organizations – among stakeholders of that region's healthcare system. The ultimate objective is to improve the safety, quality, and efficiency of healthcare as well as access to healthcare through the efficient application of health information technology. RHIOs are also intended to support secondary use of clinical data for research as well as institution/provider quality assessment and improvement. RHIO stakeholders include smaller clinics, hospitals, medical societies, major employers and payers. RHIOs are intended to be key to the proposed US Nationwide Health Information Network (NHIN).

as of 2009, 193 initiatives (including RHIOs) in the United States were working on health information exchange, and 57 of those were actively exchanging data used by healthcare stakeholders. RHIO initiatives exist at two levels, larger (statewide) and smaller (local and rural). Compared to local RHIOs, state level initiatives, because of the larger number of stakeholders and patient base, and consequent financial strength, have a greater likelihood of being able to utilize national level expertise both in health IT and policy making. Most operational RHIO efforts tend to be larger efforts, though the risk of political battles and consequent failure is also amplified if several large stakeholders choose not to cooperate with each other. Compared to state level RHIOs, stakeholders tend to be more heterogeneous with respect to line of business, use of technology and size. Rural RHIOs have a subscriber base of less than 100,000. The presence of numerous, smaller organizations with relatively limited IT budgets translates to numerous challenges due to the dis economies of small scale. There is limited access to skilled technology professions, and health IT vendors pay less attention to small customers. Many stakeholders continue to deploy legacy software from long defunct vendors and some may not deploy IT at all. In addition, stakeholders may be less IT savvy, and even availability of high speed Internet connectivity may not be assured. A significant sustainability challenge for smaller RHIOs involves funding. Some support models (e. g., used by Northwest, Louisville KY) are based on shared, subscription based use of commercial health information software, and the shared use of scarce resources such as information technology professionals, who are unaffordable for smaller organizations acting individually. Irrespective of size, certain challenges remain, such as interoperability standards, as well as consistent standards with respect to privacy, security and appropriate use of the data. Currently, privacy/security issues vary across states, and federal efforts to ensure uniformity are desirable.

The Indiana Network for Patient Care (INPC) — originally the Indianapolis Network for Patient Care and Research (INPRC) — operational since 1994, connects all five major hospital systems in greater Indianapolis. All INPC participants now deliver registration records, all laboratory tests, text reports, medication history and all UB92 records (diagnosis, length of stay, and procedure codes) for hospital admissions and emergency room visits to separate electronic medical record vaults in a central INPC server using a federated data store model. The message exchange standard that is used is HL7. The computer system standardizes all clinical data as it arrives at the INPC vault, laboratory, radiology, and other study test results are mapped to a set of common test codes LOINC with standard units of measure, and patients with multiple medical record numbers are linked. Stakeholders/ participants in this RHIO include: major and regional hospital systems, regional and national reference laboratories, state, federal, and private payors, pharmacy benefit management claims repository services, major physician practice organizations, individual providers, state government (Dept. of Health), major academic research institutions, and others. The statewide Indiana Health Information Exchange (IHIE), which uses the expertise of the same medical informatics/IT team as the INPC, combines clinical data in combination with administrative (claims) data to support electronic delivery of test reports to physician offices using faxes, printers, and e mail, as well as Clinical Quality Services, which provide a "report card" (and incentives) on established quality measures to physicians, practice groups, employers, and payers. The IHIE is a rare example of a self sustaining health information exchange (not reliant on government grants). Stakeholder satisfaction with this RHIO is apparently high.

CalRHIO is an example of an RHIO failure due to political/turf battles; it shutdown January 8, 2010. Following heavy competition with California e Health Collaborative (CAeHC) for designation as California's statewide HIE entity, both organizations were turned down by the state government in December 2009; large stakeholders such as Medicity Inc. and Kaiser Permanente subsequently followed suit and withdrew financial support. Reasons for CalRHIO's failure have been attributed to a limited business model dependent on state entity designation.

Healthcurrent is the RHIO for the state of Arizona, formerly known as AZHeC. Healthcurrent hosts a physical health and behavioral health/crisis portal for health information exchange throughout Arizona. Healthcurrent links care providers to its standards based HIE platform and holds a repository of data that is available to be shared with properly accredited care providers in the community. Arizona is an opt out state for healthcare data flowing to the state HIE.

In some states (e. g., Kansas), an alternative to a stakeholder consortium based state level RHIO is being considered, namely direct involvement of the state governments in creating the RHIO infrastructure. This approach builds on the strengths of state governments as major employers and purchasers of healthcare services (e. g., University of Alabama at Birmingham, is Alabama's largest employer). Similarly, TennCare in Tennessee has roots in addressing the state's un and under insured population and is consequently more state driven. Utah's efforts are based on the state's prior efforts to process healthcare claims. Recent federal efforts (e. g., at the Veterans Administration) are aimed at creating a federal employee based electronic health record system, which might be considered a national RHIO.