Apex Unify! will start out with ForeverDB and Synchronicity in our initial pilot offering in Q1 of 2019, but we intend quickly to layer BlockSync support for interop across organizational boundaries and workflow in 2019.
Unify! as a stack will create a cottage industry of semantic adapters, workflow orchestrations and custom user experiences that we expect to become a vibrant third-party market. In support of that, by the end of 2019 we expect to offer collaboration tools for developers and subject matter experts to extend the platform in domain-specific ways, and to help them monetize these extensions commercially.
Also in 2019 we expect to offer the entire stack as a service on a variety of popular clouds, including AWS, Azure, Google and BlueMix.
We are working on two demonstration use cases for Apex Unify! at this time, which we plan to unveil by Q1 of 2019.
The first is a universal "provider" or "practitioner" directory that focuses on helping stakeholders in the insurance industry share a common "truth" about the available pool of physicians and specialists that are represented as being in their published provider networks ("Physician Directories"). This use case will demonstrate a new approach for the industry to better manage the accuracy of Physician Directory data across multiple internal business lines (government, commercial, private) in enterprise environments that are currently fragmented thereby impeding real-time synchronization of the "truth" across stakeholder systems of record.
The second use case is more clinically relevant and attempts to show how business logic in the medication reconciliation domain can be customized locally while sharing a common view of prescriptions across multiple facilities and practices that take care of a patient. In this use case we'll be using our Medication Reconciliation technology to show a scenario where a patient is subtly abusing opioid prescriptions circumventing oversight by getting multiple prescriptions filled at different hospitals. This data sharing is essential to identifying and diagnosing the potential opioid misuse and addiction so that the patient can be helped before it's too late. Once again, the boundary between shared data and local business logic will be front-and-center, as well as focus on patient privacy concerns.