#InterSystems IRIS for Health

12

InterSystems IRIS for Health™ is the world’s first and only data platform engineered specifically for the rapid development of healthcare applications to manage the world’s most critical data. It includes powerful out-of-the-box features: transaction processing and analytics, an extensible healthcare data model, FHIR-based solution development, support for healthcare interoperability standards, and more. All enabling developers to realize value and build breakthrough applications, fast. Learn more.

Starting out with ObjectScript, it is really exciting, but it can also feel a little unusual if you're used to other languages. Many beginners trip over the same hurdles, so here are a few "gotchas" you'll want to watch out for. (Also few friendly tips to avoid them)

NAMING THINGS RANDOMLY

We have all been guilty of naming something Test1 or MyClass just to move on quickly. But once your project grows, these names become a nightmare.

4 4
0 65
Article
· Sep 16 14m read
High Availability IAM

One of the recommendations when deploying InterSystems Technologies for production is to set up High Availability. The recommended API Manager for these InterSystems Technologies is the InterSystems API Manager (IAM). IAM (essentially Kong Gateway) has multiple deployment topologies.

Open Exchange app
6 1
3 36

Hi everyone,

I'm looking for the next job for now. My major skill is app integration (Interoperability on the IRIS platform). My coding background on Cache Object Script includes hundreds of data flows, thousands of Production business hosts, dozens of APIs, and other solutions on the IRIS Data Platform. I worked to fuse applications such as ERP, WMS, CRM, DWH, e-commerce solutions, mobile apps, marketplaces, and POS software. I have also gained experience in the Cache platform, IRIS administration, and various programming areas like SQL, Java, Mobile development (Android, Flutter).

3 0
0 22

My problem was separating HL7 messages by message type. I had to create multiple File Operations. So I with custom code I am able to use 1 File Adapter for 1 interface and multiple message types. I did experiment pulling the MSH 4 out of the raw content to further access dynamic information, but that may open a need for more robust error checking / lookup default actions.

Using the recommended naming convention of "To_FILE_<IntegrationName>"

I decided to use a generic file name and path in the default settings.

2 0
0 19