At Apex, we build all of our products in order to achieve a very specific technology vision. That vision is embodied in our Apex Unify! stack and involves solving some of the hardest problems in IT, problems whose roots are deep and not apparent, and for this reason the industry seems to cycle on them endlessly.
How many times has your organization tried to come up with an "enterprise data model" or faced massive data transformation projects whenever a new system or application had to be brought online or into alignment with existing systems (for example, curing a corporate acquisition)?
Seriously - how many times are we going to have to talk about advances in "interoperability" in healthcare that, on closer inspection, are really just horrible point to point integration band aids that make the problem worse, more intractable?
Too often discussions about "interoperability" and related topics portray them as if they're the best-known problems in the world. Vast ontologies are constructed to feed ever more complex vocabularies of "things" in our domains, as if all the world lacks is a new data exchange format to standardize upon, and viola, we'll suddenly live in world of systems "talking to each other."
But are we even looking at this problem in a way that makes it solvable? Do we really need systems "talking to each other" or is there another way to frame the issue entirely?
Apex Unify! attempts to answer these questions in a way that focuses on pragmatic operationalization over conceptualization. We see interoperability as a problem of capturing truth over time in a world where multiple sources of truth disagree, not on inventing some new magical standard for data exchange. Such standards are needed and useful, but entirely orthogonal to the real problem.
Each component in the Unify! stack was conceived to solve a specific aspect of the real problem. Our goal over time is to make interoperability an architectural layer, not something of which existing sources of truth need even to be aware.