The healthcare industry has for years turned to IT to help improve patient care and become more efficient. Back in 2004, IT became the cornerstone of interoperability efforts set in motion when President Bush issued an executive order calling for widespread use of electronic medical records (EMR). IT continues to play a significant role in those efforts but integration challenges remain. Read more about the challenges and how healthcare companies are applying both old and new solutions to overcome them in this post from the Red Hat JBoss Middleware Blog.
In the post, Sameer Parulkar, principal product marketing manager, Red Hat, walks through the primary factors challenging healthcare integration: the complex standards to exchange and manage healthcare data, structure of the healthcare industry, and healthcare’s strict and evolving regulatory environment. He details, for example, the impact of the Health Insurance Portability and Accountability Act of 1996 (HIPAA) and the Health Level Seven standards (HL7), both of which address interoperability and data sharing but require adherence to a complex set of rules and processes.
Parulkar also talks in the post about ways healthcare organizations can address interoperability challenges. He recommends using ESB technologies that provide capabilities like connectivity, transformation, mediation, routing, and service orchestration, but points out that traditional ESB technologies may not support the relevant healthcare standards or be compatible with the cloud. To that end, he suggests organizations consider modern integration platforms such as Red Hat Fuse.
According to Parulkar, Red Hat Fuse offers traditional ESB capabilities like transformation, connection, scalability, clustering, high availability, and failover, as well as an open, modular, and lightweight integration platform that can make it easier for healthcare companies to address their integration challenges. Red Hat Fuse also supports HL7 standards and enables healthcare companies to create HIPAA compliant solutions, he says.
We recommend reading the entire post. There’s plenty more information about the integration challenges and the solutions to mitigate them, and let us know your thoughts on it in the comments section below. Bonus—Parulkar recommends attending this webinar (and so do we!): Creating HIPAA-compliant applications without JCAPS/JavaMQ architecture on Dec 2, 2015.