[Jim Beall]

Did you see it with all your outbounds or just some?  I still don’t understand why I don’t see it from all outbounds although there’s a possibility the ones I don’t see it happening on are all VPN connections (need to check that).

[Jim Beall]

Virtually nothing here as far as PM is concerned.  Daily SMAT file backups, monitoring scripts take care of notifying us if there’s anything in the error D/B or queue backups.  We don’t even cycle processes on a scheduled basis.  We’re on older software (5.6) and hardware (HP UX), but it’s extremely stable.  Will be tempting fate soon by migrating to 6.x and RHEL but I’m cautiously optimistic it’ll be stable too.

[Jim Beall]

We’re on 5.6.  It doesn’t go any higher than 2.5.  I’ve been looking at the 2.5.1 messaging standard doc and the lab results implementation guide, and there’s not a whole lot missing in Cloverleaf.  The ORU message structure is identical and the only thing I see is a a few fields added to the end of some of the clinical segments (OBX, ORU, etc.).

[Jim Beall]

FWIW I’ve been able to install the 5.6 IDE on Win 7 by installing it in Microsoft’s 32-bit virtual machine (the exact name escapes me and I can’t get to that machine at the moment).  The VM is a free download from MS.  I haven’t really run it much under the VM but what little I’ve done with it seems to work.

[Jim Beall]

One of the ways we’ve tested upgrades in the past is to send production inbound SMAT files through the test/upgrade inbound thread, and then doing a diff against the outbound SMAT files.  We’re planning on doing a 5.6 to 6.0 upgrade this summer.  Will that methodology still work if we use these utilities?

[Jim Beall]

I pinged one of the Cerner use groups about this and here’s the answer I got (it comes from a Cerner resource who I think moderates the group I posted to).  Her response was:

We will support the HL7 v2.5.1 ORU Result messages for lab and micro results and for immunization reporting.  We actually support HL7 v2.5.1 ORU messages for lab, micro and AP today as MU1 required HL7 v2.5.1 ORU.

However, you will need to turn on the new 2.5.1 triggers in SI Manager.  We won’t just start sending them.  We will continue to support our current HL7 v2.3 triggers.

[Jim Beall]

I don’t have an answer to your query but I do have a question.  Is this Cerner Millennium?  And is this upgrade to 2.5.1 part of their 2012 code level upgrade?

[Jim Beall]

Just check”Cloverleaf Integration”.  If you check both that and “Cloverleaf Health Information Exchange”, nothing returns.

[Jim Beall]

I just checked the Inforum web site and there are a number of Cloverleaf sessions posted: https://inforum2013.activeevents.com/connect/search.ww#loadSearch-searchPhrase=&searchENGINE=session&tc=0&sortBy=&p=&i(10082)=10294&i(10360)=

[Jim Beall]

We’re in the midst of implementing a new core HIS too and we opted for brand new sites.  No issues that I’m aware of with IPs and ports as long (obviously) as you’re not trying to connect to both at the same time.  We copied a few tclprocs for routine stuff like handling acks, etc. but by and large we started from scratch with variants, procs, etc.  One thing that did bite us was not having enough semaphores available when we started the new site.  There’s a post from me about that on Clovertech somewhere.

[Jim Beall]

Thanks Jim!

[Jim Beall]

I ended up going back to multiple OR’s.  The value OP returned true for the variable containing ED OPS OBV CLI QER which I didn’t want.  I assume it did that because it matched the first two letters in OPS – or maybe I implemented it incorrectly?  Still good to know though; this will come in handy in the future.  Thanks!

[Jim Beall]

I need to check PR1.18 and if it’s one of five values do the same thing.  If I understand this right, instead of doing a bunch of “ors” I could do this:

COPY

Source: =ED OPS OBV CLI QER

Destination: @temp_var

IF

@temp_var ct ~0(0).PV1(0).00148(0)

Just want to confirm because the syntax seems almost backwards to me.  Thanks

[Jim Beall]

We shut down another non-prod site and, sure enough, we were able to start up monitord and all the processes/threads on the new non-prod site.  We think we’ve figured out which kernel parm we need to increase as well.  Thanks to both of you for your help.

[Jim Beall]

I  hate to say this but I don’t remember.  I know I didn’t implement Gary’s suggestion but darned if I can recall what the outcome of this was.  I think we were trying to find a solution for it within Millennium and it kinda died on the vine.  Sorry…

[Author]

Replies