@david-caragay
Forum Replies Created
-
AuthorReplies
-
We are planning on implemening 4.3 over the next few months. We’ll be working with outside vendors and physician practices. Was wondering if you had any issues working with private practices? Did these practices usually have an on-site IT person? Was there any issues with installing the client on their workstations/servers? Were you recommending dedicated client HW or did they install it on systems that also ran other multiple applications? Any thoughts would be great. Take care.
Hi Scott, We recently purchased a few licenses which we plan to deploy in the next few months. Was hoping you may have some experience with actual prod use. Any lessons learned you might be able to share?
Russ, Sorry about the late reply on your question.
As Jim has stated, there are concerns that need to be managed while implementing the GRV3 format. That being said, all of our new ADT interfaces from Invision to any foreign system are developed utilizing the GRV3 format. Any current interface that uses the Siemens superrecord format will probably be replaced with the GRV3 format over the next year or two. Not sure when Siemens will discontinue support for the superrecord but we have found the advantages to outweigh the disadvantages. Issues as presented by Jim are being managed via user process or custom coding in our interfaces.
If you need more information, let me know. We’ve been using the GRV3 format for many years. Take care.
We had the same problem with our fail-over shutdown scripts, running way too long. We are now running them in parallel and it has made a big difference. No problems. Vaiju, For a more accurate test of the alert, you might consider changing a tclproc or xlate to force an error on the message.
Hi James, How was the file you are attempting to resend created? Is it a saved message file or was it saved via the resend function in SMAT? SMAT will only open up valid saved message files (consisting of an idx and msg file) . If the file was created using the Smat resend function, the file format is len encoded not new line.
You also need to know if the messages you are attempting to resend were previously processed by your pre-tps outbound proc. If so, normally you would not want to run them through again.
Rickl, I’m also looking for info on the Global Monitoring version release. A list of revisions and enhancements for GM would be great.
Try this.. It will cycle process log, smat files and compress the .old files. Let me know how it works out. setroot
setsite [site_name_here]
echo
echo site is:$HCISITE
echo
hcicmd -p [process_name_here] -c ‘. output_cycle’
hcicmd -p [process_name_here] -c ‘[smat_file_name_here] save_cycle in’
hcicmd -p [process_name_here] -c ‘[smat_file_name_here] save_cycle out’
find $HCISITEDIR/exec/processes -name *.old.idx -exec compress -f {} ;
find $HCISITEDIR/exec/processes -name *.old.msg -exec compress -f {} ;
We have had our servers fail over a few times. Our biggest issue is with the SNA connections we have between our mainframe and our unix cloverleaf servers. All other interfaces fail over nicely. We’re still working to make the SNA fail-over happen smoothly. Right now we just start the SNA connections up manually. Rich,
If the “outbound only” checkbox is checked, Cloverleaf will still expect to receive a reply if you have set up the thread to do so. By setting up for replies, your outbound thread will set an “awaiting reply” switch each time it sends a message out. This tells Cloverleaf to expect a reply. “outbound only” will ignore any unexpected inbound messages that arrive when the “awaiting reply” switch is not set.
You would not check this box if you are using your outbound thread to receive “data” messages from the foreign system. An example would be a request for an lab order number. A system could be set up to respond back to the outbound thread with this lab order number. This is not very common since most interfaces will use a different pair of threads to communicate data back to the source system.
If you are having problems with losing replies from the destination system, you may also want to temporarily turn off this check box so you can track replies that may have been received after the reply timeout period. After the timeout is met, the “awaiting reply” flag is turned off and the “outbound only” option would end up throwing away your late arriving replies.
Daniel, Since a “no match” error does not give much debugging info in the log, Rob Abbott created a revised mlp pdl that might help identify the problem. Check out this link:
Arslan, Although we did not interface from Meditech, we did interface from Lastword to Cbord. The biggest issue we encountered was the handling of future orders and room service/no room service data. If you are running room service in your hospital, ask Cbord many questions on how that will work in their system. Almost 2 years since we implemented the Lastword to Cbord interface, we are still using a work around that we put in place as a temporary measure. Not very pretty but it works.
If you would like more information on this issue, send me an email with your phone number. We have been working very closely with CBORD for two years to resolve this problem and we think we are real close to a solution.
Hi Jim, 1) Do you use cron jobs to cycle / save or prefer to cycle manually? Why?
We run a nightly cron job to cycle all our saved message files. Much easier since we probably have around 200+ saved message files spread out over 30 different sites.2) If you use cron, do you find it best to cycle by file size, time of day, number of messages, or something else?
We cycle at every midnight. Some threads may not produce a significant volume over a 24 hour period but it’s much easier to manage the .old files since they cycle all at the same time.3) What is considered an optimum number of messages to manage in a SMAT file?
If you use the old SMAT GUIs, they will handle large saved message files much better than the newer SMAT GUIs. The old version of SMAT was written in TK/TCL unlike the newer JAVA Version. If you cycle each day, you should have no problem managing the files using the TK/TCL version.4) Do you archive SMAT files? For how long?
Depending on the saved message file, we may choose to keep only one cycle save before overwriting or we may choose to compress and save up to 10 days worth. This is all done in the scripts we run each night.Hope this helps.
Nathan, Looks like that rawhl7ack.tcl has been around for quite a few years. Interesting way to avoid creating an ack. We don’t include this code fragment in our tcl ack procs but maybe we’ll consider it in the future. Thanks for the infomation.
Nathan, If the code you posted is from your actual inbound tps ack proc that would explain why changing the priority would cause the ack not to be sent. Is this an inhouse developed tps ack proc? If it is a delivered proc, what is the name? This logic is not included in our ack procs (custom) so I’m guessing it was introduced some time ago in a delivered Quovadx ack proc. If this is the case, changing priority may or may not skip ack processing, depending on how the ack procs are written.
-
AuthorReplies
