Forum Replies Created
-
AuthorReplies
-
You are da man sir !! Including my temp variable in the Source for the CONCAT worked like a charm.
September 14, 2018 at 5:18 pm in reply to: How to build an outbound thread for a database connection #81797Thanks for the feedback.
I ended up discovering that just running the test data through the threads populated the database on the other end…
So yes, if I would have run the test file through the XLT tester, write that to file, then pull that into the database tester then it probably would have worked as expected.
I’ll take the blame for not understanding the tester fully 😉
September 13, 2018 at 1:17 pm in reply to: How to build an outbound thread for a database connection #81795last attachment showing no value passed
September 13, 2018 at 1:06 pm in reply to: How to build an outbound thread for a database connection #81794I realize this is an older thread, but it looks relevant to my current issue..
Cloverleaf 6.1.1 running on Windows server
Trying to create an HL7 to database interface, the XLT I have setup seems to work as expected (I see the HL7 values in the related database field I defined in the XLT), when running the tester for Database Protocol I cannot get the Value in the “Executed SQL” statement. If I check “whole message” then I can get the entire message as a value…but that does me no good here..
Attaching a couple screenshots.
Thank you James !
I’ll be testing this out and becoming familiar with it.
Guess I’ll just keep fixing my own issues here…..
This one was because I did not use the correct sample site, I was using the Windows version and I had to use the AIX sample site tar file.
Once I un-tarred the AIX sample site and copied over the tclprocs, it loaded everything as it should.
Now I am having a problem actually decrypting the message on the final leg of the interface, but that is another battle.
June 20, 2017 at 1:10 pm in reply to: process panic with infor supplied csc_msg_route tclproc #85297In case anyone reads this for reference, the problem ended up being that I did not copy all of the ‘tclprocs’ files from the CSC installation into the Cloverleaf csc_server directory.
So Cloverleaf was balking at the missing tclprocs.
We have been on Epic now for a few years and to answer your question of how well do they work together, very well 😉
Epic Bridges certainly does not take the place of an interface engine, but it does complement Cloverleaf and even provides some nice features that are…..well have always been…. lacking in Cloverleaf, like a very nice user friendly way of viewing and editing the HL7 messages.
We also have several point-to-point interfaces, straight from Epic Bridges to the ancillary system…. typically these are Device interfaces (i.e. glucometers and such).
Epic’s interface support (their “EDI” group) is fantastic ! I can send an email directly to one person and get a response in minutes, or I can always pick up the phone and call their main support and they will route me to someone immeditately. I don’t have to go through the aggrevation of dealing with a new person each time and explaining who we are and what we have……
😀
Thanks again for your assistance, most helpful !
Roger that…. I think I’ll leave my workaround script in place for now, since I would have to move the SMAT history files around anyway.
It would be nice if the SMAT cycling could be done site-wide and if they symbolic link ‘trick’ worked as advertised.
Thanks for the help Max….
I saw the cycling radio button for Logs but not for SMAT files…. until your help!! I’m now a happy camper 😉
One more question… the Log cycle under the Site Options is for ALL processes in the site, correct ? Does the process Log cycle setting take precedence over the Site log cycle option ?
I have a ticket opened with all the information, thanks.
I have my workaround in place, I let CL create the SmatHistory directory under the process directory, then I create a symbolic link in the SmatHistory directory that points to my archive filesystem and I have a cron script job that cycles and moves all the files in SmatHistory.
It works…. but it would be nice if it worked as advertised, and it would be even nicer if they included a way to automate the cycling of SMAT files (like the logfiles).
Strange… it works for the logfiles, just not the SMAT files.
I just verified by cycling the logfiles, using a softlink for LogHistory.
The softlink SmatHistory points to the exact same location as LogHistory, but the cycle fails.
Seems like a “BUG” to me.
thanks for the suggestion… I just checked and hci has ownership and I used “777” to open up every directory at the destination.
No change..
With Jim’s help, I was able to build a Xlate that works perfectly for our interface.
-
AuthorReplies