We have now released a new learning path to get you started with FHIR: Building Basic FHIR Integrations with InterSystems IRIS for Health. In this path, you'll learn the basics of FHIR, how to set up FHIR endpoints in InterSystems IRIS for Health, consume data into the FHIR repository and transform FHIR data, manage FHIR APIs with InterSystems API Manager, and query for FHIR resources using a client application. This path includes recommendations for starting such as using SDA-FHIR transformations to transform other formats of data to FHIR.

We're also looking at possibly creating additional

Business services are powerful components that pull data in from external sources. In most cases, pre-built components do the job, but sometimes you need to code custom business services. There are a few best practices to keep in mind when doing this:

1. Lean and Mean - Business services should be coded to have minimal processing.This is due to the fact that if any errors occur within the business service, no message will be sent, and thus no trace will be created.This makes it very difficult to troubleshoot.

Hi all,

We're in the process of creating several courses for creating custom business components for productions. This includes custom business operations, BPL processes, and custom business services. Custom Business Operations and Custom Business Services are both aimed at software developers while BPL processes can be also be created by business analysts. What are some gotchas or best practices you've learned that you wish you knew when first building these components?

We'd love to include what you've learned into these courses so others can learn from them as well!

Thanks!

Do you find yourself commonly adding code actions to your data transformations? If so, what do these contain? Is there a reason you choose to add a code action over creating a custom function that you can call?