Introduction

As healthcare providers face increasing pressures to lower costs and reduce readmissions, they're rapidly shifting towards accountable?care organizations (ACOs) and other coordinated, quality-based reimbursement systems. However, most providers have historically?organized their data and workflows in ways that best fi t the fee-for-service payment model. Now that so many providers are sharing?risks and rewards, they must also share and coordinate information by adopting more streamlined health information technology?solutions.

InterSystems encourages the adoption of a flexible, practical approach to application development, rather than strict adherence to one of the prevalent development theories. This paper offers advice based upon our experience. However needs, attitudes, and styles vary; we recommend that each programmer choose the development approach that works best for them. Caché supports a wide range of development methodologies, not just those recommended here.

Improved Access to Clinical Data Across Hospitals and Systems Helps Pharmaceutical Companies Reduce Delays and the Costs Associated With Bringing New Treatments to Market

Executive Summary

The pharmaceutical and life sciences industry has a strategic imperative to accelerate clinical research in order to reduce overall R&D costs while delivering innovative treatments.

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.

Executive Overview

Accountable care and value-based reimbursement models are causing a seismic shift in the medical device industry. In the new medical device market, the value of the device and data alone will not drive sales. instead, it will be solutions that bundle device, data, and real-time analytics that clinicians, health systems, and payers will want to buy. For improved decision-making and outcomes, they need these solutions to deliver actionable information into existing electronic medical record systems and health information exchanges.

Executive Summary

The best way to compare the performance of database products is in a head-to-head test using a real application, preferably one of your own. This is especially true when evaluating Caché's post-relational technology, because "standard" transaction processing benchmarking methodologies assume the restrictive "row and columns" format of a relational database. They cannot accurately predict the performance of real applications, which often use complex data models.

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.

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.

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

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 body of any Ensemble message is represented by a persistent class that has one property for each value that the message is intended to carry.

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.

If your first project is to deploy a small number of reusable services in a matter of months but you know that four years from now you might have hundreds of services, an enterprise SOA infrastructure and specialized governance technology you have a dilemma.