I am working on an Ensemble demonstration that involves workflow. Over the course of testing I have cleared out the Ensemble message store several times. This has left several workflow tasks that no longer can be assigned, accepted or rejected.
How do I clear the Workflow Tasklist which is found by going to Ensemble -> Manage -> Workflow -> Workflow Tasks in the Ensemble Management Portal?
If I paste something into the Message editor (e.g. when posting) the editor duplicates the content in the clipboard. This is very annoying. I am using Safari 7.1.7.
If you have Cache installed on a Cent OS machine, and you want to switch the OS to Red Hat 7, and your Caché is installed on a non-OS drive, do you need to reinstall Caché?
The situation is, I have a Partner that is looking to create common Dashboards in a SaaS model where the Partner's Clients would want to have their individual views of this common dashbaord be branded (logos, color, styles, etc.) to match the Client's branding. This my Partner's Client's End Users will see this common dashboard as the dashboard from the "Client" and not the "Partner" (and certainly not ISC branding)
It seems pretty easy to add a post to a group or something like that. But lets take Code Packages for example. How do I go about submitting a code example to be posted under that area?
The attached zip file contains a bunch of examples of Cache SQL Storage mappings that I have done over the years.
If you have existing globals and want to expose them via Objects or SQL you need to setup Cache SQL Storage mapping. If you do not see an example that helps with your case send me an example and I can help you out.
Tip dvacátý šestý: objekty a concurrency 2 - swizzling
Když tento seriál před několika lety začínal, byl jeho první díl věnován zajištění izolace instance objektů pro exkluzivní přístup a popisu příslušných API funkcí. Nedávno se mi ale stalo, že mě tento díl dostihl. Jeden ze zákazníků začal mít problémy v aplikaci, přestože důsledně používal exkluzivní zámky pro editování instancí svých objektů.
Information Sharing Enables Health Plans to Leverage Data and Analytical Assets to Deliver Sustained Value
Executive Summary
The shared-risk payment models that are central to health reform all require tight coordination among payers, providers, and patients if they are to succeed. As payers and providers enter into more and more such agreements, they need to enhance success by communicating and collaborating more effectively with their partners and actively engaging, supporting, and empowering their members.
Australia's recent launch of the Personally Controlled Electronic Health Record (PCEHR) - a significant step towards establishing a national e-Health infrastructure - has simultaneously provided a boost to shared Electronic Patient Record (EPR) projects and delivered a wake-up call to healthcare providers about their readiness for connected care initiatives. In countries around the world, the era of connected care is here.
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.
Impedance mismatch is a term commonly used to describe the problem of an object-oriented (OO) application housing its data in legacy relational databases (RDBMS). C++ programmers have dealt with it for years, and it is now a familiar problem to Java and other OO programmers.
Improved Access to Clinical Data Across Hospitals and Systems Helps Pharmaceutical Companies Reduce Delays and the Costs Associated With Bringing New Treatments to Market
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:
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.
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.
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:
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
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.
Changes in reimbursement approaches in healthcare are unleashing unprecedented business forces in the industry. As a result, providers are consolidating into larger integrated delivery networks, hoping to achieve economies of scale and operating efficiency.
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.
To overcome the performance limitations of traditional relational databases, applications - ranging from those running on a single machine to large, interconnected grids - often use in-memory databases to accelerate data access. While in-memory databases and caching products increase throughput, they suffer from a number of limitations including lack of support for large data sets, excessive hardware requirements, and limits on scalability.
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.
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.