#Interoperability

Hey Developers,

See how API management can simplify healthcare application development with FHIR:

⏯ FHIR API Management @ Virtual Summit 2020

https://www.youtube.com/embed/VfO-hLmRhB0
[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 Developers,

A new video is already on InterSystems Developers YouTube:

⏯ Creating an HL7 v2 to FHIR Transformation Pipeline with S3 Target

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

Productions often need to receive REST requests.

Here's how to do that.

1. Create proxy Service:

/// Empty BS we would use to send Produciton requests
Class production.ProxyService Extends Ens.BusinessService
{
}

2. Add it to production as RESTService (or any other name).

Hi Community,

We're pleased to invite you to the upcoming webinar in Spanish called "Interoperability in FHIR"!

Date & Time: June 23, 4:00 PM (CEST)

Speaker: @Ricardo Paiva, Sales Engineer, InterSystems Iberia

How can FHIR coexist and integrate with other protocols?

In this article, I will show how you can easily containerize .Net/Java Gateways.

For our example, we will develop an Integration with Apache Kafka.

And to interoperate with Java/.Net code we will use PEX .

Architecture

Our solution will run completely in docker and look like this:

Hi Community,

Please welcome the new video on InterSystems Developers YouTube:

⏯ FHIR Overview @ Virtual Summit 2020

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

The file passthrough service isn't recognizing the timestamp variables. I tried multiple iterations of using timestamp variables without any luck.

The filename format is DCVaccine_20210520.txt.

The current File Spec is "DCVaccine_%Y%m%d.txt" in the service.

According to IDC, more than 80% of information it is NoSQL, especially text into documents. When the digital services or applications not process all this information, the business lose. To face this challenge, it is possible use OCR technology. OCR uses machine learning and/or trained image patterns to transform image pixels into text. This is important, because many documents are scanned into images inside PDF, or many documents contains images with text inside. So OCR are an important step to get all possible data from a document.

We are migrating from 2017.1 to Nice New Iris. Data conversion is fine. However, we would like to do a "global" Enable="false" on all the production's services and operations. Is this possible? Working through the operations and services will be tedious! Any code that can do this would be a great help.

Thanks

Managed File Transfer (MFT) feature of InterSystems IRIS enables easy inclusion of a third-party file transfer service directly into an InterSystems IRIS production. Currently, DropBox, Box, and Kiteworks cloud disks are available.

In this article, I'd like to describe how to add more cloud storage platforms.

Here's what we're going to talk about:

• What is MFT
• Reference: Dropbox
  • Connection
  • Interoperability
  • Direct access
• Interfaces you need to implement
  • Connection
  • Logic
• Installation

Hi all,

I have a very weird error when I'm calling to a SOAP Webservice as client.

I've create all objects to invoke to this SOAP using the add-in "Assistant SOAP" in Eclipse, it has created all objects (Response, Request, Business operation WS class, etc...).

When I call to this service it retuns the following error message:

ERROR #6243: HTTP request to SOAP WebService returned unexpected CONTENT-TYPE response: text/html.

This article is a continuation of this post.

In the previous article, how the Interoperability menu works for system integration was explained.

In this article, I would like to explain how to develop a system integration using the Interoperability menu.

This article is a continuation of this post.

In the previous article, we reviewed how to create and define messages used to send and receive data between components.

This article is a continuation of this post.

In the previous article, we discussed the development of business processes, which are part of the components required for system integration and serve as a production coordinator.