I'm very proud of the Worldwide Response Center - an excellent group of men and women - and I am interested to hear from you about your experience using the WRC. There are always better ways for us to serve you.
I'm also very excited about the Developer Community which we're bringing to you to give you an opportunity to connect with groups and individuals in the InterSystems community. Let us know what you think and how we can improve it in order to serve you better.
Hello-
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?
Thanks in advance
Ken
I am using &html<> to output some CSS to my page (which is a class-based and not a tag-based page), and the selectors contain the '>' character which the compiler chokes on. How can I escape the '>' so it still displays as such in the web page source but doesn't trip up the compiler?
This is for 2012.2 btw.
Hi -
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é?
I don't think so, but I wanted to check
Hello DeepSee'ers -
How hard is it to brand a dashboard to a login?
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)
ie. ISC -> Partner -> Client -> End User
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.
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ů.
Abstract
A benchmark of a real-world application, which loads data into a data warehouse for subsequent analysis, was performed. To conduct the benchmark, one module of the Oracle-based application was replicated in Caché ObjectScript. Only about 40 person-hours of work was required to duplicate the functionality of the original module in Caché.
The time required to complete certain tasks was measured running the Caché-based module, and was compared to existing data.
Introduction
With the growing popularity of smart phones and tablet computers, consumers are coming to expect that software solutions will be presented as "apps" on their mobile devices. The challenge for most application developers is to find ways to make their existing solutions run on modern mobile platforms without incurring the delay and cost of a complete rewrite.
Executive Summary
For twenty years or more, large financial institutions have been locked in a battle between the need for extremely high performance transaction processing and the demands of downstream applications that can deliver competitive advantage if they can get real time access to this transactional data. When individual database servers could no longer handle simultaneous transaction and query workloads, many firms turned to replication, offloading data access onto read-only copies of production databases.
Executive Overview
The healthcare software market offers exciting and significant growth opportunities. Yet, while some healthcare software companies enjoy incredible growth, others under-perform, languish, or even fail. There are many criteria for success in this market, but two are particularly critical:
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
With data volumes soaring and the opportunities to derive value from data rising, database scalability has become a crucial challenge for a wide range of industries. In healthcare, the rising demands for healthcare services and significant changes in the regulatory and business climates can make the challenges particularly acute.
Introduction
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.
The PCEHR has increased both the push and pull factors that will lead to widespread shared EPR adoption.
Introduction
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.
Impedance mismatch arises from the inherent lack of affinity between the object and relational models.
Introduction
In healthcare, information accessibility can impact the outcome of a medical decision, or the success of a bundled payment initiative. To ensure that the right information is available at the right place and time, healthcare organizations typically have used HL7® interface engines to share data among clinical applications. But the demands on healthcare information technology are changing so rapidly that these simple engines are no longer sufficient.
Introduction
In today's world, an ever-increasing number of purchases and payments are being made by credit card. Although merchants and service providers who accept credit cards have an obligation to protect customers' sensitive information, the software solutions they use may not support "best practices" for securing credit card information. To help combat this issue, a security standard for credit card information has been developed and is being widely adopted.The Payment Card Industry (PCI) Data Security Standard (DSS) is a set of guidelines for securely handling credit card information.
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.
Like other care models that are experiencing changing reimbursement structures, ACOs require new competencies to coordinate the delivery of care, and to manage populations, finances and risk.
Introduction
Software services, in a service-oriented architecture (SOA), can be used again and again in many different business processes, making for a very flexible, efficient, and vibrant business and information technology infrastructure. Providing, of course, that IT has the right platform in place for modeling business processes and implementing the SOA. Using the InterSystems Ensemble product as an example, this paper examines two key technologies that are absolutely essential for successful SOA implementation, but missing from most SOA development platforms.
Introduction
Tying quality of care to reimbursements has been proposed in the last few years as a solution to increase the efficiency and quality of care and replace the costly and ineffective fee-for-service model. Provisions within the Affordable Care Act of 2010 have given accountable care organizations (ACOs) the foundation upon which to build real-world, value based care models.
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.
But it’s difficult to truly integrate organizations, and that’s particularly true when it comes to getting disparate information systems to work together. Overall, consolidation has become more difficult because providers now have a variety of IT systems in place.
Introduction
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.
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.
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.
However, much of the world's data still resides in relational databases.
Introduction
If the administrators responsible for securing applications had their way, passwords would be long complex strings of random symbols, and users would memorize different passwords for every application they use. But in the real world, few people are capable of such prodigious feats of memory. The typical user can only remember a handful of relatively short passwords.
That’s why an increasing number of applications are requiring two-factor authentication.
Introduction
In healthcare, the outcome of a life-or-death decision can depend on the available information. To help deliver the right information at the right time and place, healthcare organizations traditionally have used HL7 interface engines to share data among clinical applications.
But the world of healthcare information technology is changing so rapidly thatHL7 interface engines are no longer sufficient. The technology landscape now includes new protocols and architectures, and the business environment has changed as well.
Using Intel® Advanced Encryption Standard New Instructions with InterSystems Caché Substantially Improves Encryption Performance and Reduces Computational Overhead
Executive Summary
Financial services companies have an ever-growing need to encrypt databases containing sensitive customer and trade data. However, using encryption on these databases can require significant computational resources, potentially impacting trading latencies.
Executive Summary
InterSystems HealthShareÆ and InterSystems EnsembleÆ both provide a rapid integration and development platform with built-in capabilities for the high-speed processing of HL7 messages. For the purposes of HL7 v2 message routing the two products are equivalent in performance. For brevity, this document will just say Ensemble in many places but it should be taken to apply equally to both products.
We have recently completed a performance and scalability benchmark of Ensemble version 2015.1, focusing on HL7 version 2 messaging.
Business Transformation for Application Providers
Introduction
InterSystems regards the enterprise service bus (ESB) as a business transformation engine for application providers.
Why the emphasis on transformation? For many application providers meeting today’s customer demands will require a change in business model. Customers are looking for unified solutions instead of application portfolios from vendors. They want these solutions delivered on their device of choice, from desktop to mobile. Above all, these solutions must be focused on the user experience.
