Unification Server

How can you share information when data is rigid, incompatible between systems and interfaces can be fragile/expensive?

Over the last 30 years healthcare has tried numerous times1 to reliably collect a complete medical picture of each patient. From health information networks to RHIOs and now HIEs, the approach has been surprisingly similar. After all it doesn’t look that impossible; use interfaces and pool the data. Yet, the results of each of these initiatives has been un-inspiring.

Should we try again using the same concepts?

In modern healthcare computers data is rigid and software is rigid. The software isn’t really designed to represent data from multiple computer systems. Should we just assume that all of the data from every system was collected with the same protocols and controls?

Instead of trying to share rigid data, why not create an environment where the data is fluid but can still be sourced from rigid systems?

Unityware has succeeded in creating a real-time process that translates raw structured and rigid data into computer understood information2. Multiple systems can now be connected with a common way to understand the data. The process by-passes interfaces and all that we associate with traditional software.

Newly encountered systems can go live in the unified environment in as little as 1/2 hour3.

Data does not have to be pooled into an amalgamated database as part of the install process or to be accessed. Fast install and start-up are matched with a low demand on maintenance or administration.

  

1. Journal of the American Board of Family Medicine / Patricia Fontaine, MD
2. Patent pending
3. As little as 15 minutes for brands the technology already knows but could be as long as 2 days for unknown brands using less obvious designs.

Unification and Unification Server are trademarks of Unityware, Inc.