Clover call Store procedure issue

[David Ma]

I have a store SQL procedure (CREATE_HOLMS_EPIC_EXTRACT) in SQL server. When we run it in SQL server, It will return all rows in one line. following is one of the query results

P101746,Plastname,Pfirstname,19520113,OMW|Osteoporosis Management (OMW)|N/A|20231117070922^ Functional|Functional|N/A|20231117070922^ Pain|Pain|N/A|20231117070922^ Med Review|Medication Review|N/A|20231117070922^ HBAControl|Hgb A1c<9 (HbA1c Control)|Met|20231117070922^ EYE|Eye Exam|Met|20231117070922^ Diabetes Meds|Diabetes Meds|Met|20231117070922

But when I use PROTOCOL: database-inbound and “{CALL CREATE_HOLMS_EPIC_EXTRACT()};” commend at it only gets first row. Following is one example of the query results running from Cloverleaf.

P101746,Plastname,Pfirstname,19520113,OMW|Osteoporosis Management (OMW)|N/A|20231117070922

Is there anything I missed?  I attached my thread setting in this post.

Thanks!

 

 

Attachments:

You must be logged in to view attached files.

Topic

[Jim Kosloskey]

Perhaps rather than ‘Each Row as a Message’ you might want ‘Each Read as a Message’?

Although, are you sure you really want to get all of the tuples located dumped into the engine at once?

 

 

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[David Ma]

I tried “Each Read as a Message’” and I still see the first row of the query results for each patient.

I scheduled it to run once a month. The thread will combine all rows (results) to one HL7 messages with multi OBXs if all the rows of one patient’s results are in one line.

[Jim Vilbrandt]

As long as your calling a stored procedure, why not create the complete HL7 message there and return it as a string? I have a couple database query interfaces (without a called procedure) that return each HL7 segment as a field. I then replace commas and quotes in an inbound data TPS. As you are dealing with a variable number of segments, it would be better to deliver the HL7 as a single string.

[Author]

Replies