Welcome to the next chapter of my CI/CD series, where we discuss possible approaches toward software development with InterSystems technologies and GitLab.
Today, we continue talking about Interoperability, specifically monitoring your Interoperability deployments. If you haven't yet, set up Alerting for all your Interoperability productions to get alerts about errors and production state in general.

Inactivity Timeout is a setting common to all Interoperability Business Hosts. A business host has an Inactive status after it has not received any messages within the number of seconds specified by the Inactivity Timeout field. The production Monitor Service periodically reviews the status of business services and business operations within the production and marks the item as Inactive if it has not done anything within the Inactivity Timeout period.
The default value is 0 (zero). If this setting is 0, the business host will never be marked Inactive, no matter how long it stands idle.

This is an extremely useful setting since it generates alerts, which, together with configured alerting, allows for real-time notifications about production issues. Business Host being idle means there might be some issues with production, integrations, or network connectivity worth looking into.
However, Business Host can have only one constant Inactivity Timeout setting, which might generate unnecessary alerts during known periods of low traffic: nights, weekends, holidays, etc.
In this article, I will outline several approaches towards dynamic Inactivity Timeout implementation. While I do provide a working example (currently running in production for one of our customers), this article is more of a guideline for building your own dynamic Inactivity Timeout implementation, so don't consider the proposed solution as the only alternative.

Improved Access to Clinical Data Across Hospitals and Systems Helps Pharmaceutical Companies Reduce Delays and the Costs Associated With Bringing New Treatments to Market

Executive Summary

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.

The strategies surveyed in this document are based on three different HA technologies:

Hi Community,

Watch this video to find out how these digital health startups are improving workflows for disease management, remote patient monitoring, and patient engagement:

⏯ Digital Health Showcase - Virtual Care @ Global Summit 2023

https://www.youtube.com/embed/-_lZ1CGqB9I
[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]

When you are in a group looking at the postings

- search for a keyword that gets no results

- clear the search box to get back to the full list

- notice the "Create a New Post" button is gone from the upper-right

MacOS \ Chrome

InterSystems FAQ rubric

To enable Interoperability functionality after creating a namespace, use the EnableNamespace method of the %EnsembleMgr class:

do ##class(%EnsembleMgr).EnableNamespace()

clinFHIR is a web application that has been developed pretty much over the same time as FHIR has.

Originally developed to help clinicians visualize FHIR (hence the ‘clin’ in the name) it has become more widely used by the FHIR community for learning FHIR and assisting with design. It is maintained by David Hay - one of the FHIR Management Group co-chairs with support from InterSystems, which is much appreciated!

There are 4 modules that may be of interest to participants in the upcoming Interoperability contest.

• The Patient viewer for looking at an individual patients records
• Server Query which makes RESTful API calls against a FHIR server displaying the result in different formats
• Bundle Visualizer which will display the contents of a bundle
• Graph Builder which allows you to build graphs of interconnected resources.

I’ve created a longer post on google docs that goes into a little more details of these modules, with links to other resources such as my blog and the R4 Specification and R5 FHIR specification. I’ll be enhancing that over time - feel free to comment.

A note with regard to FHIR versions. The latest version is R5 (release 5), though many in the community still use R4. In most cases, if you're not sure then use R4. If you're not sure which version a FHIR Server supports, examine its CapabilityStatement which you can get from the server endpoint [host]/metadata

I should also point out that clinFHIR doesn’t currently use SSL. It is on the roadmap, but there are a few issues to work through. The consequence of this is that if you enter ‘clinfhir.com' into the browser, it may not find it. You sometimes have to specify http://clinfhir.com/ .

If you need further assistance, I would alway recommend using the FHIR chat, and if your question / comment / suggestion is related to clinFHIR then there’s a specific stream there.

The latest release of Serenji focuses on the debug experience. Not only can you now debug on the spot, no matter where you are or what you're doing, but we've also added some smaller features that will make debugging more straightforward. 

• Run and Debug CodeLenses - clickable links above each class method, procedure, subroutine or extrinsic function.
• Intuitive prompting for entrypoints and arguments - when debugging a class method, produce, subroutine or extrinsic function. 
• Shaded read-only background - to clearly differentiate between documents which are editable and those that are read-only. 
• Program output in debug console - output is shown in the debug console. 
• Serenji commands on Server Manager's namespace trees - allowing you to launch Serenji through Server Manager. 

Find out more in our release notes here. 

Do you need to build an object-oriented application using Caché? Take this course to learn how to create, retrieve, update and delete objects in Caché.

Caché Objects Introduction

Hi Everyone!

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

Creating an Event Management Service

https://www.youtube.com/embed/D9vo0shPf24
[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]

InterSystems FAQ rubric

The $ZF(-100) command is used in the following format.

$ZF(-100, flags, command name, command arguments)

The "/shell" flag is required when running OS commands.
For example, use mkdir like this:

In the last article we presented the architecture of our SMART On FHIR project, so it's time to get down to business and start configuring all the elements that we are going to need.

We will first start with Auth0.

AUTH0 configuration

We will start by creating an Auth0 account with a valid email, once registered we will have to create our first application, and we will do it from the menu on the left:

Hey Community,

Get an introduction to the purpose and key concepts of Fast Healthcare Interoperability Resources, or FHIR:

⏯ FHIR: Healthcare Data Standard Designed for the Future

https://www.youtube.com/embed/xr-xSGPe96k
[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]

Hi Community,

Learn about strategic approaches being taken to leverage the potential of HL7 FHIR in InterSystems HealthShare:

⏯ The Promise of FHIR

https://www.youtube.com/embed/Qo3nTn2WilU
[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]