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.

UPDATE

Recently we introduced a yet another Instruqt interactive foundation course on Digital Health Interoperability with IRIS for Health - please give it a try here! It will help everyone who is new to InterSystems Digital Health Interoperability productions to go through several simple but illustrating scenarios and get a great foundation for building your ones!

Enjoy!

In addition to what @Ben Spead suggested there are several more hands-on labs on this site: REST+ Angular, Machine Learning and Interoperability. 

Also, there are several Developer Learning Paths on the Online Learning platform that will help you to start with ObjectScript Development.

Once you’ve got the basics I recommend to start coding using Docker enabled templates on Open Exchange - you can find templates with the Template filter on.

For example I recommend a basic ObjectScript template or basic REST API with ObjectScript template.

HTH

Technically tarball downloading feature refers to ZPM Registry package, which is intended to host IPM packages. And as folks mentioned above you can use it as the private registry hosting in your organization with the option to proxy some public packages.

I filed the ticket to update the documentation on tarballs.

And I think it makes sense to add the link to tarball download in Open Exchange for IPM packages.

These are good points. IPM(ZPM) is officially supported now by InterSystems, so I'm tagging @Bob Kuszewski and @Timothy Leavitt on providing more information.

Here is the current documentation of IPM and it contains the information on how to load from tarballs here.

As for the option to download the package tarball it is indeed not very documented as it is a relatively rare case that people cannot use Internet to install the community package. 

Tarball can be downloaded from the community IPM Registry REST API requested in a format:

https://pm.community.intersystems.com/download/[package-name]/-/[package...

e.g. here is the URL for git-source-control:

https://pm.community.intersystems.com/download/git-source-control/-/git-...