[Mike Shoemaker]

Thanks Max. I will revisit the details once the dust settles. I just got off the phone with Goutham and he was pretty helpful as usual. For my current situation, I am simply going to remove the standby node from the cluster and just run the single vm with cloverleaf during the network swap tonight. It’s basically just stopping the cman/rgman services on the inactive node. Go figure.

[Mike Shoemaker]

When you say ‘snapshot’ are you talking about the VMWare software snapshot? The problem I’m having is that I can’t take a snapshot, regardless of LVM, VMWare does not allow snaps or clones of active VMs due to the Shared disk mode the cluster uses.

[Mike Shoemaker]

I was supported with an issue related to a security limit at the OS level for the max number of processes allowed to run.  Redhat version was not an issue, although I found the solution to the problem via Google before Support did 😉   I was assured at install that the OS version would not be a problem with regard to Support.

[Mike Shoemaker]

Hi. I’m running HA Cloverleaf 5.8 on RHEL 6.2 64bit without any problems so far.  I’m not in production but I am mirroring my production environment for testing purposes and so far it runs like a dream.

[Mike Shoemaker]

Unfortunately, in this case, they are sending 2.3 but sprinkling in a little 2.6 just for fun. They have since fixed the situation.

MSH|^~&|Siemens_EDM|1AZ0|||201206140243||ORU^R01|TX20120614024322000|P|2.3|||AL|NE|USA

[Mike Shoemaker]

Sales at Lawson is looking to show us how wonderful this add-on is, which I’d love to see. Our biggest problem right now with regard to joining an HIE would be which one to join and how to pay for it 😉

[Mike Shoemaker]

The simplest thing for you to do as far as debug is to turn up the EO Output to enable all, that will give you the PDL details you are looking for.

[Mike Shoemaker]

Hey Ryan, I have a similar interface from Seimens EDM and we also encountered the same problem when initially starting the interface. Seimens was sending me logs from their side that the connection was being refused by Cloverleaf (or as they continually call it … Openlink) and in the end, I realized they were attempting to send a binary pdf through the connection. We had originally purchased an textual HL7 interface from them and they had some configuration mishap on their side that caused the interface to send PDF instead of HL7. Once they tweaked their side, messages have been flowing happily ever since.  Perhaps Seimens likes to be consistent with their configurations, regardless of how well they work. Hope this helps.

Thanks!

Mike

[Mike Shoemaker]

64 “glorious” bits!

[Mike Shoemaker]

I hope it’s still supported 😉 They assured me it didn’t matter and I have the emails to prove it.  The only reason I went down that road was to avoid any additional upgrades to the OS in the near future.  Our change management here requires a pretty hefty validation. I can’t put the depts. through any more testing after this is complete or they’ll turn on me.  We purchased the high availability scripts and as part of that, they (Goutham) came out on-site and stepped through the whole setup with me.  Install/config of the OS and install/migration to 5.8. I have a Redhat subscription for the OS and Cloverleaf is supported outside of that. So far it runs like a dream.

[Mike Shoemaker]

Hey Chris, I’m still in migration mode, but I just installed Cloverleaf 5.8 in a VM environment running Red Hat Enterprise Linux Server release 6.2 (Santiago).  We had some minor issues getting the clustering setup as they changed the gui settings a bit, but aside from that everything is running smoothly during my testing.  I wanted to be at the latest OS level I could possibly have in a stable environment to avoid OS upgrades in the near future.

Mike

[Mike Shoemaker]

That’s exactly what they are doing. And they just informed me, they can not remove the “Siemens EDM^text/plain^TXT^^Patient Name: Not specified” from the OBX-5 but they offered to try to use Openlink as an intermediary step. I guess Openlink is much more Robust at misinterpreting HL7.

[Mike Shoemaker]

This isn’t a huge ordeal for me, I can map my way around this, but I’m basically just looking for clarification and Jim certainly pointed me in the right direction. The ED data type makes perfect sense looking at the spec but not by looking at the message.  I never considered anything aside from the FT data type because I wasn’t expecting any sort of encoded data, only text. And why would I when OBX:2 says otherwise? They keep talking about their “style-sheets” so part of me thinks they have some sort of template style-sheet with a hard-coded OBX segment.  On a side note, with regard to the encoding characters in the MSH, I always assumed they do a similar thing with their encoding characters in the MSH … they never respect the escaping because they never respect the idea behind stating the encoding characters in the MSH, they just present them in the field as hard coded value and move along (not the first vendor to that either) But I think I won this battle. I have them working on providing the OBX-5 value as text along with the appropriate type in OBX:2…I hope.

[Mike Shoemaker]

Hey Jim,

Yup, the FT data does not specify multiple components, I’ve been staring at it for the past week trying to figure out how it could be misinterpreted (or shall I say, robustly interpreted?) But I was very short-sighted and never thought about peeking at the other data types, in my defense, when they say data type FT, why would I look for data type ED 🙂 As you explained below, that appears to be what they are doing. I’m sure once I point this out, they’ll change OBX-2 to ED and tell me to use Openlink to make it work. I’ll probably end up with some sort of scrub of the data on the Inbound and thank them for being so thoughtful in their interpretations 😉 As usual, I appreciate your insights 😉

Thanks,

Mike

[Mike Shoemaker]

It seems like you are saving messages via smat for trouble shooting? I’m not sure thats the intended purpose. Smat is an archive of messages. Sure you can save both inbound and outbound and plainly see where you are missing messages, but thats kind of only part of the picture. My troubleshooting always begins with the question “What happened with Patient XYZ?” Or “What happened to lab result from this patient on this date?” So to deal with those issues, I’ve always used smat as a way to reproduce the questioned message (or messages), a source message that hasn’t been translated or filtered, and then use Cloverleaf’s testing tool to see whats happening.  I never save outbound messages because its redundant if you have the source. You can always resend the source message or run it through the route tester tool or translation tester to see what’s happening with that particular message. Also, as it stands now for me, those smat files become too big to deal with if I don’t cycle save routinely. I chose to do so every hour and then time-date stamp the files and store outside of the /hci filesystem. Also, each individual “interface” has it’s own threads and saves in different Smat files, so I never get to see “the big picture” without lots of work pooling all the messages. The other problem I have is dealing with a patient that spans several hours or even days. Pulling those files make my stomach churn sometimes 😉 So with my little utility, I can basically see all the messages in a 1 stop-shop time lapsed feed so to speak.  Think of it like a patient profile in facebook format for Smat 😉  On a side note, how often are you “losing” messages in the engine? 95% of my job is pointing a finger at one of the ancillary apps and of course vendor complaints 😉

[Author]

Replies