Also you can just do (in IRIS for Health):

USER>zpm "install fhir-server -dev"

And you'll have it setup in "FHIRSERVER" namespace with fhir server R4 at /fhir/r4

Hi @Fahima Fahima !

You can check this example by @Guillaume Rongier 
 

Hi @Ali Chaib !

1. Yes, it can work with POST, GET and PUT out of the box.

2. The data is stored in IRIS database, in global arrays - as any data other stored via InterSystems data products.

3. FHIR server exposes standard FHIR R4 REST API which you can access via HTTP requests.

4. These classes help with development Digital Health Interoperability scenarios, e.g. if you have to establish perpetual processes to read from FHIR server and/or transform the data into other formats (e.g. HL7) and/or send it into different consuming applications.

5. This can be implemented via Digital Health interoperability framework. See the example.

I request @Patrick Jamieson and @Daniel Franco to provide more information.

Yes, that's a pain. That's why we suggest the naming convention of everything in lowcase for UDL class packages.

wow. @Jeffrey Drumm , do you want to publish the class on Open Exchange too?

Community images can be used for now:

intersystemsdc/irishealth-community:latest

and 

intersystemsdc/iris-community:latest

Hi @Prasanth Annamreddy !

Here is the example project by @Guillaume Rongier that demoes how to convert FHIR to HL7 using DTL.
 

Also see  the question

I'm using VSCode to code on IRIS that starts from Docker. And with this approach you have the Terminal available in a menu - see the screenshot and loom:

Loom video

The only drawback - there is no Microsoft Solitaire :)

Jokes aside maybe you'll miss InterSystems Studio. But VSCode does more than Studio can.

Also Docker is much more stable on Mac.

They are "special" :) and called locals for variables and globals for persisted variables.

in case if you are in debug you can always print out the array with zwrite array_name. E.g. in your case:

USER>zw args

will print out all the data it contains. useful for understanding and debugging.

Hi @Colin Brough !

I don't know if you can use IRIS but if yes docker+IRIS is a perfect combination for desktop operations.

Hi @Jordan Everett !

You can debug in terminal using ZBreak And Break commands.

E.g. insert in the ObjectScript code a new line where you need to step-by-step debugging:

Break "L"

which means turn on interactive terminal debugging with line-by-line mode

and use "go" command to run the line of code.

In addition to what @Dmitry Maslennikov told here is the way to enable IRIS BI(Analytics) programmatically:

do EnableDeepSee^%SYS.cspServer("/csp/user/")

You can use InterSystems Package Manager(IPM) to list all the members of production and distribute it to another machine (e.g. your client) via the IPM registry, or using zpmhub.

E.g. you can install several EnsDemo productions as one package:

USER>zpm "install irishealth-ensdemo"

Or recently I published an example of a very simple CSV data transformation production that you can install as one line:

USER>zpm "install esh-i14y-csv"

And here is how all the modules of production depicted in a module.xml.

Hi @Julian Matthews !

I'd suggest using IPM modules for deployment where you suggest what is included in the module. Here is an example of module with simple Interoperability production.

Hi @Dmitrii Baranov!

Check this basic iris-dev template on the Open Exchange. As you can see it installs git in Dockerfile changing user to root and back to iris-owner:

## install git
## USER root   
##RUN apt update && apt-get -y install git
##USER ${ISC_PACKAGE_MGRUSER}

if uncommented it installs git via user root. I hope this is what you wanted.