[B Pariyesana]

Matt,

I also experience similar issue during 5.41 to 5.5 testing. Cloverleaf FTP protocol can’t send file as ASCII to our IBM Mainframe, which make the file unreadable in Mainframe. It also pick up the file as binnary, so the Cloverleaf receives an EBCDIC file.

As a workaround, we will use an in house FTP Upoc that employs curl outside the engine. First we had a problem when we we tried to use this after we upgraded the box, and we found out that the upgrade automatically forced our curl to use 7.15 libcurl, and since our curl version is 7.14, we set curl to use static library 7.14 libcurl.

We are hoping that Quovadx will fix this issue so we don’t have to use special UpoC interface for this. May I know the incident number that you have opened with them so I can just refer to that number when I call them?

Thanks

Budhi Pariyesana

MedStar Health

[B Pariyesana]

Thanks Scott.

For quovadx people:

So is it a bug in Cloverleaf 5.*?

Thanks

B. Pariyesana

Sr. Interface Engineer

MedStar Health IS

[B Pariyesana]

We also have Meditech interfaces but didn’t have the same pleasant experience as others when we built it. Meditech is very sensitive to sequence of transactions that need to be happened to change patient status or event, also specific patient status and patient type rule, such as, place outpatient in bed will only work with patient status A when the type is X.

The scripts that we created for Meditech was voted as longest OB TPS script that was ever written here 🙂

B. Pariyesana

MedStar Health

[B Pariyesana]

Beware when you’re using Advance Scheduling in 5.3. Cloverleaf stops scheduling next scan if it receives file lock error during scanning the directory. It doesn’t report the error to the console too

B. Pariyesana

MedStar Health

[Author]

Replies