[Amol Kulkarni]

Hi Scott,

saw your reply on the CSC, the large files that we wanted to SFTP out were from CSC to client site. It seems that 800MB tiff file will prevent the CSC from sending the file out, on CSC 5.3.

However I believe that 5.4 can handle 1GB ++ tif files (encrypted), so i am hoping to upgrade and hope for the best.

At present when we encounter 800MB file we fax out the result to the client.

[Amol Kulkarni]

Rick,

We are very interested in the Advance Protocols, especially the CBT tutorials on XML, ODBC, HTTP. Although there are quite a few free sites with information available, in my humble opionion many of us struggle when trying to relate these within the frame work of the cloverleaf engine. In others words “THE HOW TO” apply these protocols using real examples with the cloverleaf engine.

Thank you

[Amol Kulkarni]

Alka,

From the example input, should the final OUTPUT be:

OBX|1|NM|NA^LAB01262^Sodium||145|meq/L|137-144|H|||F

ADD|1||analyzed on hemolyzed specimen

OBX|2|NM|NA^LAB01262^Sodium||145|meq/L|137-144|H|||F

ADD|2||analyzed on hemolyzed specimen

[Amol Kulkarni]

We were finally able to get our Eagle system to write out to the cloverleaf engine a message, except it is in EBCDIC format. Is there a table that I should have in place to convert the EBCDIC format to ASCII for the engine to translate. Is there a proc that I should be using?

Jim and Mary, thank you for your earlier response, the thread behaves as you indicate below.

Thank to all in advance.

Amol

[Amol Kulkarni]

Max and Jim,

Totally agree with you, takes away from the standard.

I did follow up with TDS group, and the answer was too easy.

All they wanted was to take the sub fields and map these data elements to the next field, i.e MRN = PID3, the hosp ID = PID.4 and so on.

[Amol Kulkarni]

Max,

Thank you so very much for the scripts and the examples. I find your scripts very helpful and quick to work with when the suits want immediate information. New members of the interface group get a useful education with your example on how to manipulate the output thus empowering them.

Again thank you very much.

[Amol Kulkarni]

Jim,

I am an old person  🙂 (actually in the old dog catagory); but yes you are correct i should be changing these old tcls as i come across them.

🙂 Amol

[Amol Kulkarni]

Mike,

Perhaps this might be useful:

proc check_Alpha {} {

 upvar xlateId       xlateId        

       xlateInList   xlateInList    

       xlateInTypes  xlateInTypes  

       xlateInVals   xlateInVals    

       xlateOutList  xlateOutList  

       xlateOutTypes xlateOutTypes  

       xlateOutVals  xlateOutVals  

   set code  [lindex $xlateInVals 0]

   set suppmsg “transaction suppressed, value is alpha”

          echo >$code<    if {[ctype alpha $code]} {            set xlateOutVals [lindex $xlateInVals 0]    } else {            set xlateOutVals $suppmsg    }            return $xlateOutVals }

[Amol Kulkarni]

Alka,

I am curious, why wont the lab place the TEXT comment on the

INR02 Test. If they were to define a comment under INR02, SCC would release this information with results and the comment in the NTE segment.

Perhaps I am missing something.

[Amol Kulkarni]

Alka,

Thinking this one over again, the test INR; is this reported on all PT’s at your Medical Center? If yes, I would rerequest the lab to set up the PT test as a group test with INR as one its resulting components. The INR would be setup as an individual test with the INR message as a message under the message tab.

From the example you posted, it seems that the PT and INR are setup as two seperate individual tests and therefore the two seperate messages from SCC.

One other identifier you may want to use is the SCC ID in OBR.3 (filler ID); but you have to be careful because if I am not mistaken one can have upto 24 different test under a single ID.

Again I am guessing that the SCC on your side is setup similar to ours.

[Amol Kulkarni]

This is a sample message that our SCC sends outbound for the PT /INR results. As i recall, this was accomplished by SCC to pull in the text that had to accompany every PT/INR test, thereby avoiding a seperate message.

I think there is a way on SCC to attach a constant comment as a note in the test setup; perhaps the lab IT can enable this for you.

MSH|^~&|SCC||HCM|MSMC|20080422144503||ORU^R01||P|2.2

PID|||222222||LAST^JAMES||12220202|M||||||||||222222

PV1||u|02^G111||||9000^NDIAH^DEVI

ORC|RE||1|425||||||||9000^NDIAH^DEVI||||O

OBR|||1|00250^PRO TIME^^PT^PRO TIME|||200604120610|||||||200604181350||||||||200604181350|||F||||||||||||||||||||NR

OBX||NM|00250^PRO TIME^^PRO^PRO TIME||30.8|SECONDS|12.3-15.5|H|||F

OBX||NM|02553^INR^^INR^INR||3.3||||||F

NTE|||General Recommendations for Monitoring I.N.R. (International

NTE|||Normalization Ratio) Values for Warfarin Anticoagulant

NTE|||Therapy.

NTE|||Note: These are general recommendation and are not intended to

NTE|||      direct treatment for individual patients. Individual

NTE|||      treatment will vary with specific circumstances.

NTE|||Recommended

NTE|||I.N.R. Level         Clinical Circumstance

NTE|||2.0-3.0     Deep vein thrombosis, pulmonary embolism,x0d

NTE|||                 atrial fibrillation, tissue heart valves,

NTE|||                 prevention of systemic embolism in

NTE|||                 valvular heart disease, acute anterior

NTE|||                 myocardial infarction.

NTE|||2.5-3.5     Pevention of systemic embolism with

NTE|||                 mechanical mitral or aortic valves.

NTE|||3.0-4.0     Arterial thromboembolism in the

NTE|||                  antiphospholipid syndrome.

NTE|||3.0-4.5       Prevention of systemic embolism in high

NTE|||                   risk patients with mechanical mitral or

NTE|||                    aortic valves, recurrent systemic

[Amol Kulkarni]

Does not sound right from SCC; The Test and all its result interpretation should be in a single message. Perhaps I am misunderstanding.

Can you please post an example of what SCC is sending out.

We have SCC and IBEX interface through the cloverleaf engine and hopfully I can compare our SCC results outbound for a possible solution.

Thanks

[Amol Kulkarni]

Sundeep, try setting the keepalive setting to 1800 = 15 minutes if you are on an AIX server.

To determine current keepalive setting:  no -a | grep tcp_keepidle.

[Amol Kulkarni]

Reply to John’s question: Yes, I can not figure out why are we showing in the AtStaff Service Log, connecting and disconnect. This pattern continues throughout the day; meanwhile I have 100+ connections using the same mlp driver and these do not have similar behaviour.

thanks

[Amol Kulkarni]

Thomas, reply to your questions:

1.  Is there a firewall between you and the vendor?  –> No, the server is in the Medical Center.

2.  What is the volume of activity between your engine and the vendors system?  Are there periods of inactivity? –> There are periods of inactivity during the day.

My understanding is that a receiver basically is always up and listening.

When I did check system logs in the Vendors application, the log states dropping connection and then restarting.

Thanks

amol

[Author]

Replies