[Peter Heggie]

To start Cloverleaf, start the lock manager and monitor first, then start the processes. I think it is desirable to have the lock manager running before messages are processed through threads.

it is interesting that our HACMP environment, configured by Infor, has a shell script that determines all the processes in a site and does a kill -9 on the PIDs, then a kill -9 on the lock manager and the monitor. And does that for all sites. Then kills the host server. So nine sites with a total of 400 threads will end in about eight seconds. Never lost a message, never had a problem. We use Recovery Databases for everything.

 

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

This is how we use LIKE – if that is what you are looking for?

 

select status from dbo.prl_charges WITH (NOLOCK) where keyvalue like ‘%’ + <keyvalue> + ‘%’

in_column_name=keyvalue
out_column_name=status

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

We had bad (character) actors.. but from one specific source. A doctor cut and pasted dictation/consult notes from Word into a text reader that sends them as an ORU into Cloverleaf. This included some strange formatting characters that did not convert to ASCII . We tried education, to no effect. We ended up creating a TCL proc that performed string maps. Every few weeks we added more string mapping From and To characters. That was almost two years ago and we still get that input but the TCL catches it and fixes it.

 

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

Can EPIC take in lab results in an older version of HL7? Our current lab vendor sends us results in v2.3. So not all data is discrete and not all meta-data is discrete. Does that mean documents like CCDAs, sent through Care Everywhere, could not be ingested in other EMRs, because some of the data is textual, not discrete?

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

This is great detail – thank you. Our current financials/ADT interface from our EMR is 2.7, so I think we are good there. But our clinical interfaces – orders, results – are 2.4, so we may have a lot of work to do with clinical interfaces.

Is a TS person an EPIC employee? I’m wondering where the line is, between what we would do and what they would do.

Right now, with Cerner/Oracle, we have Cloverleaf connecting to Openlink. We don’t do any programming in Openlink. On rare occasions, maybe five or six times in the last eight years, we have had Cerner make changes to Openlink. But 99.9% of the time, we do everything in Cloverleaf, when it comes to translation and transformation of interface data to and from ancillary systems. As far as doing everything in Cloverleaf, does that remain the same? And there is a potential for less interfaces if some of our modalities are part of the EPIC component set?

The ACK work sounds interesting; we only do the immediate, “message received” ACK for the most part, except for a state registry interface, which sends us application ACKs.

Peter

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

adding email

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

adding email

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

Hi Nancy,

Sorry to hijack this thread, but I couldn’t help notice that the above eligibility verification functionality is something that we are also looking at implementing. We looked at an Experian package called eCare Next Base Platform, and with it, Premium Eligibility Services. We also use HDX and the above package included costs for HDX configuration.

But what you are describing sounds more automated, and faster, than what we are looking at. I’m just wondering if this is actually a different service than the Experian eCare. It sounds like you have a direct tcp/ip connection. I assume you have a VPN?

And for anyone else (!), is there a similar service using web services or FHIR? The tcp/ip flavor seems easier?

Peter

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

#following

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

I am very interested in any responses to your question. We have been struggling with false positives on holidays and wanted a simple way to turn off or turn on sets of alerts that should not be running on a holiday.

We looked at using the AND alert type, to connect a “normal” alert and a holiday alert (which could be a TCL alert that would look at a calendar file and figure out if today was a holiday), but we would need to do this for every normal alert, so we could easily end up with double the number of existing alerts.

i was hoping for an additional function contained in each alert that allows me to callout to a TCL and get a 0 or 1 return code – this would be in additional to all the other attributes of an alert.

So…  you may have to create an alternate alert file that you would load via the command line, that has the right alerts for that holiday.

I think this is the syntax??
<p class=”- topic/p p”>Use this format to run a specific alert. In this example, the alert file is named foo.alert:</p>

<pre class=”+ topic/pre pr-d/codeblock pre codeblock”><code>hcisitectl -s a -A “<var class=”+ topic/keyword sw-d/varname keyword varname”>a</var>=-cl foo.alert”</code></pre>
We played with this once and could not get the command line command to work so hopefully you will figure it out.

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

We too are grateful for your support and your service to this Cloverleaf Community.

We only go back to 1998 when we used the SNA protocols to connect to the mainframe, to SMS, then Invision. I remember looking on Clovertech for answers and seeing your posts with looong TCL procs… 🙂

We will miss you on the strategy and new offering webinars as well!

Peter

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

I have not used the HL7 package and I’m notso great with namespaces, but maybe this line:

set hl7 [hl7::parse_msg [msgget $mh]]

it just makes me wonder if it is confusing that you are creating/updating a variable that has the same name as the namespace?

Maybe you use a different variable name:

set hl7msg [hl7::parse_msg [msgget $mh]]

and then change the lines that come after that to use the different variable name:

set MSH_3 [hl7::get_field hl7msg MSH.3]

 

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

I like that solution Jim!

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

I’ve never seen or heard of this. Do you have Use Recovery Database enabled?

Peter Heggie
PeterHeggie@crouse.org

[Peter Heggie]

I was unable to get that to work. I am on cis2022.09.01, on AIX 7.2

On the local site I restarted all processes and the two daemons, and I executed the Refresh Objects command. On the Primary site I ran mktclindex and also edited the TCL proc in the GUI to force the update of the .upocindex file. I ran Refresh Objects there also and I restarted both daemons. I’m still getting the error. I went back to the local site and ran mktclindex but that did not fix the problem.

tcl :out :INFO/0: to_email:11/09/2023 10:33:00] sourceFilter /hci/cis2022.09/integrator/soabattst/tclprocs/email_smtp_mime.tcl: Failed to source filtered file: couldn’t read file “/hci/cis2022.09/integrator/soabattst/tclprocs/email_smtp_mime.tcl”: no such file or directory
[sms :sms :ERR /0: to_email:11/09/2023 10:33:00] Tcl error:
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] msgId = message0
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] proc = ‘extracts_email_send’
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] args = ”
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] result = ”
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] errorInfo: ‘
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] invalid command name “email_smtp_mime”

Just to be clear, the above folder name: /hci/cis2022.09/integrator/soabattst is a link, and all the local sites are in a different file system, with links to them stored in the integrator folder. Our master site is in a sub-folder in the integrator folder (/hci/cis2022.09/integrator/clovertest/<site content>); our local sites are in a different file system (/test/cis2022.09/soabattst/<site content>). Does that make a difference?

 

Now that I have gone through all that and documented the error messages, it just started to work. The only thing I changed was to update the calling proc, in the local site. I don’t know why this made a difference. I looked in the .upocindex file and the tclindex file, in both the local site and Primary Site, and while these were updated at the same time, I don’t actually see the called proc, in the Primary Site, listed in the local site’s upocindex/tclindex files. But the update to the calling proc and the subsequent recycle of that one process which invokes the parent proc seems to have closed the loop. I did not see this activity documented anywhere as required. But nothing else changed.

Peter Heggie
PeterHeggie@crouse.org

[Author]

Replies