Forum Replies Created
-
AuthorReplies
-
Bump to the top for an update…
Yes, this is of strong interest to our organization as we are on Windows 7 with a very slow push to Windows 10. No date has been set for Windows 10.
Since we are on 6.0.2 using Windows 7, we can’t upgrade to 6.2 using our current PCs. So if no change is made, we would have to get creative with the budget for temporary PCs for our 10+ team members. That likely won’t go over too well.
Thank you for considering 6.2 on Windows 7. It would be a definite benefit and customer satisfier.
Nate
Sorry for the late reply to this, but good luck Jim. While I don’t post much, I do read often. Glad that you’ll still be around as your insight is appreciated.
Nate K
Sorry Robert, just saw this thread. Let me know if you have any questions on the results. We now have an ADT interface implemented too. For the most part, it is a pretty hands-off interface with one sticking point….someone having the patient’s chart locked in Epic and the incoming result cant’ file.. So we had our Epic TS create a process where failed results, due to locked charts, get resubmitted every 5 minutes for up to 3 times. Then the result goes to our error work queue. Nate
I use WinVi. It’s a simple, free application. I basically open the file in hex mode and search/replace all 0a’s with nothing. Then if you have multiple messages in the file, search/replace 0d 4d 53 48 with 0d 0a 4d 53 48 to insert the 0a between messages. Also make sure that the last message in the file ends with 0d 0a. Every segment ends with 0d so that is why it is easy to remove all 0a’s first, then put them back where needed. After you do it a few times, it gets to be a very quick and easy routine.
Good luck!
Nate
Thank you, James. That worked perfectly! I typically don’t have to replace hex characters, so I was stuck since I couldn’t use the typical n r values for newline and carriage return. Learn something new everyday!
Nate K
December 30, 2011 at 8:50 pm in reply to: Windows 7 certified Cloverleaf versions ~ need update please #75726Yes, I was just referencing the Client. I should’ve made that clear. We’ll keep the server on our AIX OS. I see that you mentioned version 5.8.5. Is that the earliest Client version that is certified or just one that you happened to check?
June 2, 2011 at 9:27 pm in reply to: Inbound thread with outbound thread in different process #74510I concur with James.
I also don’t think that you’ll have specific performance or “unexplainable” issues with separate processes. We tend to keep our inbound and outbound threads in the same process as it is easier to group related items when modifying, shutting down, or bouncing processes. With that said, we do have a few that the inbound is a different process versus the outbound and we haven’t experienced any issues….(we need a knock-on-wood emoticon).
This resolved my issue. I renamed the wpid (just in case), started the process and it has been working correctly every since.
Thanks again Michael!
Thanks Michael. I’ll give it a try.
Thank you, Jim. I appreciate your quick response. I had contemplated using that setting, but figured I would just get the modified HL7 messages flowing out of the thread.
Thank you for the replies and information.
Try a comma with no space.
Charlie Bursell wrote:Be very careful when making unique file names from date and/or time. The granularity of time is in seconds.
I’m sure this isn’t perfect as it was written in crunch-time during a go-live, but it works for me. It appends the current date to the file. Nate.
-
AuthorReplies