Forum Replies Created
-
AuthorReplies
-
FYI, we purchased HL7Spy and asked the vendor about the password issue. After providing some sample SMATDB files from our TST environment he was able to figure out that it was an issue with SQLite v4 files. He said it worked correctly with v3, and was able to make a 5 minute change for it to work with v4. He sent us a new build as v24.1.690 that had the correction and it works perfectly.
I would highly recommend this tool for anyone working with Cloverleaf, as it saves us hours parsing through data to find what we are looking for. It is better than Cloverleaf and Epic Bridges combined when it comes to dealing with large volumes of data.
Thanks for the quick answer! I’m testing out HL7 Spy and I’m wondering if there is a way to not have to enter the site password for every single file? We archive our SMATDB files daily so I would like to open a week or a month of data, but it gets old entering the password for every single file. It would be nice if it tried the first password entered for the rest of the files and prompted you when it doesn’t work.
I love the tool so far. This will save us so much time in data searches!
I am also interested in using HL7 Spy, but how do you know the password for the SMATDB encryption if you are letting the system create it? I know if revolves around the Site Name, but it can’t be that simple.
Also check your alerts configuration for all sites. There may be a rule checking for that service to be up and restarting through command line.
I looked at the release notes for the latest versions, but I cannot find anything to tell me if 2022.09.x will run on a Redhat 9 server. This OS has been out for two years and my IT Engineers want me to use this version if possible during my upgrade this year.
Has anyone tested this version with Redhat 9? Are there plans to officially certify it?
Thank you for the ideas! I am actually using a combination of them by using HCISMATDB to write out a good sampling of Inbound Data to a file, and then running it through both Test environments and using WinMerge to compare the output. This way I don’t need to change or turn on the Outbound Threads and I still get a full comparison of every route involved.
I ran a sample this morning for ADT’s and it works exactly as expected. Now I just have to get started…
I was able to resolve my issue by commenting out the following three lines in .profile:
if [ -s “$MAIL” ] # This is at Shell startup. In normal
then echo “$MAILMSG” # operation, the Shell checks
fi # periodically.
They were causing feedback to the login process which stopped any SSH processes from working.
-
AuthorReplies