go to post Evgeny Shvarov · Jan 23, 2024 I replaced $$$Lower() but still getting <SYNTAX> Here is the alias in the file: :alias enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$zcvt($namespace,"L")) And here is SYNTAX i'm getting: IRISAPP>:enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$zcvt($namespace,"L") DO EnableDeepSee^%SYS.cspServer("/csp/"_$ZCVT($NAMESPACE,"L") ^ <SYNTAX> Here is what I have in the alias: IRISAPP>:enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$zcvt($namespace,"L") DO EnableDeepSee^%SYS.cspServer("/csp/"_$ZCVT($NAMESPACE,"L") ^ <SYNTAX> IRISAPP>:alias enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$zcvt($namespace,"L") IRISAPP> Interesting, if I set the alias in terminal as @Robert Cemper did it works. Perhaps the issue is in line endings? Any ideas?
go to post Evgeny Shvarov · Jan 23, 2024 @Robert Cemper, @Brett Saviano, thank you! Indeed, this is the thing! But even without macro it is a very powerful feature!
go to post Evgeny Shvarov · Jan 23, 2024 In fact I'm having a weird issue in docker: it looks like terminal doesn't read the last symbol from alias string. e.g. if I have the following alias (one liner to turn on IRISBI in a current namespace): :alias enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$$$LOWER($namespace)) It results with following: IRISAPP>:enablebi do EnableDeepSee^%SYS.cspServer("/csp/"_$$$LOWER($namespace) DO EnableDeepSee^%SYS.cspServer("/csp/"_$$$LOWER($namespace) ^ <SYNTAX> IRISAPP> Any thoughts @Robert Cemper @Dan Pasco ?
go to post Evgeny Shvarov · Jan 22, 2024 Community docker images with IPM on board are also available with 2024.1 preview. The tags are: intersystemsdc/iris-community:preview intersystemsdc/irishealth-community:preview
go to post Evgeny Shvarov · Jan 20, 2024 Hi @Dan Pasco ! Thanks for sharing! How did you make ":pp" terminal alias?
go to post Evgeny Shvarov · Jan 18, 2024 Turned out I created SSLConfig.properties file in wrong place. I put it in a proper place (as adviced in the article) and all started working. BTW, in the latest DBeaver version 23.3.2, the issue with cumbersome Database/Schema is not an issue anymore - Database/Schema can be just USER.
go to post Evgeny Shvarov · Jan 18, 2024 Amazing, @Chris Stewart ! Thanks a lot! And for Open Exchange too, please!
go to post Evgeny Shvarov · Jan 17, 2024 I'm getting this error while trying to connect to IRIS Cloud SQL instance to 443 port: All the requirements listed in the article are satisfied. This is M2 Macbook. Any advice?
go to post Evgeny Shvarov · Jan 17, 2024 Oh, that'd be amazing! Just've tried it - doesn't work for me:
go to post Evgeny Shvarov · Jan 17, 2024 Hi @Momeena Ali ! Yes, you can, for sure! Don't forget to publish your application on Open Exchange in a form of GitHub or Gitlab repository as an open source.
go to post Evgeny Shvarov · Jan 17, 2024 Great staff, @Chris Stewart ! Could you please share the related GitHub repo?
go to post Evgeny Shvarov · Jan 17, 2024 Hi @David hay ! Thanks for sharing the info on such a profound tool for FHIR developers! BTW, is there any local version of ClinFHIR that can be installed on a laptop? E.g. if I have the FHIR server locally for development purposes to be able to vusualise the data in local FHIR repository?
go to post Evgeny Shvarov · Jan 17, 2024 Hi @Guillaume Rongier ! Please consider the PR to make it an IPM module?
go to post Evgeny Shvarov · Jan 16, 2024 If I'm not mistaken, iFind is a part of 'Basic' text search which and according to documentation it is not deprecated
go to post Evgeny Shvarov · Jan 16, 2024 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.