[Kumar Ananth]

We have a tcl proc that checks the message and throws it out if the size is larger than 64K. I had to remove that as I had to pass HL7 BASE64 PDF from a vendor to Cerner. I’ve created a new variant and bumped the OBX-5 to handle the message size in CL. Looks like Cerner is not able to digest all of OBX-5 content which is over 64K and vendor can’t break it into repeating OBX-5. So, I need to send the OBX-5 content as repeating OBX-5 with each OBX-5 less than 64K. Any suggestions on how/where (xlate or tcl) to accomplish this? Anyone willing to share your script or provide a starter script?

TIA

[Kumar Ananth]

That make sense. Thanks Jim!

[Kumar Ananth]

Thanks for reply Brandon. I had to add some logic to move around some value within HL7 message for patients less than 8 yrs old. Hence the age_in_years tcl to determine the age from DOB. I don’t need the decimal. I have rounding logic which rounds the returned value(age with decimal).

Looks like clock scan range is 1902 to 2037. I’ve been searching on the web about clock scan and came across following.  

I tested it and the information seems to be accurate. I changed the DOB from 1900 to 1902 and it works – no tcl call out error. I get tcl call out error if the 1901 or 1900 or lower.

“clock scan “dateString” ?-base clockVal? ?-gmt boolean? Convert dateString to an integer clock value. If only a time is specified, current date is assumed. Without time, midnight is assumed. Without time zone uses local zone unless -gmt is specified. If -base is used, the date in clockVal is used for determining the time on a specific day or other date-relative conversions (like daylight savings time for day or greater units). Allowed range of years is 1902 to 2037. DateString consists of zero or more specifications of the following forms: “

[Kumar Ananth]

Update: Issue is resolved. Putting {} around General Lab in the VALUELIST took care of the issue.

[Kumar Ananth]

Jim,

I tried doing that and got the same results(hangs) in command line too.

[Kumar Ananth]

Thankyou all for the reply. Keith McLeod was right on the money. I still had the smat file. So, loaded the smat file with detail level zero and I see the hex values between segments. When the vendor is doing manual push the messages are getting sent properly with hex value for CR between segments. But, on the automatic sweep, the vendor is sending CR and Line feed(0A) between segments.

[Kumar Ananth]

Keith,

that’s exactly what I was looking for and it worked perfectly. Thank you for your reply.

[Kumar Ananth]

Hi Daniel,

Thank you for the reply. Yes, the result is coming out of Cerner Millennium.

No

[Author]

Replies