#HealthShare

As we said yesterday... our EMPI can receive data from multiple sources, REST, HL7 messaging, etc. But it is possible that the standard fields are not enough and we want to expand the patient information to help discriminate and uniquely identify them. How could we customize patient data? Modifying the standard classes to our liking? NOOOOO!!!! Well, a little yes, but not like crazy, because if we modify standard classes carelessly we may find that in a future update we lose all these modifications.

Please let your clients and others on your ISC team know that currently there are spots available for the following June courses which currently have a low registration:

Hi Community,

Watch this video to learn about the new and future changes to the security framework in the HealthShare product suite. Topics include OAuth 2.0, SSO, and the Universal Login Page:

⏯ Updates in Security in the HealthShare Suite @ Global Summit 2022

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

In over a decade of using Ensemble/HealthShare, we have been able to use a single message type (doc type) for all HL7 ADT event types. We now have an application for which the HL7 segment sequence is different for A03s than it is for other ADT event types. The content of the segments is the same across event types; only the segment sequence differs. The data transformation has to do some custom logic, so we can't just use the "copy" variety of the transformation Create property.

Please help,

I'm using a SearchAndFetchRequest to retrieve a full SDA3 Container from the ACCESS gateway. The response is presented in the pResponse.SearchAndFetchGeneralResult.XMLData property. This property is of type string. I want to put the data from this property in a HS.SDA3.Container and then use this container is a dtl for translation purposes. My current data in the XMLData property is too large to fit in a string. Therefore I'm searching for a way to convert te data to a stream and that import the stream into my Container...

I am having a difficult time trying to get DEBUGGING tags working in my xslt transform.

Here are snippets of the xslt I am using:

namespace declaration:

Hello everyone,

I am looking for a sort of REST interoperability adapter that can forward REST calls within HealthConnect. If necessary, we need to adjust the requests or responses.

For Fhir calls, we use the FHIR Interoperability Adapter. This works perfectly; a message comes in as HS.FHIRServer.Interop.Request, and a message HS.FHIRServer.Interop.Response goes out. I can make adjustments as needed to both the request and response. I am looking for the same functionality, but then for non-FHIR REST calls.

I'm working with a client who has InterSystems in his hospital to the management of patients and nurses. Now he want to develop a web app which can schedule nurse sift. Is there any way I can authenticate the user from his hospital InterSystems and get data from the system when ever the user login through the web app.

Sync operation in registry is not receiving any request from ODS. I have tried to synchronize from Registry management however, sync operation doesn't receive any request.

HSODS>w ##Class(Ens.Director).StartProduction()

Deltanji 7.1 is now available.

Key updates include: 

* Interoperability Production component driver included, for customers who have purchased the add-on. You can watch a short demo of it here.
* Implement multi-select delete of objects and components
* Add setting to give a passable Beyond Compare launch command line
* Support simplified Locations & Routes diagram 

For more information, read the release notes here >> https://bit.ly/3mHyJHc

Please get in touch with support@georgejames.com for your release kit. 

The update is also available for Serenji debugger users on VS Code, which has the Deltanji solo edition embedded. Simply update the Serenji extension to version 3.2.3 or later and load the server-side code. 

A common need for our customers is to configure both HealthShare HealthConnect and IRIS in high availability mode.

It's common for other integration engines on the market to be advertised as having "high availability" configurations, but that's not really true. In general, these solutions work with external databases and therefore, if these are not configured in high availability, when a database crash occurs or the connection to it is lost, the entire integration tool it becomes unusable.

InterSystems is pleased to announce the 2023.1 release of InterSystems IRIS Data Platform, InterSystems IRIS for Health, HealthShare Health Connect, and InterSystems IRIS Studio are now Generally Available (GA).

2023.1 is an Extended Maintenance (EM) release. Many updates and enhancements have been added in 2023.1.

InterSystems is pleased to announce that the extended maintenance release of InterSystems IRIS, InterSystems IRIS for Health, and HealthShare Health Connect 2022.1.3 is now available. This release provides a few selected features and bug fixes for the previous 2022.1.x releases.

You can find additional information about what has changed on these pages:

InterSystems FAQ rubric

The ID of the last updated record can be obtained using the SQL function LAST_IDENTITY().
* This function can be used with embedded SQL or ODBC but not with Dynamic SQL, SQL Shell, or the Management Portal's SQL interface.

Here's an example of usage with simple Embedded SQL: