Starting a FHIR repository project with IRIS for Health, what are the pros and cons to use R5 instead of R4 ? What is the effort to migrate from R4 to R5 the FHIR repo ? What are the risks or disadvantages to use R5 ?
I'm facing an issue while converting an ORU_R01 HL7 message to XML, specifically with the <pidgrpgrp> kind elements. When I use the getvalueat() method before conversion, the XML includes the <pidgrpgrp> and other <grp> elements, but when I don't use the getvalueat() method, the XML is generated without these <grp>elements.
I am working on a Zen page that has a table pane with the maxRows set to a default value. My customer is coming back with the following request of making that value bigger & begs the question whether the new value can be configurable. I looked @ the documentation, and forgive me if I missed, and I couldn't find anywhere that it can. Am I wrong? Thanks.
I'm trying to send alerts in Ens.Alert process to a teams channel.
I have already created a production that transforms the incoming alerts and send to a set of user's email but I also wanted to sent it to the teams channel
I have a situation where I am writing to global from different processes - let's call it an Event Queue. There is then a different process that uses $order to read through the data - the PubSub processing BP.
Sometimes the writing of this global will form part of a transaction that also insert data into other tables, using tstart and tcommit. If there is some issue, it will roll back, and the entry written to the global will also roll back.
A report that I need to create - I need to write a class method that will execute a few queries and save the data to a class and then return the data in a result set that can be used in the Logi report as a Stored procedure.
I can create the class method that is a Stored procedure and do the queries and manipulate the data, however I am having an issue at the end of the method to return the fields back as a result set.
I've upgraded from Ensemble 2014 to 2018 and copied all classes across, ran Upgrade & CompileAll and looks fine, but when trying to search on dataCombo I get the below error
After running many tests to kick the tires calling Python from COS (which worked fine) in any directory, I encountered problems when trying to access Python libraries like Numpy from any OTHER namespace. I saw some other posts about this but the resolution seems unclear. When I run the test program method numpytest below in %SYS it works just fine. If i run the Python method in any other namespace I get:
PITT>do ##class(test.python).numpytest() DO ##CLASS(test.python).numpytest() ^ <OBJECT DISPATCH> *python object not found
I know that you can use Do $SYSTEM.SQL.Schema.ImportDDL() to insert sql files into IRIS however I was wondering if there is a way that I can upload .sqlite files into iris? I have about 20 .sqlite files that I need to get into my database. I tried using the ImportDDL method but it said "SKIPPING non-SQL SOURCE:"
Attempting to setup an outbound (I'm querying out, not querying the IRIS db) SQL connection. I am connecting to a PostgreSQL database, name "hl7interface".
I have setup the odbc.ini file at /usr/local/etc with the following contents:
Last year we introduced our new angular-based View page for CCR as part of the UI refresh for the application. This has been used very effectively by close to 1000 users around the world as the default UI for viewing CCR, and as a result we're getting ready to completely disable the "classic" View page.
Hello everyone, I would like to not rely on %SYS.Journal.Record class is used to implement the function of reading and parsing logs. I want to use Python to read and parse journal log files, and implement %SYS.Journal.Record class functionality.
A partner have decided to change the algorithms that were used to connect on it's SFTP, but our version of libssh2 don't match with the list of it's HOSTKEYS algorithms.
If i update the library with the last version without to be sure that it includes the old algorithms, i risk to break the connection for other cases.