#Health Connect

1

InterSystems HealthShare Health Connect is a healthcare integration engine that delivers high-volume transaction support, process management, and monitoring to support mission-critical applications. 

At the heart of Health Connect is a high-performance, multi-model data engine that seamlessly handles multiple forms of data at high speed. Health Connect easily scales from serving small clinics to handling the transaction volumes of the largest and most complex healthcare delivery systems in the world. Capabilities include:

  • Interoperability by design
  • Mirroring with fast failover recovery
  • Source control for HL7 schemas
  • Intuitive drag-and-drop HL7 schema editing
  • A flexible, adaptable security model and more

I created a Custom Search Table that extends EnsLib.HL7.Search Table. I saved, compiled, and rebuilt the index however when I go into Message Search to try to use the Search Table, within the conditions the proper fields are not showing up that was defined. It is showing the fields from EnsLib.HL7.SearchTable. I did a build index on both EnsLib.HL7.SearchTable and OSU.HL7.SearchTable.

1 6
0 50

Build 2025.1.0.1.24372U.f00326d.

Overview


This release delivers expanded Azure support for InterSystems Data Fabric Studio, enhanced subscription flexibility, major module updates, and multiple improvements to networking, security, and API responsiveness.

New Features and Enhancements

Category

Feature/Improvement

Details

Azure Support

4 0
1 53
Contestant

#InterSystems Demo Games entry

⏯️ Being READY to Tackle Healthcare Enterprise Challenges in a Few Clicks

Managed Cloud Solutions to Help Streamline Your Health Services.

This demo showcases composing several InterSystems Managed Cloud Services to solve various use-cases.

The video is actually built of 6 short chapters (each ~2.5 minutes long) showing each part of the story, demoing a different service.

You can watch each "chapter" individually if you're interested in a specific service, but there is value in viewing the whole composition and observing the full flow.

  • 0:00 Health Connect Cloud - Medical Device MQTT - HL7v2 for Hospital Operation Systems
  • 2:29 FHIR Server & FHIR Transformation Service - HL7v2 to FHIR & Repository for Regulation & Exchange
  • 5:21 FHIR SQL Builder - Providing standard relational access to FHIR data
  • 7:22 "FHIR IntelliChat" (see note below) - Natural human language chat with FHIR Server
  • 9:37 OMOP Solution - FHIR to OMOP transformation & OMOP database with OHDSI tools compliance
  • 12:54 InterSystems Data Fabric Studio for Health - Creating a multi data/app sources fabric

[Note the "FHIR IntelliChat" part is not an actual formal InterSystems service, it is just a demonstration of a possibility (based on this solution by @José Pereira) ]

Presenters:
🗣 @Tani Frankel, Sales Engineer Manager, InterSystems
🗣 @Keren Skubach, Senior Sales Engineer, InterSystems
🗣 @Ariel Glikman, Sales Engineer, InterSystems

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

16 0
0 30

Using a WSDL and the SOAP wizard I created a WebServiceClient, and Operation to send an encoded message to a Vendor. But the vendor is now sending back an HL7 in the SOAP response.

I tried updating the Operation to Extend EnsLib.HL7.Operation.ReplyStandard, but still use the EnsLib.SOAP.OutboundAdapter. When I did this it broke my Operation and would not compile with the following error...

0 0
0 28

We have a task that runs objectscript code to load data into a linked external table. After upgrading from 2024.1 to 2025.1, the load is throwing an error, with error code -400, and no error message. The data DOES get loaded into the external table in its entirety, so with no meaningful error message, its hard to determine what the issue is. The result is the same with and without the USING clause, so don't let that confuse you. We have logs of this statement succeeding before upgrade, and were able to get this statement to work in our production environment, which is still on version 2

0 0
0 26

We currently have Business Operation that we built to use the EnsLib.SQL.OutboundAdapter so we can make Microsoft SQL Server Stored Procedure calls. The BO is attached to a Java Gateway Service.

Some of our MS SQL Databases have moved from being OnPrem to Azure Cloud. We have started seeing where we are receiving errors on the BO saying that we cannot connect to the Azure Database, but we never receive a Disconnect from the Azure Database.

0 2
0 20