Preview kits are now published via the WRC's preview download site for:

• InterSystems IRIS 2019.1.1
• InterSystems IRIS for Health 2019.1.1
• HealthShare Health Connect 2019.1.1

The build number for these releases is 2019.1.1.608.0.

This is a maintenance release and includes changes in a number of areas, as described in the online documentation here.

It also includes three new features, described in the online documentation here:

• Support for the InterSystems API Manager,
• In-place conversion from Caché and Ensemble to InterSystems IRIS
• X12 element validation.

Hi Community,

Our latest issues of Developments  and Developments Healthcare Edition have been posted to the Developments Archive site, where you'll also find other previous issues. Learn about InterSystems API Manager, preview releases of InterSystem IRIS and IRIS for Health, and live webinars this month about how you can easily move your Ensemble or Caché applications to InterSystems IRIS. 
 

Optimize your investment in InterSystems technology by subscribing to these and other InterSystems publications.

We've just published an update to the Serenji extension for VS Code. Starting with this version (3.0.7) you can now debug the code that implements your REST services. Here's a taster:

Read more about Serenji on Open Exchange.

Hello All.

In need of some help.

We are currently migrating Interfaces from JCAPS to HealthConnect 19.1 and have done a lot of work on our Dev server.  I am looking to copy/export this work over to the Test server and have managed to export the production and Rules, HL7 custom Schemas etc.  The only thing left now are the Data Transformations but so far I can only find ways of copying the transformations over individually.  Is there some way to copy all of the transformations we have produced in our namespace to another server in one go?  

Thanks

Hi Community!

You're very welcome to watch a new video on InterSystems Developers YouTube, recorded by @Stefan Wittmann, InterSystems Product Manager:

InterSystems API Manager Introduction

Hi Community:

If you're interested in the future of InterSystems technology, you won't want to miss these nine Global Summit sessions on our hottest technologies:

Roadmap Sessions

• Business Intelligence (BI) & Analytics Roadmap
• In-Place InterSystems IRIS™ Conversions 
• InterSystems IRIS Adoption Guide
• InterSystems IRIS Cloud Roadmap
• Partner Hub: An Overview
• Personas: Your Team's Quiet Partners
• Selling InterSystems to Your Manager
• Showcase: InterSystems IRIS Directions
• User Experience Feedback: Focus on BI

REGISTER SOON. Early bird rates end August 30.

Thank you,

Jacquie

Preview releases are now available for the 2019.3 version of InterSystems IRIS and IRIS for Health!

Container images are available via the WRC's preview download site.

The version number for these releases is 2019.3.0.302.0

Public announcements will be made shortly, with separate announcements for each product.

InterSystems IRIS Data Platform 2019.3 is a CD (continuous delivery) release of InterSystems IRIS.  It has many new capabilities including:

Continuous Delivery Releases of InterSystems IRIS

InterSystems API Manager

Node-level Architecture for Sharding and SQL Support

Hi Community!

New video is already on InterSystems Developers YouTube Channel:

InterSystems Platforms and FHIR STU3

Has you may know, EnsDemo from Ensemble are not available anymore on IRIS.

This is a good thing, Iris is cloud oriented, it must be light, fast. Now the new way of sharing samples or modules is through git, continuous integration and OpenExchange.

But, in some cases you want to go back to your good old samples from EnsDemo to get inspiration or best practices.

Good news, there is a git for that :

• https://github.com/grongierisc/InstallEnsDemoLite

How to use it ?

Clone this repository

git clone https://github.com/grongierisc/InstallEnsDemoLite.git

And run install.sh

This is more for my memory that anything else but I thought I'd share it because it often comes up in comments, but is not in the InterSystems documentation. 

There is a wonderful utility called ^REDEBUG that increases the level of logging going into mgr\cconsole.log. 

You activate it by

a) start terminal/login

b) zn "%SYS"

c) do ^REDEBUG

d) change logging level to FFFFFFFF

InterSystems has corrected a memory leak in applications that pass by reference to a formal parameter that accepts a variable number of arguments.

This problem exists for:

• InterSystems IRIS Data Platform – all currently released versions
• InterSystems IRIS for Health – all currently released versions
• HealthShare Health Connect 2019.1.0

If this defect occurs, the process partition will eventually be exhausted, resulting in a <STORE> error.

Hello,

I'm new to Iris for Health and I'm trying to get some experience using it.  I've subscribed to the Intersystems Iris for Health software in AWS marketplace.  I successfully spun up the EC2 instance with the default security group.  The try-iris instance is healthy and successfully starts within EC2.  I've also successfully changed the default password too.

 However, I'm unable to authenticate into the management portal.  The portal launches okay though I keep getting an access denied.  I'm also unable to authenticate into a session from the EC2 instance.

The 2019.2 version of InterSystems IRIS for Health is now Generally Available!

Container images for IRIS for Health are available via the WRC's  download site. The build number for these releases is 2019.2.0.107.0.

InterSystems IRIS for Health  2019.2  is the first CD (continuous delivery) release of IRIS for Health.  It has many new capabilities including:

InterSystems has corrected a defect that can result in application data integrity issues following an abnormal shutdown.

This problem exists for:

• Caché and Ensemble 2018.1.2
• HealthShare Health Connect (HSAP) 15.032 on Core version 2018.1.2
• InterSystems IRIS Data Platform 2019.1
• InterSystems IRIS for Health 2019.1
• HealthShare Health Connect 2019.1

The defect breaks the journal sync guarantee that all updates in the journal buffer have been written to the journal file. The failure is silent: it does not generate an error message and there is no entry about it in any log file.

The preview release of IRIS for Health 2019.2 is now  available - give it a try!

Container images are available via the WRC's preview download site.

The build number for these releases is 2019.2.0.100.0.

InterSystems IRIS for Health  2019.2  is the first CD (continuous delivery) release of IRIS for Health.  It has many new capabilities including:

Hi Everyone!

New session recording from Global Summit 2018 is available on InterSystems Developers YouTube Channel:

InterSystems Healthcare Showcase

Hi Community!

This is the update on what are the new applications submitted on OpenExchange in March 2019

New Applications

isc-tar  published by @Dmitry Maslennikov 

Compact files as TAR or Extract files from TAR files

Light weight EXCEL download v.1.0 published by @Robert Cemper 

We can load a CCDA xml document into SDA3 object.

Once parsing SDA3 object, how do we determine from which XPATH from CCDA the specific SDA3 elements were mapped to.

Is there any way?

The 2019.1 version of InterSystems IRIS for Health is now Generally Available!

Kits and container images are available via the WRC download site

The build number for these releases is 2019.1.0.510.0.

IRIS for Health 2019.1 provides the following new capabilities:

For a solo developer developing web applications what will be the best  technology to use IRIS or Studio with cache database and containers for deployment

Breaking news!

InterSystems just announced the availability of the InterSystems IRIS for Health™ Data Platform across the Amazon Web Services, Google Cloud, and Microsoft Azure marketplaces.

With access to InterSystems unified data platform on all three major cloud providers, developers and customers have flexibility to rapidly build and scale the digital applications driving the future of care on the platform of their choice. 

To learn more please follow this link. 

The preview release of InterSystems IRIS for Health 2019.1 is now available - try it out!

Kits and container images are available via WRC's preview download site.

InterSystems IRIS for Health 2019.1 is the second major version of InterSystems IRIS for Health.  It has many new capabilities including:

Hi Community!

I'm pleased to announce that we've just launched the new product in the family of InterSystems Data Platforms:

InterSystems IRIS for Health

IRIS for Health — is the world’s first and only data platform engineered specifically for healthcare. It empowers you to rapidly create and scale the industry’s next breakthrough applications.

In the last post we scheduled 24-hour collections of performance metrics using pButtons. In this post we are going to be looking at a few of the key metrics that are being collected and how they relate to the underlying system hardware. We will also start to explore the relationship between Caché (or any of the InterSystems Data Platforms) metrics and system metrics. And how you can use these metrics to understand the daily beat rate of your systems and diagnose performance problems.

This post will guide you through the process of sizing shared memory requirements for database applications running on InterSystems data platforms. It will cover key aspects such as global and routine buffers, gmheap, and locksize, providing you with a comprehensive understanding. Additionally, it will offer performance tips for configuring servers and virtualizing IRIS applications. Please note that when I refer to IRIS, I include all the data platforms (Ensemble, HealthShare, iKnow, Caché, and IRIS).

One of the great availability and scaling features of Caché is Enterprise Cache Protocol (ECP). With consideration during application development distributed processing using ECP allows a scale out architecture for Caché applications. Application processing can scale to very high rates from a single application server to the processing power of up to 255 application servers with no application changes.

Index

This is a list of all the posts in the Data Platforms’ capacity planning and performance series in order. Also a general list of my other posts. I will update as new posts in the series are added.

You will notice that I wrote some posts before IRIS was released and refer to Caché. I will revisit the posts over time, but in the meantime, Generally, the advice for configuration is the same for Caché and IRIS. Some command names may have changed; the most obvious example is that anywhere you see the ^pButtons command, you can replace it with ^SystemPerformance.

While some posts are updated to preserve links, others will be marked as strikethrough to indicate that the post is legacy. Generally, I will say, "See: some other post" if it is appropriate.

Capacity Planning and Performance Series

Generally, posts build on previous ones, but you can also just dive into subjects that look interesting.

• Part 1 - Getting started on the Journey, collecting metrics.
• Part 2 - Looking at the metrics we collected.
• Part 3 - Focus on CPU.
• Part 4 - Looking at memory.
• Part 5 - Monitoring with SNMP.
• Part 6 - Caché storage IO profile.
• Part 7 - ECP for performance, scalability and availability.
• Part 8 - Hyper-Converged Infrastructure Capacity and Performance Planning
• Part 9 - Caché VMware Best Practice Guide
• Part 10 - VM Backups and IRIS freeze/thaw scripts
• Part 11 - Virtualizing large databases - VMware cpu capacity planning

++Update: August 2, 2018

This article provides a reference architecture as a sample for providing robust performing and highly available applications based on InterSystems Technologies that are applicable to Caché, Ensemble, HealthShare, TrakCare, and associated embedded technologies such as DeepSee, iKnow, Zen and Zen Mojo.

Azure has two different deployment models for creating and working with resources: Azure Classic and Azure Resource Manager. The information detailed in this article is based on the Azure Resource Manager model (ARM).