[Hai Nguyen]

My colleague advised me a twist, modified version to CONTINUE the $mh instead of KILLREPLY $mh. The ACK flow works as expected now.

Thank you 🙂

[Hai Nguyen]

Expect One per message, or NAK when timeout.

[Hai Nguyen]

Thank you, Jason and Jim,
I will check with ImmuLINK to confirm whether they have worked with CLV.
I initially developed separate PDLs for inbound and outbound processing, though neither is fully complete. Since the vendor requires bidirectional data exchange, it became quite complex to consolidate everything into a single PDL.
As a result, I shifted to developing a standalone program as the front end to ImmuLINK and CLV as the backend for integration with other applications.
Thanks again for looking into this.

• This reply was modified 1 month, 3 weeks ago by Hai Nguyen.

[Hai Nguyen]

Hello Jason,

it’s ASTM, I attached the spec , hope it can answer your questions. Due to the complexity of this interface, I’m thinking about developing a process outside of Cloverleaf, e.g.  daemon.

Thanks for checking,

-hai

Attachments:

You must be logged in to view attached files.

[Hai Nguyen]

Hello Jim,

The ImmuLINK is client and Cloverleaf is the server.

The ImmuLINK has this reason, so we can’t set the pairs of threads. ImmuLINK act as the client initiating connections to the LIS, rather than the LIS acting as the client, to avoid CPU performance issues observed in previous deployments when ImmuLINK was configured as the host.

We’re on CLV version cis2022.09. I’m not sure if TCP/IP ‘Encapsulated Options’ can meet the several interaction exchange ENQ, STX, ETB, etc. before and after data transfer, e.g.  handshake, ACK, etc. So, I plan to develop a PDL for this work.

Example:

ImmuLINK → ENQ
CLV      → ACK
ImmuLINK → frames (data segments)
CLV      → ACK (per frame)
ImmuLINK → EOT
CLV      → (done)

I’d like to learn if how to configure ib thread “order_ib” sending data to thread ‘bidirection’, then ‘bidirection’ forwarding to ImmuLINK, like returning ACK message to the sender Application.

Thank you,

-hai

 

 

 

[Hai Nguyen]

Hi Jason,

It’s an instrument interface, ImmuLINK, not lab. Here are more details with more complex, the ACK and NAK are handle by developing a Low-level Protocol with a PDL, like following flow:

TCP Connected

│

▼

Establishment Phase

│

▼

Analyzer → ENQ

│

LIS → ACK

│

▼

Transfer Phase

│

▼

STX Frame 1 ETB

│

▼

ACK

│

▼

STX Frame 2 ETB

│

▼

ACK

│

▼

STX Frame N ETX

│

▼

ACK

│

▼

Send EOT

│

▼

Neutral State

 

My plan maybe not possible to develop on CLV. I just try to see if anyone has done this. Otherwise, we will see their other option working with files.

Thank you,

-hai

[Hai Nguyen]

The vendor for analyzer insists their instrument can do only this pattern over TCP/IP. They initiate the connection, then exchange order/result messages thru the same connection.

[Hai Nguyen]

Hello Rob,
We were late to register for this event as it’s closed. Is it possible if we can participate the Cloverleaf sessions on Tuesday 5/21 only?
Hope can see you, colleagues, and the Infor team at the event.
Thank you,
…hai
nguyen.hai@mayo.edu

[Hai Nguyen]

Great! looking forward using Cloverleaf engine to implement FHIR.

Thanks Jim and Ron.

[Hai Nguyen]

Same here Jim, I downloaded all resources from FHIR website, and tried to compile their .xsd files in Cloverleaf XML manger, it failed.

[Hai Nguyen]

Only sqlite3 installed on my box:

$ which sqlite3

/hci/qdx5.7/integrator/tcl/bin/sqlite3

$ which sqlite

/usr/bin/which: no sqlite in (/hci/qdx5.7/integrator/…)

I have to wait until our current 5.7 upgrading to CLV version 6 then  😛

Thank you all for your help and check!

[Hai Nguyen]

Thanks for quick response and suggestion Kevin.

I got the same error with both log-in sessions Unix and Cloverleaf user, and there is only “sqlite3” on both sessions.

### Logged in as an Unix user:

$ which sqlite

which: no sqlite in (/bin:/usr/bin:/usr/ucb:/etc:/opt/sfw/bin:/hci:/hci/bin:/hci/kshlib:/usr/local/bin:.)

$ which sqlite3

/usr/bin/sqlite3

$ sqlite3 foo

SQLite version 3.3.6

Enter “.help” for instructions

sqlite> create virtual table bar using fts3;

SQL error: near “virtual”: syntax error

### Logged in as a Cloverleaf user:

$ which sqlite

/usr/bin/which: no sqlite in (/hci/qdx5.7/integrator/…)

$ which sqlite3

/hci/qdx5.7/integrator/tcl/bin/sqlite3

$ sqlite3 foo

SQLite version 3.6.4

Enter “.help” for instructions

Enter SQL statements terminated with a “;”

sqlite> create virtual table bar using fts3;

SQL error: no such module: fts3

My Linux version is:

Red Hat Enterprise Linux Server release 5.9 (Tikanga)

Kernel 2.6.18-348.3.1.el5 on an x86_64

[Hai Nguyen]

Hello,

Yup, I learn the fts feature from https://www.sqlite.org/fts3.html#section_1_2 🙂 and like to try it out.

I have no luck following Charlie’s and Kevin’s suggestion, I always use command “sqlite3” for SQLite.

$ sqlite3 test.db

SQLite version 3.6.4

Enter “.help” for instructions

Enter SQL statements terminated with a “;”

sqlite> CREATE VIRTUAL TABLE docs USING fts3(title, body);

SQL error: no such module: fts3

sqlite> .q

$ sqlite3 foo

SQLite version 3.6.4

Enter “.help” for instructions

Enter SQL statements terminated with a “;”

sqlite> create virtual table bar using fts3;

SQL error: no such module: fts3

sqlite> .q

Max, I have SQLite version 3.6.4, which is embedded in our CLV 5.7. Don’t know why it works for Charlie on the same version with mine.

[Author]

Replies