#HealthShare

Strategic Interoperability

Executive Overview

This white paper discusses the critical requirements for the U.S. Departments of Defense (DoD) and Veterans Affairs (VA) to share Service members’ medical records – including real-time access to a complete composite health record – and it proposes an immediate solution via implementation of a health informatics platform. This approach will provide significant and clearly visible results in a matter of months, while positioning the Departments for strategic improvements in the years ahead.

Slowness of the 'Source' and 'Target' parameters in the (portal) Message Viewer is caused by the Bitmap indices of Ens.MessageHeader.

Running the 'bitmap index clean up' routine for Ens.MessageHeader will fix the issue.

I checked with WRC and they advised:

Schematron is a rule-based validation language for making assertions about the presence or absence of certain patterns in XML documents. A schematron refers to a collection of one or more rules containing tests. Schematrons are written in a form of XML, making them relatively easy for everyone, even non-programmers, to inspect, understand, and write

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.

Introduction.

Have you ever felt like your PDF files take up too much space on your server? As you collect more and more of these files, you might run into storage issues that can be costly to solve. But what if there was a way to shrink the size of these PDFs by 50% to 70% without compromising the document's visual clarity.

Today, we're going to explore a solution for this problem that I really like: GhostScript.

After upgrading an Information Exchange/HealthShare instance that has a registry namespace, you may notice that the Caché audit log gets filled with frequent login failures by the HS_Services user (check this by going to Management Portal > System Administration > Security > Auditing > View Audit Database). Clicking the “details” shows event data like:

Error message: Access Denied
CSP Application: /csp/healthshare/hsregistry
Authentication: Delegated

Presenter: Alex MacLeod
Task: Understand and use IHE in HealthShare
Approach: Provide a real-world example of a successful IHE implementation

In this session, we will discuss the basics of IHE in HealthShare, as well as share a real world example of a successful IHE implementation.

Content related to this session, including slides, video and additional learning content can be found here. Please note that this content is available only to HealthShare customers and attendees of the Global Summit. On the learning web site you will be prompted for your Global Summit credentials to access this content.

In this article, I am demonstrating how to create a table column(formerly known as properties) with your custom datatype classes by using User defined DDL. Properties are the crucial member of the persistent class definition. Datatypes are essential to define types of values that are stored in a table column. In general, the datatype names of SQL different from Intersystems datatypes, such as VARCHAR = %String.

HealthShare HealthConnect and Information Exchange version 15.03 support import transformations from C-CDA 2.1 to SDA. You can find these transforms in your installation's csp/xslt/SDA3 directory. For general information about import transforms, see "CDA Documents and XSL Transforms in HealthShare" in Overview of Health Connect.

Among the enhancements to import functionality added in connection with C-CDA 2.1 support is the ability to preprocess your C-CDA input files prior to the transformation done for import.

Presenter: Boris Mamkin
Task: Understand and use CDA in HealthShare
Approach: Provide a real-world example of how the Clinical Document Architecture standard is being used in a clinical integration

In this session, we will discuss the basics of using CDA in HealthShare, as well as a real world example of how CDA is being used in a clinical integration.

Content related to this session, including slides, video and additional learning content can be found here. Please note that this content is available only to HealthShare customers and attendees of the Global Summit. On the learning web site you will be prompted for your Global Summit credentials to access this content.

One of my colleagues had developed an interface in Health Connect (HealthShare 2019.1) to add large amounts of data to an external SQL Server database. The data comes from many text files with delimited rows and data for one table per file. There is a business process to read a file line by line and send an Insert Request to an operation.

I have been struggling with a docker run command that kept crashing, the error message was too generic to point me to the right direction.

Since the container is shut down after the failure, I was unable to login to it in order to figure out the problem.

I had to run the container in a way that I'll be able to log into it before it crashed, so I found the adding -u false prevents the docker run command to run the iris session IRIS and the container stayed up and running. then I was able to log into it using:

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.

IRIS can use a KMS (Key Managment Service) as of release 2023.3. Intersystems documentation is a good resource on KMS implementation but does not go into details of the KMS set up on the system, nor provide an easily followable example of how one might set this up for basic testing.

The purpose of this article is to supplement the docs with a brief explanation of KMS, an example of its use in IRIS, and notes for setup of a testing system on AWS EC2 RedHat Linux system using the AWS KMS. It is assumed in this document that the reader/implementor already has access/knowledge to set up an AWS EC2 Linux system running IRIS (2023.3 or later), and that they have proper authority to access the AWS KMS and AWS IAM (for creating roles and polices), or that they will be able to get this access either on their own or via their organizations Security contact in charge of their AWS access.