We are pleased to announce that now you can choose the preferred language of the Global Masters program! Available languages: English, Spanish, Portuguese, Japanese, Chinese.

Choose the language in your profile settings:

Red Hat Insights alerts now available for InterSystems IRIS

InterSystems and Red Hat are working together to add IRIS-specific alerts to Red Hat Insights.

gj :: locate was the entry from George James Software for the Developer Tools competition back in April 2021. When an ObjectScript error is reported, gj :: locate takes the .int line location and navigates you directly to the line in the source file where the error originated. Over the past few months we've found it a very useful tool when it comes to debugging, especially when used alongside the Serenji debugger in Visual Studio Code.

Our first update, version 1.1.0, now includes support for multi-root workspaces. This enables gj :: locate to be used with every workspace folder. If your VS Code workspace has more than one root level folder, connecting to different namespaces or perhaps different servers, then gj :: locate will determine which workspace folder is current and locate the source code in that folder. If your workspace doesn't have any files open then gj :: locate will prompt you to select a folder from a pick-list.

This will particularly benefit VS Code power users who have workspaces with simultaneous connections to multiple namespaces, on multiple different IRIS and Caché servers.

If you would like to try it out then you can download it from the VS Code marketplace. Or if you’re already a user, then gj :: locate will automatically update. Let us know how you're getting on with it!

For containers in ECS files are not editable if the file size is larger than ephemeral storage free space. For example if I have 4Gb free I can't edit 8Gb file. But if I start container with 50 Gb of ephemeral storage (24Gb free) I can edit my 8Gb file just fine.

What’s new from InterSystems Learning Services? Be the first to know – subscribe to the monthly Learning Newsletter! Read June's newsletter and subscribe. This month, you can:

Hello Again,

InterSystems Certification is still looking for people to beta test the HealthShare Patient Index Technical Specialist Certification exam. We have extended the deadline of the beta test to July 31st, 2021. For details, see the original announcement.

Thank you!

Fixing the terminology

A robot is not expected to be either huge or humanoid, or even material (in disagreement with Wikipedia, although the latter softens the initial definition in one paragraph and admits virtual form of a robot). A robot is an automate, from an algorithmic viewpoint, an automate for autonomous (algorithmic) execution of concrete tasks. A light detector that triggers street lights at night is a robot. An email software separating e-mails into “external” and “internal” is also a robot. Artificial intelligence (in an applied and narrow sense, Wikipedia interpreting it differently again) is algorithms for extracting dependencies from data. It will not execute any tasks on its own, for that one would need to implement it as concrete analytic processes (input data, plus models, plus output data, plus process control). The analytic process acting as an “artificial intelligence carrier” can be launched by a human or by a robot. It can be stopped by either of the two as well. And managed by any of them too.

Hi community,

This is another article about how to perform actions that you can do in the web portal but via code.

Today.... Add a business item in your production by code

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?

Hi Community!

Please welcome a new video on InterSystems Developers YouTube Channel:

Alexa: Connect Me with the World of IoT

https://www.youtube.com/embed/ZGYIdCTEqoQ
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

I have had a few questions about the number of HL7 messages Ensemble can handle lately, so i thought i would draw people's attention to the benchmark report

https://community.intersystems.com/documentation/ensemble-and-healthshare-hl7v2-message-throughput-0

It describes the throughput of HL7 messages with realistic messages and routing.

Dave

Hi Community!

Here is the digest of the most popular videos on InterSystems Data Platforms we published in 2018 on InterSystems Developers YouTube Channel!

And!

Please check the most popular videos by Watch Time. See the details below.