Integration

Turbo Disaster, or When failure was Not an option... - A Success Story of some software integration

Hello everybody,

My name is Sergey Kostrov. I'm an Intel Black Belt Software Developer and am Not an-Intel employee. I'd like to share my experience ( a <strong>Success Story</strong> ) on how some very complex software integration was done a couple of years ago on the <strong>ScaLib</strong> project.

Service-Oriented Computing and Web Software Integration(ASU)

Web software development and cloud computing based on Service-Oriented Architecture (SOA) and Service-Oriented Computing (SOC) represent the modern software engineering theory, practices and technologies. The book takes a comprehensive and coherent approach to address these issues. The goal is to learn the concepts, principles and methods in advanced software architecture, software engineering, and software development. The approach is learning by developing.

Applying a Service Gateway architecture to integrating your e-Invoicing

Surfing the Eisbach riverI was recently asked to talk at the European eInvoicing and eBilling conference about better ways to integrate the transfer of e Invoicing and e billing into existing applications and security solutions. By the way, it was held in Munich and, if you go, definitely check out the surfing at the south end of the Englischer Garten.

New Intel® SOA Expressway for Healthcare Release Powers Patient/Provider Community Exchange at Newark Beth Israel Medical Center

It’s been about a year and half since we first released Intel® SOA Expressway for Healthcare, which is a purpose-built, easy-to-deploy integration appliance for connecting islands of information together to enable a secure, high-performance, best-of-breed health information infrastructure. We have now begun shipping release 2.2, which contains a number of new feature enhancements.

Design approaches for patient identification in health networks

My last few posts have looked at the role of data standardization and terminology translation in enabling healthcare organizations to exchange information that can be understand by all. Terminology translation acts as a bridge to make it possible for two organizations to share and understand health data that is "codified" differently.

Designing for gray scale: under the hood of medical terminology translation

My last couple posts have touched on the importance of data standards in enabling interoperability in healthcare. It is important to recognize, however, that data standardization is not about dictating the way organizations capture and share clinical data.

Semantic normalization: making sense out of health data

In my last post I looked under the hood at data interoperability, examining the need for the normalization of both "syntactic" and "semantic" aspects of healthcare data. In this post I will present a high-level architecture for data normalization to share some understanding of how health information exchange is implemented in practice.

Peeling back the onion of health data interoperability

Data interoperability is vital to today’s healthcare computing environment, allowing clinical information to be effectively and consistently exchanged, compared, and analyzed among healthcare partners such as insurers, pharmacies, affiliated providers, and public health departments. Put simply, data interoperability enables better decision making.

Suscribirse a Integration