[Matthew Brophy]

desired output for EMR for historical imports…

rather than repeat a VRL, planning to iterate over the HL7 and return the multiple values in a concatenated output

[Matthew Brophy]

In addition to using OpenJDK as the alternative, is there any plans to be compatible with Amazon Corretto or Zulu?

[Matthew Brophy]

jonathan – what did you come up with on this multiple lines/single message solution?

I assume this was for a Cerner export, correct?

[Matthew Brophy]

fwiw – we ran into this issue a few years ago (cis6.1.2) with large documents ending up crashing the site the processes our mdms.

The killer is loading the messages into recovery db (x2), processing the messages while also smatting.  What we ended up doing was setting a GUI alert to shut down the incoming threads that feed our document repository (OnBase) if the outbound queue is greater than 200 msgs.  This RARELY happens, but its a life saver because the alternative is crashing the site and potentially losing thousands of message if they aren’t saved off appropriately.

 

We have a two dozen receive threads that feed this OnBase connection so if a system started flooding us with MDMs/PDFs we could prevent a system crash

[Matthew Brophy]

the best part of Clovertech (or any knowledgebase) would be community.  The more you participate, regardless of how basic the question would be, the more you will get out of it. I know it would be intimidating to ask a question on “how do I get X to do Y on this ADT msg?” when you see all these other questions about APIs and FHIR going on (which are great).

Timeliness of responses would be another thing I could see people not bothering to participate.  Though, i’ve never had a question ever go unanswered for more than a day and never been left wanting…..so the resource is here, it just may not seem like it.

[Matthew Brophy]

We’ve gone with the recommended standard of no more than 10 processes / site.  No more than 10 threads / process.

 

In our newer environment (starting clean), we have kept threads under 50 / site.

[Matthew Brophy]

if it helps, we ran into this issue a while back, as well

https://usspvlclovertch2.infor.com/forums/topic/hl7-file-w-no-terminators/

attached pic is the inbound protocol

 

Attachments:

You must be logged in to view attached files.

[Matthew Brophy]

is your protocol inbound style set to ‘eof’ or ‘hl7’?

does your hl7.csv file have message terminators included before the start of each message?

[Matthew Brophy]

This is a practice we avoid whenever possible, not because of message volume, but just for better management of traffic.  If you have intra sites A,B,C, and D feeding a receiving connection on site X, it can be a rats nest sorting out issues with the receiving connection on site X (tracking the issue back to the source site).  Performance? no issues.

[Matthew Brophy]

within the xlate, we used a conditional IF statement to determine if a notification would be sent.

system echo “Please remove the LaPOST document for $MRN $DOB” | exec mailx -s “CLOVERLEAF_EMAIL<encrypt>”

 

this is intended to be sent only within our secure domain Exchange server.

[Matthew Brophy]

thank you, Vince. Thats exactly what we were looking for (“exec mailx”) .

I’ll share what we’ve built out once completed.

[Matthew Brophy]

1. On your process log, how much is it logging? More than transaction events? If so, check to make sure the thread Engine Log Configuration (full control of thread) does not have “enable_all” toggled (use “disable_all”) and cycle the process to see if you get significantly less data in the process log.
2. if you are getting CORE files, that would indicate you have a memory leak associated with this process that will eventually crash your process.  Check your error log to ensure there are no glaring issues, correct them, and restart the site process and remove the coreddump file.  Check the error database to ensure message health is in order and no routing/xlates need correcting.
3. If need be, stop all inbound threads to exhaust the recovery database and perform a siteinit to eliminate runaway processes on this site that would be causing a coredump

[Matthew Brophy]

what are the permissions for your xlate within the file directory?

If Cloverleaf is attempting to load the xlate with the ‘hci’ account and this xlate was moved to the directory (from non-prod) via a user account, the permissions would likely be tied to the user account and not allow ‘hci’ to access it.

 

The simple fix would be to change the file permissions of the xlate to ‘777’ full read/write for everyone.

[Matthew Brophy]

if your filtering criteria is simple (one field / non-iterating), the incoming procedure is where you’d want to define it.

Using the generic proc to handle arguments is a modular method to be used for any thread’s filtering.  Attached is generic proc that can use a list, range or even a lookup table. Put the generic proc in your master site so it is 1) central and 2) there is no other derivative in your environment.

Call the procedure in the route pre proc, then supply the arguments (below)

List space-delimited

{FILTERLIST {HMSH RPBH LECH}} {DISP KILL} {SEG PV1} {FLD 3} {CMP 3} {COMMENT {Remove facilities based on facility in PV1.3.4}}​

Contain range

{FILTERRANGE {EDMA MROH}} {DISP CONTINUE} {SEG PV1} {FLD 3} {CMP 0} {START 0} {END 3} {COMMENT {filter messages based on PV1.3.1}}

Lookup table

{FILTERTBL {rxstrategies_facilities.tbl}} {DISP CONTINUE} {SEG PV1} {FLD 3} {CMP 3} {COMMENT {send if facility is found in table}}​

If it gets more involved than filtering like this, the xlate (suppress) criteria is an easy way to handle messages

• This reply was modified 4 years, 10 months ago by Matthew Brophy.

Attachments:

You must be logged in to view attached files.

[Matthew Brophy]

we encountered search performance issues when files were quite large (+1 GB)

I may be looking at this wrong, but I have noticed that when defining the site SMAT criteria, it looks like it takes the larger of the three values. (i.e. size limit = 100 MB age limit = 14 days….. SMAT will exceed 100 MB to store 14 days worth).

I understand the best practice sizing is SMAT size 100GB / 1 million transactions.

So if you only wanted to keep 50,000 messages, you would size 5GB

Sizing of a Cloverleaf site would be for 1/2 the disk to recovery DB and the other 1/2 for SMAT archiving.

[Author]

Replies