Search

Hey developers, We want to hear from you! Give us your feedback on the InterSystems Grand Prix Contest! Please answer some questions to help us improve our contests. 👉🏼 Quick survey: InterSystems Grand Prix Contest Survey Or please share your thoughts in the comments to this post!

Hi Community, Find out how to work with FHIR profiles and conformance resources when building FHIR applications on InterSystems IRIS for Health: ⏯ Working with FHIR Profiles in InterSystems IRIS for Health 👉🏼 Subscribe to InterSystems Developers YouTube. Enjoy and stay tuned!

Hi Developers, I am glad to announce Git for InterSystems IRIS, my first submission to OpenExchange and part of the current Developer Tools Contest. Git for InterSystems IRIS is a source control package that aims to facilitate a native integration of the Git workflow with the InterSystems IRIS platform. It is designed to work as a transparent link between InterSystems IRIS and a Git-enabled code directory that, once setup, requires no user interaction. A detailed description can be found on GitHub. I am looking forward to learn what you think about this approach. Does it make sense? Would this help you with establishing a Git-based deployment pipeline? Are there any issues that may have been overlooked? A ready-to-run docker demo is available on OpenExchange. The application is in a usable proof-of-concept state, with some features still to be implemented. I am happy to receive any feedback from you. Thank you for publishing!! I am curious ... did you start with one of the existing open source Git hooks for ObjectScript or did you start from scratch with this project? Hi Ben, the project started as a fork of Caché Tortoize Git, which was a good starting point, and initially I intended to change only a few things. As development went on, however, most of the code has been rewritten and I think only 10-20% is left from the original code. There were just too many differences in the basic concepts, including the Globals structure, handling of namespaces and projects, and interaction with Git (hooks -> REST) and Studio (none). This is really interesting - I've been starting on a similar project with the same starting point. Got it Marcus - thanks for the history :) Thank you Marcus, great initiative! Any thoughts about how to manage environment specific variables in the pipeline e.g. different interoperability host configurations for dev / prod? @Janne.Korhonen - typically these are managed using System Default Setting: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=ECONFIG_other#ECONFIG_other_default_settings Hello Marcus, Thank you for sharing. I'm building a dockerised DEV environnement. The main issue I am encountering at this moment is the modification from the portal of Business Process or Transform for exemple. I have to export manually my new processes. If I forget it, I just lose it ... I try to install and configure GIT directly on my image. The aim is to link my local repo to the container. I don't want GIT at all. This way, I will have a automatical export. But, it is quite difficult to use in command line. I always have to perform an INIT when I start my container. I tried to perform an init from my DockerFile (do ##class(SourceControl.Git.Utils).UserAction("","%SourceMenu,Init")) but it does not work. Do you have a clean way to install and configure GIT from a DockerFile ? Thanks Regards, Matthieu. My iris start in my DockerFile : RUN iris start IRIS \ && iris session IRIS -U %SYS < /tmp/iris.script \ && iris stop IRIS quietly my iris.script : //On installe ZPM set $namespace="%SYS", name="DefaultSSL" do:'##class(Security.SSLConfigs).Exists(name) ##class(Security.SSLConfigs).Create(name) set url="https://pm.community.intersystems.com/packages/zpm/latest/installer" Do ##class(%Net.URLParser).Parse(url,.comp) set ht = ##class(%Net.HttpRequest).%New(), ht.Server = comp("host"), ht.Port = 443, ht.Https=1, ht.SSLConfiguration=name, st=ht.Get(comp("path")) quit:'st $System.Status.GetErrorText(st) set xml=##class(%File).TempFilename("xml"), tFile = ##class(%Stream.FileBinary).%New(), tFile.Filename = xml do tFile.CopyFromAndSave(ht.HttpResponse.Data) do ht.%Close(), $system.OBJ.Load(xml,"ck") do ##class(%File).Delete(xml) do ##class(%SYSTEM.Process).CurrentDirectory("/opt/irisapp") //On charge les installer et les deployer do $SYSTEM.OBJ.Load("InstallerLibrary.cls", "ck") //On installe les namespaces set sc = ##class(App.InstallerLibrary).setup() // Je ne sais pas pourquoi mais je dois redéfinir le dossier de travail do ##class(%SYSTEM.Process).CurrentDirectory("/opt/irisapp") //On importe les default settings + le plugin GIT (SURTOUT LAISSER LES PASSAGES A LA LIGNE) zn "LIBRARY" zpm "install git-source-control" d ##class(SourceControl.Git.API).Configure() /irisdev/app/LIBRARY/ // Pour éviter de devoir modifier le mdp SuperUser. zn "%SYS" w ##class(Security.Users).UnExpireUserPasswords("*") // Pour faire fonctionner le plugin Git, il faut que le path défini existe, par défaut il est à chaine vide et cela fait planter le plugin. En l'enlevant cela fonctionne k ^SYS("SourceControl","Git","%gitBinPath") zn "LIBRARY" do ##class(SourceControl.Git.Utils).UserAction("","%SourceMenu,Init") halt Hi Matthieu, so you want to use Git for IRIS for an automated export of classes and set it up from the iris.script, which will be invoked in the Dockerfile. From the code you have pasted, it seems like you use a different Git Source Control implementation (zpm "install git-source-control“). The implementation discussed in this thread would be installed with zpm "install git-for-iris“ There, you can use the API functions in SourceControl.Git.Utils in the iris.script: do ##class(SourceControl.Git.Utils).AddDefaultSettings() do ##class(SourceControl.Git.Utils).AddPackageToSourceControl(„<My.Package.Name>“, „<MyNamespace>“) do ##class(SourceControl.Git.Utils).SetSourceControlStatus(1) A default package is added to source control via module.xml for demo purposes, as well as the /csp/user/sc web application for callbacks from git, both of which you may want to remove. As a final step, you will have to activate the source control class in IRIS. The manual process is described here https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=ASC#ASC_Hooks_activating_sc_class, you might look into the corresponding CSP page to find out how to do it programatically. Hope this helps. Currently there is a select few of us in the group that use Git and Local Repos for VS code, but I want to make this more wide spread for our team as most use the Editors off of the Management Portal to do their coding. Does anyone have steps they have used in the past to move towards Server Side Source Control from creating the Repos on your Server, getting the IRIS Code into the new Repo you created on your server, and pushing it to github? Git for IRIS has been updated to v0.3. It now provides source control for lookup tables and supports deletion of classes. Also, improvements were made to provision default settings, and Git hooks are now disabled by default to avoid unwanted side-effects (writing hooks to the .git directory, setting a random password for the technical user). A complete guide for deploying Git for IRIS to an existing IRIS instance has been added to README.md along with detailed descriptions of settings, Globals and behaviour.

Hey developers, We want to hear from you! Give us your feedback on the past InterSystems Developer Tools Contest! Please answer some questions to help us improve our contests. 👉 Quick survey: InterSystems Developer Tools Contest Survey Or just share your thoughts in the comments to this post!

Hey Community, We want to hear from you! Give us your feedback on the past InterSystems FHIR Accelerator Contest! Please answer some questions to help us improve our contests. 👉 Quick survey: InterSystems FHIR Accelerator Contest Survey Or just share your thoughts in the comments to this post! FHIR as service on public cloud is not available in China. Is it possible to deploy it in China? Thx! Michael

Hi Developers, Watch the execution of a speed test for a heavy-ingestion use case on InterSystems IRIS: ⏯ InterSystems IRIS Speed Test: High-Volume Ingestion Try the full demo at https://github.com/intersystems-community/irisdemo-demo-htap Speakers: 🗣 @Amir.Samary, InterSystems Director, Solution Architecture 🗣 @Derek.Robinson, InterSystems Senior Online Course Developer, InterSystems Subscribe to InterSystems Developers YouTube and stay tuned!

Three new sets of maintenance releases are now available: Caché 2018.1.5, Ensemble 2018.1.5, and HSAP 2018.1.5 InterSystems IRIS 2019.1.2, IRIS for Health 2019.1.2, and HealthShare Health Connect 2019.1.2 InterSystems IRIS 2020.1.1, IRIS for Health 2020.1.1, and HealthShare Health Connect 2020.1.1 Installation kits and containers can be downloaded from the WRC Software Distribution site. These are maintenance releases with many updates across a wide variety of areas. For information about the corrections in these releases, refer to the documentation for that version, which includes a Release Notes and Upgrade Checklist, and a Release Changes list, as well as the Class Reference and a full set of guides, references, tutorials, and articles. All documentation can be reached via docs.intersystems.com. New platform support has also been added to these releases. In particular, Ubuntu 20.04 LTS support has been added to all releases, IBM AIX 7.1 and 7.2 for System p-64 support has been added to 2019.1.2 (and was already in 2020.1), and ARM64 support for Linux was added to 2020.1.1. For details, see the Supported Platforms document for each release. Build numbers for these releases are shown in the table below: Version Product Build number 2018.1.5 Caché and Ensemble 2018.1.5.659.0 2018.1.5 Caché Evaluation 2018.1.5.659.0su 2018.1.5 HealthShare Health Connect (HSAP) 2018.1.5HS.9056.0 2019.1.2 InterSystems IRIS 2019.1.2.718.0 2019.1.2 IRIS for Health 2019.1.2.718.0 2019.1.2 HealthShare Health Connect 2019.1.2.718.0 2020.1.1 InterSystems IRIS 2020.1.1.408.0 2020.1.1 IRIS for Health 2020.1.1.408.0 2020.1.1 HealthShare Health Connect 2020.1.1.408.0 2020.1.1 InterSystems IRIS Community 2020.1.1.408.0 2020.1.1 IRIS for Health Community 2020.1.1.408.0 2020.1.1 IRIS Studio 2020.1.1.408.0 Very exciting!! Congratulations to all involved in getting these out the door :)

Hi Developers, See how a FHIR implementation can be built in InterSystems IRIS for Health, leveraging both PEX and InterSystems Reports: ⏯ FHIR Implementation Patterns in InterSystems IRIS for Health 👉🏼 Subscribe to InterSystems Developers YouTube. Enjoy and stay tuned!

We released a new version of ZPM (Package Manager) New in ZPM 0.2.14 release: Publishing timeout Embedded vars usage in module parameters Package installation from Github repo Transaction support for install, load and publish. See the details below. New configuration setting - publish timeout zpm:USER>config set PublishTimeout 120Use this setting if you are unable to publish the package due to a bad connection or other problems Support embedded vars in Default values in Module.xml <Default Name="MyDir" Value="${mgrdir}MySubDir"></Default> Thanks to @Lorenzo.Scalese for the suggested changes Load packages from repo (git) zpm:USER>load https://github.com/intersystems-community/zpm-registrygit must be installed Transactions Now Load, Install, Publish commands are executed in a transaction, which allows you to be sure that no changes will remain in the system in case of problems during these operations Many bug fixes and improvements All Docker images https://github.com/intersystems-community/zpm/wiki/04.-Docker-Images are updated and include ZPM 0.2.14 To launch IRIS do: docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/iris-community:2020.4.0.524.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/iris-community:2020.3.0.221.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/iris-ml-community:2020.3.0.302.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/irishealth-community:2020.4.0.524.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/irishealth-community:2020.3.0.221.0-zpm Robert Thanks @Nikolay.Soloviev! How to use load "github repo" feature using docker container? It says there is no git inside. in DockerFile USER root## add gitRUN apt update && apt-get -y install git This works, thank you, Robert!

Hi Community, Enjoy watching the new video on InterSystems Developers YouTube: ⏯ InterSystems API Manager: Gummy Bear Factories InterSystems API Manager allows developers to manage multiple APIs and consumers. This demo environment uses InterSystems API Manager, or IAM, to monitor and control the HTTP-based API traffic coming from three different candy factories, leading to an endpoint in InterSystems IRIS data platform. Stay tuned! 👍🏼

Hi InterSystems Developers! Recently I've updated the FHIR dev template so that it now publishes an IPM package fhir-server that makes the setup of InterSystems FHIR server a trivial manual or automatic or programmatic procedure one command long. Please see below how you can benefit from it. TLDR USER>zpm "install fhir-server" All the details below. Setting up InterSystems FHIR Server without IPM Of course you can setup InterSystems FHIR server without using IPM package manager. Here are the options: 1. You can setup a cloud FHIR server and have a trial for several days by following these instructions. This will be an InterSystems FHIR server in AWS cloud. 2. You can setup InterSystems FHIR server a running InterSystems IRIS for Health following these steps. 3. And also you can git clone the repository of this template and run in a cloned directory: $ docker-compose up -d to have InterSystems FHIR server up and running on your laptop. What I suggest in the article is point 2 where you can skip all the manual steps and have the FHIR server up and running on a laptop IRIS either in docker or host OS. Setting up FHIR server with IPM DISCLAIMER!! The steps described below refer to a newly installed IRIS for Health instance or for usage with docker images. The package creates a new namespace and a new web application so it could possibly harm the setup you had set up before. IPM stands for InterSystems Package manager, previously known as ZPM. Make sure you have IPM-client installed. You can check this if you run in IRIS terminal zpm command and see the following: IRISAPP>zpm ============================================================================= || Welcome to the Package Manager Shell (ZPM). || || Enter q/quit to exit the shell. Enter ?/help to view available commands || ============================================================================= zpm:IRISAPP> You will need IRIS for Health for that of versions 2022.x and newer. How to run iris for health on your laptop? Running on a host-operation Download the latest IRIS for Health from InterSystems Evaluation site that fits your platform (Windows, Mac, Linux) and install it. Install ZPM. Here is a one-liner: USER>zn "%SYS" d ##class(Security.SSLConfigs).Create("z") s r=##class(%Net.HttpRequest).%New(),r.Server="pm.community.intersystems.com",r.SSLConfiguration="z" d r.Get("/packages/zpm/latest/installer"),$system.OBJ.LoadStream(r.HttpResponse.Data,"c") Running a docker version Call in your terminal to launch: docker run --rm --name iris4h -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community Then start terminal: docker exec -it iris4h iris session IRIS Installing FHIR Server Once having IRIS running either on host or just run in IRIS terminal: USER>zpm "install fhir-server" This will install FHIR server in FHIRSERVER namespace with parameters: Set appKey = "/fhir/r4" Set strategyClass = "HS.FHIRServer.Storage.Json.InteractionsStrategy" set metadataPackages = $lb("hl7.fhir.r4.core@4.0.1") Set metadataConfigKey = "HL7v40" FHIR REST API will be available at http://yourserver/fhir/r4. It will also add some synthetic data. How to understand that server is working? To test on host version: http://localhost:52773/fhir/r4/metadata To test on docker version: http://localhost:9092/fhir/r4/metadata Also zpm installs the simple UI which is available at: yourserver/fhirUI/FHIRAppDemo.html And you'll see something like this (with patient id=1 entered): How it works? In fact you can observe what is being installed with this ZPM module in the following module.xml scenario. As you can see it imports code, installs demo frontend application fhirUI, runs the post-install script, which calls the following method. The script in the method performs the FHIR server setup. Installing FHIR server programmatically You also can install it programmatically via the following command: set sc=$zpm("install fhir-server") Happy FHIR coding! Added a host setup and docker run examples

Hi Developers! Here're the technology bonuses for the InterSystems Women’s Health FHIR Contest 2022 that will give you extra points in the voting: Women’s Health Topic Women’s Health Dataset IRIS For Health FHIR or FHIR Cloud Server Usage Healthcare Interoperability Embedded Python usage Docker container usage ZPM Package Deployment Online Demo Code Quality pass Article on Developer Community The second article on Developer Community Video on YouTube First Time Contribution See the details below. Women’s Health Topic - 5 points Collect 5 bonus points if your application is helping with any Women’s Health problems solution. For example if your application can help pregnant patients discover trends in tracking pregnancy symptoms and/or build an integration to share symptoms and pregnancy journal notes with a partner application Women’s Health Dataset - 3 points Collect 3 bonus points if you submit a Women’s Health dataset into Open Exchange and use it in your application. Here are examples of datasets in Open Exchange: titanic, community posts, health datasets. Dataset should be a separate Open Exchange application. IRIS For Health or InterSystems FHIR Server Cloud Usage - 2 points Collect 2 bonus points if your solution uses FHIR server via IRIS for Health or InterSystems FHIR Server on AWS. Get IRIS For Health template with FHIR server running here. You can spin up your instance of FHIR server here. Healthcare Interoperability - 4 points Collect 4 bonus points if your application is healthcare interoperability solution that uses InterSystems Interoperability to transfer or/and transform healthcare data via messages or it uses healthcare formats data transformation. Here is an example of healthcare interoperability solution. Embedded Python - 3 points Use Embedded Python in your application and collect 3 extra points. You'll need at least InterSystems IRIS 2021.2 for it. Docker container usage - 2 points The application gets a 'Docker container' bonus if it uses InterSystems IRIS running in a docker container. Here is the simplest template to start from. ZPM Package deployment - 2 points You can collect the bonus if you build and publish the ZPM(ObjectScript Package Manager) package for your Full-Stack application so it could be deployed with: zpm "install your-multi-model-solution" command on IRIS with ZPM client installed. ZPM client. Documentation. Online Demo of your project - 2 pointsCollect 3 more bonus points if you provision your project to the cloud as an online demo. You can do it on your own or you can use this template - here is an Example. Here is the video on how to use it. Code quality pass with zero bugs - 1 point Include the code quality Github action for code static control and make it show 0 bugs for ObjectScript. Article on Developer Community - 2 points Post an article on Developer Community that describes the features of your project. Collect 2 points for each article. Translations to different languages work too. The Second article on Developer Community - 1 point You can collect one more bonus point for the second article or the translation regarding the application. The 3rd and more will not bring more points but the attention will all be yours. Video on YouTube - 3 points Make the Youtube video that demonstrates your product in action and collect 3 bonus points per each. Examples. First Time Contribution - 3 points Collect 3 bonus points if you participate in InterSystems Open Exchange contests for the first time! The list of bonuses is subject to change. Stay tuned! Good luck with the competition!

Hey Community, We are super excited to announce the winners of the InterSystems IRIS for Health Contest: FHIR for Women's Health! Thank you all for participating in our coding competition! Without further ado, the winners are... Experts Nomination 🥇 1st place and $5,000 go to the FemTech Reminder app by @KATSIARYNA.Shaustruk, @Maria.Gladkova, @Maria.Nesterenko 🥈 2nd place and $3,000 go to the Pregnancy Symptoms Tracker app by @José.Pereira, @Henrique.GonçalvesDias, @Henry.HamonPereira 🥉 3rd place and $1,500 go to the Contest-FHIR app by @Lucas.Enard2487 🏅 4th place and $750 go to the fhir-healthy-pregnancy app by @Edmara.Francisco 🏅 5th place and $500 go to the iris-fhir-app app by @Oliver.Wilms More winners: 🏅 $100 go to the Dia-Bro-App app by @Dzmitry.Rabotkin, Maria Muzychuk, Maxim Eliseykin 🏅 $100 go to the NeuraHeart app by @Grzegorz.Koperwas 🏅 $100 go to the FHIR Questionnaires app by @Yuri.Gomes 🏅 $100 go to the Beat Savior app by @Jan.Skála 🏅 $100 go to the ehh2022-diabro app by @Maksym.Shcherban 🏅 $100 go to the Dexcom Board app by @Daniel.Šulc, Matěj Žídek, Tomáš Dorda Community Nomination 🥇 1st place and $1,000 go to the Pregnancy Symptoms Tracker app by @José.Pereira, @Henrique.GonçalvesDias, @Henry.HamonPereira 🥈 2nd place and $750 go to the FemTech Reminder app by @KATSIARYNA.Shaustruk, @Maria.Gladkova, @Maria.Nesterenko 🥉 3rd place and $500 go to the fhir-healthy-pregnancy app by @Edmara.Francisco Our sincerest congratulations to all the participants and winners! Join the fun next time 😎 Congratulations everyone! Well done! Congratulations to the winners! Good Work Thank you all for this contest and for this opportunity! Congratulations everyone! Great contest with a lot of awesome new apps!

A new release of ZPM has been published 0.5.0 New in this release Added support for Python's requirements.txt file Using tokens for publishing packages Fixed various issues Python's requirements.txt Now, if your project uses Python embedded and requires some Python's dependencies, you can add requirements.txt file to the project, as usual for any Python project, file have to be in the root of a project next to module.xml. And with load command or install command, ZPM will install dependencies from that file with using pip. USER>zpm "install python-faker" [USER|python-faker] Reload START (/usr/irissys/mgr/.modules/USER/python-faker/0.0.2/) [USER|python-faker] requirements.txt START [USER|python-faker] requirements.txt SUCCESS [USER|python-faker] Reload SUCCESS [python-faker] Module object refreshed. [USER|python-faker] Validate START [USER|python-faker] Validate SUCCESS [USER|python-faker] Compile START [USER|python-faker] Compile SUCCESS [USER|python-faker] Activate START [USER|python-faker] Configure START [USER|python-faker] Configure SUCCESS [USER|python-faker] Activate SUCCESS Great feature, @Dmitry.Maslennikov ! Thank you! [USER|python-faker] Reload START (/usr/irissys/mgr/.modules/USER/python-faker/0.0.2/) [USER|python-faker] requirements.txt START [USER|python-faker] requirements.txt SUCCESS Is it possible with -v tag to see what packages were installed? Yeah, sure, -v will show the actual output from pip

I just wrote up a quick sample to help a colleague load data into IRIS from R using RJDBC, and figured it's worth sharing here for future reference. Ultimately it was pretty simple, aside from IRIS not liking "." in column names; the workaround is to just rename the columns. Someone better at R than me could probably provide some generic approach. # Need a valid value for JAVA_HOME prior to calling library(RJDBC) Sys.setenv(JAVA_HOME="C:\\Java\\jdk-8.0.322.6-hotspot\\jre") library(RJDBC) library(dplyr) # Connect to IRIS – needs path to InterSystems JDBC JAR in your installation drv <- JDBC("com.intersystems.jdbc.IRISDriver", "C:\\InterSystems\\IRIS\\dev\\java\\lib\\1.8\\intersystems-jdbc-3.3.0.jar","\"") conn <- dbConnect(drv, "jdbc:IRIS://localhost:1972/USER", "IRIS Username", "IRIS Password") dbListTables(conn) # For maximum confusion, load the iris dataset :) data(iris) # IRIS doesn't like "." in column names, so rename. (Probably could code this generically but I’m not that good at R.) iris <- iris %>% rename(sepal_length = Sepal.Length, sepal_width = Sepal.Width, petal_length = Petal.Length, petal_width = Petal.Width) # dbWriteTable/dbGetQuery/dbReadTable just work dbWriteTable(conn, "iris", iris, overwrite = TRUE) dbGetQuery(conn, "select count(*) from iris") d <- dbReadTable(conn, "iris") bravo Tim!! A generic way to rename the columns would be as follows (I believe with this you no longer need to load the dplyr package): names(iris) <- gsub("\\.", "_", names(iris))