go to post Tani Frankel · Jul 15, 2024 Can you share the contents of the HS.Util.Installer.HSSYS-0.log file (it should be under the mgr directory of the IRIS installation). For example if it includes a line such as: 2024-05-01 13:58:46.077 HS.HealthConnect.FHIRSQL.Upgrade.V2:InstallOnce-HSSYS-1 Configured FHIRSQL Application endpoints Similarly also in ensinstall.log, with a line like this: HS.HealthConnect.FHIRSQL.Upgrade.V2:InstallOnce-HSSYS-1 Configured FHIRSQL Application endpoints
go to post Tani Frankel · Jul 14, 2024 Hi Ashok, Sorry for the silly question, but just to double check - did you deploy IRIS or IRIS for Health?
go to post Tani Frankel · May 28, 2024 There is also the topic of Search Parameters (if defined in the profile). See from the Docs here and this related video - Working with FHIR Profiles in IRIS for Health (from Virtual Summit 2020).
go to post Tani Frankel · May 22, 2024 Thank you KariI guess with a custom approach, you could also utilize for example the Vault REST API and use that when you want to access these kinds of credentials.
go to post Tani Frankel · May 21, 2024 Hi @Kari Vatjus-Anttila I was wondering if since this question you ended up using Vault for this purpose somehow? or what other alternative you used?
go to post Tani Frankel · Apr 8, 2024 Thank you, so this is clearer, and it is happening much earlier than I was thinking. You are not trying to connect via xDBC to your FHIR SQL Builder projected tables, but rather just trying to create the first Analysis step. This error "shouldn't happen", and I recommend you turn to our Cloud Support. What you could attempt doing before, is opening the browser debugger and see (perhaps under Network and the related HTTP requests you see) if you see some "interesting" error that could shed some light on what is happening.
go to post Tani Frankel · Apr 8, 2024 Perhaps you can provide more details as to what you are trying to do exactly and the way the error manifests itself. For example you say "in cloud" do you mean via the FHIR Server cloud SaaS service?If so you have to enable External Connections and setup External Rules. See from the Docs here. Then under the overview page you should be able to see xDBC Details for connecting. See also here. There is an article by @Iryna Mykhailova about connecting via xDBC to the IRIS Cloud SQL service, which should be very similar/identical. Per the above a connection refused error might have to do with the TLS setup required for this connection (which the article above does not cover currently, but the service xDBC details in the Overview page does provide detailed instructions for).
go to post Tani Frankel · Mar 5, 2024 Hi Yehuda,To answer your first question you would probably either use TLS or Kerberos between the Web Gateway and IRIS. But more to the point, from your second question what you seem to be desiring to accomplish is not securing/encrypting the communication between the Web Server (Web Gateway) and IRIS, but rather between the client (the browser for example) and the Web Server. For this you would define your Web Server (either IIS, apache or nginx for example) to accept TLS-based (HTTPS) connections/traffic. This configuration is done on the Web Server side, not on the InterSystems IRIS, or InterSystems Web Gateway side. And you can consult the relevant Web Server documentation to do that. You will also need relevant certificate/s. For your convenience here are some sample relevant 3rd party documentation references - IIS: https://learn.microsoft.com/en-us/iis/manage/configuring-security/how-to... Apache: https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html Nginx: https://nginx.org/en/docs/http/configuring_https_servers.html If you use containers, Kubernetes and our Operator (IKO) all of this can be auto-configured by some simple definitions (see for example here). (Note if you still want to also secure/encrypt the Web Gateway to IRIS communication you can of course do that as well, per the Docs you already looked at)
go to post Tani Frankel · Mar 3, 2024 Just in case - I assume you know that nowadays, in VS Code, you have a very good and easy way to debug a REST Service, see the docs here.
go to post Tani Frankel · Mar 1, 2024 If you want to use the XML Virtual Documents, you need to import an xsd (schema definition). See docs, and see the "Import" button in your screen shot above. Note there are other ways to work with XML in the product, depending on your use case. See also these docs.
go to post Tani Frankel · Mar 1, 2024 Did you try accessing the terminal web app via port 52773, like your Mgmt. Portal? 52772 used to be the default port for the Private Web Server, but this could change per installation.
go to post Tani Frankel · Feb 22, 2024 Thanks @Ben Spead, note the link @Azezur Rahman provided above - https://download.intersystems.com/download/login.cspDoes not work (and is not redirected). Though as you mentioned the more basic - https://download.intersystems.com/ would redirect to the newer Evaluation page.It would be great if, as you suggested, the original article could be updated.
go to post Tani Frankel · Feb 20, 2024 These screenshots are useful! tx! Just updating the download link, nowadays this is: https://evaluation.intersystems.com/ (see also this post) And the download page for the Community Edition could look like this -
go to post Tani Frankel · Feb 13, 2024 Here's the recording of this session - https://www.youtube.com/embed/uT5sqSwtF0k?si=AiFyEe46jahRm7SH[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
go to post Tani Frankel · Jan 28, 2024 I recommend participants who are not currently using VS Code yet, at least review our previous Webinar on the topic.
go to post Tani Frankel · Jan 27, 2024 Theo, as you see it is described as "beta" therefore it is not currently publicly documented. Internally you can see IF-1930. It states: "This should only be used with guidance from InterSystems Support."
go to post Tani Frankel · Jan 10, 2024 See also this post https://community.intersystems.com/node/548491 by @Guillaume Rongier
go to post Tani Frankel · Dec 24, 2023 I believe you have stumbled across a known issue - that if you call the method you mentioned above HS.FHIRServer.Installer:InstallNamespace() in a container, more than once, the FHIR Config UI app breaks (due to the folder location you mentioned above). This was fixed since version 2023.2 (I see you are using 2023.1). If you want to upgrade to 2023.2/3 you will have the fix. (just note the differences between CD (Continuous Delivery) releases and EM (Extended Maintenance) ones (like 2023.2/3); see this article for more details). If you can't upgrade now I suggest you turn to your local InterSystems account team (@Anssi Kauppi / @Janne Korhonen) and/or InterSystems WRC (you can reference the internal fix IF-4531).
go to post Tani Frankel · Dec 14, 2023 Maybe using the Portal built-in "Test LDAP Authentication" can help. See Docs.
go to post Tani Frankel · Nov 23, 2023 Hi Yakov, You can see from the Docs here, for example re the Property ConnectAttrs (or later ConnectionAttributes): ConnectAttrs ... An optional set of SQL connection attribute options. For ODBC, they have the form: attr:val,attr:val For example, AutoCommit:1. ... Set this property in the OnInit() method of your business operation or business service to specify the options to use at connection time. For calling SetConnectAttr() see these Docs, for example: If the connection has already been established, call the SetConnectAttr() method of the adapter. This method takes two arguments (the attribute name and the desired value) and returns a status. For example: Set tout= ..Adapter.SetConnectAttr("querytimeout",10) As to the name of the attribute and the appropriate value you should consult the SQL Server documentation (for example this, but this will be up to you to verify). If you need more assistance than this please get in touch and we can work on this together.
