[Brenda Carpenter]

We also have Cloverleaf 19.1  and also noticed the duplicate smat files in the process directory – it can be annoying, but I just ignore the first one with the symbolic link when doing my searches.

I also found that when running the test tool for the XLT,  and have added a Pre Xlate TPS and selected ‘process all records’ –  the testing is ending after it finds the first KILL message in the tclproc. If the messages, CONTINUE, then the processing continues along to the next message, but stops as soon as it hits a KILL message.  I don’t recall this happening in any of the other versions but my supervisor thought he heard something about this issue somewhere.

MSG that is output to result screen:  Xlate Tps proc ADT_Filter did not return a message to debug.

Thankfully, this does not happen when testing multiple messages in the TPS test tool, which will process both KILL and CONTINUE messages back to back. So, this is not a big issue since there is a are work around, I was just trying to test a handful of random ADT messages for a new ancillary system to ensure all the kill and continue logic and formatting logic worked as expected.  Just thought I would mention it here.

PS I looked around on Infor Xtreme for notes on this and see if anyone else had the issue, but frankly I’m kinda lost out there.

[Brenda Carpenter]

Thanks Jim for your wealth of knowledge and valuable two cents!  We are going to err on the side of caution and request a new range of ports from this vendor.  😀

[Brenda Carpenter]

Thank you both for your inputs.   So far we have them running on test sporadically as we are in the initial phase of setting up connectivity, and yes we are on UNIX.

Rob Lindsey – are you also on UNIX?

[Brenda Carpenter]

Hi Gene,

I have worked with X12 but only as file input and file outputs, but can you use the protocol pdl-tcpip instead of the tcpip where you don’t need to define those parameters? We normally use mlp_tcp.pdl as the default PDL options.

For receiving the inbound x12  as a file, I needed  two TPS Inbound Data tcls, one I wrote to remove the carriage return – if there is one on your file and the other is to use this cloverleaf tcl:   hciX12splitinterchange.

Hope this helps a little. Brenda

[Brenda Carpenter]

Hi Lina,

We also submit VXU for 19 yr olds and under (unless Rabies – then all Rabies vaccines must be sent to DOH) and it seems to be working fine for us, has been in place quite some time.  You would just have to adjust your days to be 18 yr old.

Pre proc filter calls another proc below:

   if {[getAgeDays $birthdate $admitdate] > 6935} {

       lappend dispList “KILL $mh”

       if {$debug} {echo “$module KILL msg ecd $ecd age greater than 19”}

   } else {

        continue

###############################################

# Name:      getAgeDays

# Purpose:   Get number of days old at time of admission

# UPoC type:   upoc

# Args:      none

#

proc getAgeDays {dob admitdate} {

  set admitdays [expr [clock scan [string range $admitdate 0 7]] / 60 / 60 / 24]

  set dobdays [expr [clock scan $dob] / 60 / 60 / 24]

  set ageDays [expr $admitdays – $dobdays]

  return $ageDays

}

[Brenda Carpenter]

Ah… true… I was not looking at that resolution since there are so many places that that code needs to be added… I’ll meet with Peter and discuss adding this solution instead.  It will impact ALL HL7 financial messages, where I think I was looking at trying not to impact all the current state messages that work just fine  

Thanks!

Brenda 8)

[Brenda Carpenter]

Thanks Jim for your opinion and words of advice, I greatly appreciate it!  

In my example, I am only changing the { to an & when one resides in the MSH2 as the  sub sub field delimiter instead of the place where the ampersand is – this would indicate that it is not used in any other field in the message.  Now in the case if they used non standard delimiters and they used the ampersand as a different qualifier in MSH2, then we would be in trouble – I should add additional code to make sure the other three delimiters are NOT an ampersand to ensure that doesn’t happen.  When dealing with humans (the patient access team), there is always a chance of error in freeform text fields and we cannot go to the vendor in that case – only re-iterate the importance of not using special characters when this issue arises.  In the other instance where this happened we did ask that vendor to NOT send the ampersands in the data/message for our messages.

We will continue to monitor this, thanks everyone for your inputs!

Brenda

[Brenda Carpenter]

Hi all,

Peter did open a ticket for this, but I also did find a work around to replace the ampersands with the word ‘AND’ and then replaced all the curlybraces with the ampersands.  

Initial testing looks good, I am going to do a compare and volume test before implementing, but this will put the message back to the way we expect it to normally be.  In example below, patient access team accidentally used the ampersand in the patient reason for visit field.

Before:

MSH|^~{|SOARF|J0A8|||201711011601||ADT^A08|

PV2|||^COLD SYMPTONS & EAR PAIN|||

GT1|1|….|STONECOLD^OUT^^^^^L^^^20170716~STONECOLD^OUT^^^^^L^^^20160520{20170716||

IN1|1|194^POMCO|…|HEALTH|STONECOLD^OUT^^^^^L^^^20170716~STONECOLD^OUT^^^^^L^^^20160520{20170716|SELF

Code used to revert the delimiter back to an ampersand:

       set curlybrace “{“

       set addlsubFieldSep [cindex $msg 7]       ;  #MSH2 input field

        if {“$addlsubFieldSep” eq “$curlybrace” } {

             regsub -all {[&]} $msg {AND} msg

             regsub -all {[{]} $msg {&} msg

Giving output as below:

MSH|^~&|SOARF|J0A8|

PV2|||^COLD SYMPTONS AND EAR PAIN||||~~~~FALSE|

GT1|1|…|STONECOLD^OUT^^^^^L^^^20170716~STONECOLD^OUT^^^^^L^^^20160520&20170716||…

IN1|1|194^POMCO|….|||HEALTH|STONECOLD^OUT^^^^^L^^^20170716~STONECOLD^OUT^^^^^L^^^20160520&20170716|SELF|…

We are not actually using or passing the second date field downstream, we are merely checking for the presence of one to see if the data has a termination date.

Any questions, let me know  8)

Thanks.. Brenda

[Brenda Carpenter]

Sorry, just following up on this, we beleive the issue was due to our live server on a different version than our test server.. we had installed CL6.2 in test.  Once we removed test server from GM, everything worked fine.

We now have both test and live on CL 6.2 and appears to all be working ok.  I did notice tho, that in the GM Dashboard view, when I select one of the sites, the Netmonitor pane does not contain anything in the view, only the thread status grid and process status grid has the threads and processes. I have been looking around on how to fix this, but can’t find how to get the monitor view in that third pane.

Ant ideas?

Thanks

Brenda

[Brenda Carpenter]

Thanks Rob, will do!

[Brenda Carpenter]

We have another smat database (I work with Peter Heggie) that is corrupt and the script is not working to reset it.

Errors being received on it, it’s an outbound thread:

prod:prod:INFO/0:xto_soacom_ordr:05/02/2017 00:30:12] Starting protocol thread xto_soacom_ordr as tid 2.

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 00:30:12] Error returned from SMAT database: database corruption at line 1364 of [091570e46d]. Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 00:30:12] Error returned from SMAT database: database corruption at line 1403 of [091570e46d]. Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 00:30:12] Error returned from SMAT database: statement aborts at 5: [] . Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 00:30:12] Error returned from SMAT database: database disk image is malformed. Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 00:30:12] Unable access db xto_soacom_ord_ob. Error 11:’database disk image is malformed’

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 00:30:12] Internal Init failed for SMAT xto_soacom_ord_ob

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 00:30:12] Initializing secondary for xto_soacom_ord_ob when not present

Additional errors:

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: database corruption at line 1364 of [091570e46d]. Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: database corruption at line 1403 of [091570e46d]. Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: statement aborts at 5: [] . Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: database disk image is malformed. Error code is 11

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Unable access db xto_soacom_ord_ob. Error 11:’database disk image is malformed’

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Internal Init failed for SMAT xto_soacom_ord_ob

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Initializing secondary for xto_soacom_ord_ob when  present

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: API call with NULL database connection pointer. Error code is 21

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: misuse at line 44 of [091570e46d]. Error code is 21

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error 21 ‘(NULL)’ while executing ATTACH ‘xto_soacom_ord_ob.smatdb-sec’ AS sec; in xto_soacom_ord_ob

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: API call with NULL database connection pointer. Error code is 21

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: misuse at line 44 of [091570e46d]. Error code is 21

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error 21 ‘(NULL)’ while executing ATTACH ‘xto_soacom_ord_ob.smatdb-sec’ AS sec KEY ‘ancinprd’; in xto_soacom_ord_ob

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: API call with NULL database connection pointer. Error code is 21

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error returned from SMAT database: misuse at line 44 of [091570e46d]. Error code is 21

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error 21 ‘(NULL)’ while executing DETACH sec; in xto_soacom_ord_ob

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Initializing secondary for xto_soacom_ord_ob when not present

[pd  :open:ERR /0:xto_soacom_ordr:05/02/2017 09:13:52] Error 21: Secondary collapse failed for xto_soacom_ord_ob

[Brenda Carpenter]

Forgot to answer the other two questions,

I modified the X12 variant to include the ISA/IEA and formatted them to receivers spec in the xlate

and yes, I used a counter for the total record count on the trailers.

PM me if you need more detailed info!

-Brenda

[Brenda Carpenter]

Hi Lisa,

I have built a FF to 834 x12 file in cloverleaf and needed to use multiple HRLs.

Each input record was defined as FRL, then built HRLs to do the repeating, this HRL within the HRL repeats for x amount of times.  Then within that LOOP, I have other HRL loops  to repeat data as necessary.  I think the 834 is much easier than the 835 will be tho.

ie: FF HRL:

STHDRSEG

BGNSEG

DTPFSEG

N1SSEG

N1PSEG

INSLOOPHRL  –  REPEATS X AMT OF TIMES

SETRLRSEG

EXAMPLE OF INSLOOP:

INSSEG

REFLOOP    – REPEATS X AMT OF TIMES

DTPLOOP   – REPEATS WHILE… LOGIC

NM1SEG

PERSEG

ETC….

Hope that helps.. it took quite a while to get this just right, so keep tweaking!

Brenda

[Brenda Carpenter]

Hi Carl,

I was able to test this today.. and it worked for me.  I tested your format of a range with asterisk first, then three ranges, all three worked fine –  and I was “comparing > ”  – I also tested this format below which also worked fine after manipulating the time parameters.  I changed the email message each time to ensure I was getting the right saved alert, I tested both last send and last receive alerts:

1/8:00-15:30/*/* 1/15:45-17:30,19:30-23:30/*/*

Also, I did not have to recycle the net monitor or anything else, once I saved the alert itself, it took effect.  Sorry I couldn’t help you much.  Maybe take a look at your alert email setup for incorrect email address or something else?

Brenda

[Brenda Carpenter]

No, sorry, I didn’t, I have it on my list for today.. will keep you posted.

[Author]

Replies