Executive Summary
Introduction
This document is intended to provide a survey of various High Availability (HA) strategies that can be used in conjunction with InterSystems Caché, Ensemble, and HealthShare Foundation. This document also provides an overview of the various types of system outages that can occur, as well as how each strategy would handle a given outage, with the goal of helping you choose the right strategy for your specific deployment.
The strategies surveyed in this document are based on three different HA technologies:
Abstract
A global provider of mobile telecommunications software tested the performance of InterSystems Caché and Oracle as the database in a simulated data mart application. They found Caché to be 41% faster than Oracle at building a data mart. When testing the response time to SQL queries of the data mart, Caché's performance ranged from 1.8 times to 513 times faster than Oracle.
Introduction
Providing a reliable infrastructure for rapid, unattended, automated failover
Technology Overview
Traditional availability and replication solutions often require substantial capital investments in infrastructure, deployment, configuration, software licensing, and planning. Caché Database Mirroring (Mirroring) is designed to provide an economical solution for rapid, reliable, robust, automatic failover between two Caché systems, making mirroring the ideal automatic failover high-availability solution for the enterprise.
Introduction
With the maturation and wide acceptance of Java, object-oriented programming has moved to the foreground of the application development landscape. Because of their rich data models and support for productivity-enhancing concepts such as encapsulation, inheritance, and polymorphism, object technologies like Java, C++, and COM, are favored by today's application developers.
Comprehensive patient view, communication and data sharing, and population health management are key components
Federal agencies have been incenting healthcare providers to leverage their electronic health records (EHRs) to get patients involved in the management of their care. Most organizations, however, haven’t moved beyond patient engagement as an item to be checked off in order to receive meaningful use incentive funding.
Executive Summary
An accountable care organization (ACO) is a group of providers that are collectively responsible for the total cost and quality of care provided to a specific population of patients. Together, the group assumes risk and shares rewards. As with high-performing organizations in other industries, the hallmarks of ACOs are quality measurement and continuous improvement.
Featuring the results of the HIMSS Analytics Interoperability Study
Introduction
Overview
Integrated Delivery networks (IDNs) face complex challenges in getting the right data into the right hands, at the right time, with the goal of more informed decision-making and improved clinical and financial performance.
A business case for the transition from eGate to InterSystems EnsembleÆ From interface engine to integration platform Healthcare IT is evolving so rapidly that the term "HL7 interface engine" may soon become extinct. Forces driving this evolution include:
Introduction
Customers who switch to Caché from relational databases report that their average performance is up to 20 time faster, running on the same hardware, with no changes to the application. What is it about Caché that lets applications run so fast?
InterSystems Caché 2015.1 soars from 6 million to more than 21 million end-user database accesses per second on the Intel® Xeon® processor E7 v2 family compared to Caché 2013.1 on the Intel® Xeon® processor E5 family
Overview
Using Intel® Advanced Encryption Standard New Instructions with InterSystems Caché Substantially Improves Encryption Performance and Reduces Computational Overhead
Executive Summary
The CIO Perspective
Executive Summary
Executive Overview
One way financial services firms can improve their operational efficiency is to revamp their data management infrastructure. Creating a central repository for data that is used by multiple applications can ensure data consistency and quality across the enterprise, ease integration bottlenecks, and lower the number of failed trades.However, different applications have different database usage patterns. To satisfy them all, any central data repository must:
Introduction
Because of increasing business and governmental pressures to integrate their operations, the financial services industry is developing a number of standards for data exchange and other common functions. Standards such as XBRL, FpML, MDDL, RIXML, and FIXML are all specialized dialects of XML (Extensible Markup Language). Any financial services application with good support for XML will be able to communicate effectively using one or more of the emerging industry standards.
Are you new to Ensemble? InterSystems provides several tools to learn the basics of Ensemble and get on your way to becoming an expert in the technology. Before installing Ensemble, take a look at the Ensemble Technology Overview and Getting Started with Ensemble in documentation. Respectively, these documents explain features and major components of Ensemble as well as how to install the software.
Introduction
Application integration at its simplest is often just one application sending a message to another to notify it of some change. Perhaps when a patient arrives at a hospital, the registration system will send a message to clinical systems so they have all demographic data ready to use. Of perhaps it is just a nightly file transfer from the sales system to the accounting system.
But modern application integration platforms or suites can do a lot more than this to help applications work together and add real value to the enterprise.
Introduction
HL7 V2 message routing solutions often have hundreds of business services, processes and operations. Inevitably things will go wrong and you have to monitor the production to be able to react quickly and resolve any problems before they can become serious issues.
Ensemble includes some powerful alerting capabilities that can help, but if you aren't careful you will be inundated with alerts and your inbox more or less becomes a copy of the event log defeating the object of the exercise.
Introduction
This paper describes how Ensemble behaves after a system crash or similar uncontrolled shutdown or failover. Ensemble is normally configured to start processing messages automatically when the operating system restarts or when the system has failed over to a cluster member or mirror member. No manual intervention is required. But, in order for your system to robustly handle system failure and restart, you must understand how Ensemble handles these conditions and develop your productions using the rules and guidelines in this document.
Ensemble is based on message flow, and a data transformation is a way to convert from one message type to another. DTL (Data Transformation Language) adds a layer to this - it provides a graphical way to do the conversion. This is really helpful because most of the time, people with domain-specific knowledge may not have extensive coding skills. However, you always have the ability to do some coding, so if you need or want to, this is available.
DTL has several components: the data transformation engine, the language itself, and the DTL editor.
An introduction to virtual documents
Ensemble virtual documents enable your productions to work with large and complex documents with little overhead.
What is a virtual document?
A virtual document is a special kind of Ensemble message, for use with Electronic Data Interchange (EDI) messages and with XML documents.
How are virtual documents different from standard messages?
The Business Processing Language - for orchestration and long-running business processes.
Ensemble can orchestrate calls to external systems. Very often this is done to implement or automate a long-running business process - that is, real business processes where people interact with a series of different systems to complete complex tasks. BPL (the Business Processing Language) provides a graphical way to create these orchestrations.
How do you balance the need to achieve an early success with SOA against the requirement for an architecture that will deliver long term success? You don't want to get bogged down in architectural committees for three years, but you don't want to make short term decisions that will be roadblocks to long term success.
