#InterSystems IRIS for Health

Hi All, I'm in the process of trying to rollout the git version control system with our current code base within Atelier.  We use Ensemble to develop interfaces but are looking to move to IRIS in the near future.  Our code is structured similar to below:

Site

           System1

Routers

Processes

Transformations

Data

Services

Operations

…

System2

Routers

Processes

Transformations

Services

Operations

Data

…

Productions

Routers

Operations

My initial thoughts are that we would have three repositories.  One for DEV, TEST and PROD.

I am playing with the FHIR Sandbox.

I want to sort the patients returned in the bundle from the Patient search using the _sort (according to FHIR standard the _sort parameter is what should be used to sort), but I get: "Invalid request URL parameter _sort specified"

So I am having to assume that InterSystems did not implement _sort.

This week I am going to look at CPU, one of the primary hardware food groups :) A customer asked me to advise on the following scenario; Their production servers are approaching end of life and its time for a hardware refresh. They are also thinking of consolidating servers by virtualising and want to right-size capacity either bare-metal or virtualized. Today we will look at CPU, in later posts I will explain the approach for right-sizing other key food groups - memory and IO.

Session : Working with the FHIR Resource Repository

We tried below steps to create and load sample data from Synthea (FHIR data).

1. Open terminal
2. USER>zn "HSLIB"
3. HSLib> do ##class(HS.HC.Util.Installer.FHIR).Install()
4. Namespace  : FHIRServer
5. Install DSTU2? (Y/N) N
6. Install STU3? (Y/N) Y
7. STU3 CSP app [/csp/healthshare/fhirserver/fhir/stu3]:
8. STU3 CSP Open ID Connect (OAuth 2.0) app [/csp/healthshare/fhirserver/fhir-oidc/stu3]:
9. Install STU3 resource repository? (Y/N) Y
10. Install STU3 PIXm? (Y/N) N
11. Install STU3 PDQm? (Y/N) N
12. Install STU3 MHD? (Y/N) N
13. Continue with Installation?

Hi everyone,

I am pleased to announce that the Evaluation Service is now LIVE!

If you are an InterSystems End User or an InterSystems Partner and you want to try the latest version of IRIS with all its enterprise features (mirroring, ECP and sharding), and you want it NOW, this is for you.

The Evaluation Service allows you to get your hands on an IRIS kit and a very powerful IRIS license for evaluation purposes in less than 1 minute. No paperwork. No need to talk to anyone. Fully self-service.

This service is only for IRIS and IRIS for Health and it is very easy to use.

InterSystems has corrected a defect in applications that use Unicode character 223 (ß). This defect can result in incomplete query results, class compilation errors, and removal of custom SQL privileges.

This problem occurs on systems that are running or have previously run on:

• Caché and Ensemble 2018.1.0, 2018.1.1, and 2018.1.2
• HealthShare Health Connect (HSAP) 15.032 on Core versions 2018.1.0, 2018.1.1, and 2018.1.2
• HealthShare Health Connect 2019.1
• InterSystems IRIS data platform – all currently released versions
• InterSystems IRIS for Health – all currently released versions

The defect is triggered by data and component names containing Unicode character 223 (ß). In the versions listed above, an uppercase conversion incorrectly maps that character to Unicode character 7838 (ẞ).  Applications perform this uppercase conversion using features such as $ZCONVERT and %SQLUPPER.

Problems can occur when accessing data or classes created or modified on a product with a different uppercase conversion than the one currently in use.

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

Infrastructure and Cloud Deployment Improvements

Port Authority for Monitoring Port Usage in Interoperability Productions

X12 Element Validation in Interoperability Productions

New Framework for Coding Business Hosts in Java

Java and .NET Gateway Reentrancy

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

sh install.

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:

• enhancements to FHIR STU3 support
• additional IHE profiles
• a new JMS (java message service) connector
• Addition of the IRIS Native API for Python and Node.js and relational access for Node.

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:

• enhancements to FHIR STU3 support
• additional IHE profiles
• a new JMS (java message service) connector
• Addition of the IRIS Native API for Python and Node.js and relational access for Node.

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

This is the working example of a light weight export to EXCEL based on data in SAMPLES namespace. Good old CSP is well equipped to produce HTML tables accepted from EXCEL as input. With modern Browsers you don't even need and tags. So the required code around your SQL result set is really slim. And you are free to add any formatting you need either by HTML or in SQL.

PythonGateway v.0.7 published by @Eduard Lebedyuk

Python Gateway for InterSystems Data Platforms.

Adopted Bitmaps v.1.0 published by @Robert Cemper

This is a running example of the Bitmap Adoption

WebSockets Tutorial v.1.0 published by @Lily Taub

A short tutorial on WebSockets in InterSystems IRIS 2018.1+ and Caché 2016.2+

Sync Data with DSTIME v.1.0.0 published by @Robert Cemper

Other Sync-Tools just work from Caché/IRIS to Caché/IRIS. Synchronizing your data to some external DB you requires some other solution. DSTIME can do it.

HL7 and SMS Interoperability Demo v.1.3 published by @Amir Samary

This demo shows how easy it is to integrate an Electronic Medical Record system that is sending HL7 messages with AWS.

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:

• Interoperability. The latest release further expands the product’s schema, transformation, routing, and testing capabilities, supporting integration and service aggregation as a key enabler of digital transformation initiatives.

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:

• Significant enhancements to SQL usability and performance
• Improved scalability and operations for sharded clusters
• Client language updates and performance boosts
• New interoperability capabilities that speed configuring and troubleshooting of productions
• Updates to FHIR support and message transformations.

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).