Database-inbound/outbound protocol in query thread?

[Diana de Bruin]

I’m trying to figure out if it’s possible to use the v6.0.2 database-inbound or -outbound protocol in combination with a query thread.

For example:

I would like to receive a HL7 ADT query and use the patientid to query a table (database-outbound?) and then give the info read from the table to a .xlt so that I can build a reply message.

I don’t think this is possible looking at the options in de database inbound/outbound protocols.

—

At the moment I’m using a tclproc to process the query and place the answer in a comma-seperated string. The string is send back as a reply message to the original thread using disposition “OVER”.

Diana

LUMC -Leiden University Medical Centre
The Netherlands

Topic

[Peter Heggie]

Unfortunately one cannot currently use a disposition of OVER in a SEND-OK or SEND-FAIL upoc. I wish we could, I have two interfaces that require both an FTP put and a database update but Cloverleaf cannot support more than a two protocol interface. I recommend using Infor Extreme to submit an enhancement request for the implementation of disposition OVER in a post-protocol upoc.

Having said that, I think you can achieve what you want by using two interfaces – the first would be for the HL7 query interface to feed a database outbound protocol that writes the query details to a table; the second interface would be a database inbound that executes a stored procedure which reads the query table populated by the first interface in orer to get the query details and then performs the query and returns the result. The output returned from this database inbound protocol would be sent to the submitter of the query. You would need to clean up the query table so that the details just processed do not get processed again.

Peter

Peter Heggie

[Author]

Replies