[Daniel Murphy]

Jim, I am curious as to how to ADD an OBX (or any segment) using Xlate.

I was trying to figure that out, but ended up writing my own Tcl to handle it. Which doesn’t look like this, but that’s the beauty of programming 🙂

[Daniel Murphy]

The error you are getting refers to the symbols. Try removing those as well from around each of your parameters.

Example:

Code:

{call prPFlags_insert(patient_flags.encounter, patient_flags.ecd,patient_flags.notification_consent,patient_flags.PCP_provid_and_name)}

It’s at least worth a quick shot 🙂

[Daniel Murphy]

I think you may want to delete the records based upon the date in addition to the MRN-1.

Any record that is OLDER than 2018-05-30 will be removed but leaves the current date.

[Daniel Murphy]

Just curious – why the need to downgrade Tcl?

[Daniel Murphy]

I agree with Mike Brown here.

I am also the Lone Ranger with the Interfaces. I trained the Help Desk and the Business Analysts to be able to manage all of the common issues that go wrong when the automated side fails.

The Help Desk covers simple things such as restarting processes and threads; where the Business Analysts have deeper knowledge of the inner workings of the Xlates and/or code that makes them work. Each are required to know that kind of information so that I may go away for a week and not need to worry. I also have trained one business analyst that is more general purpose and CAN do the work needed in my absence; just not as efficient nor as effective. When I return, I am briefed on what they did and I make any changes necessary to make it how it needs to be.

I made EXTENSIVE and COMPLETE documentation for things that require more than that; for example: Rebooting the Red Hat Linux Server, what to do should that goes off into an unknown state and becomes unresponsive, how to restart the interface engines, etc.

My documents come complete with pictures and verbiage just to make it clear on what to do.

That covers about 99% of the issues. Then there are the exceptionally rare cases; where I am needed to look into it. I usually take a computer with me and my cell phone, but even then I may not be reached. Text messages and voicemail always comes in after you regain service. Whenever I go on vacation, I just make it a point to make it out to an area that has service and play catch-up. The majority of the time, even when called, it is NOT an urgent need and can wait until my return.

That remaining 0.01% will just have to go unchecked until I return. 😉

[Daniel Murphy]

Thanks Robbie!

What I will be sharing will hopefully be a treat for everyone; as this has been many months in the making as well as some really neat concepts and ideas I came up with just to work within the confines of Cloverleaf. No doubt, it has taken me a LONG time due to interruptions at work and other high priorities that come along. I am glad to finally be in the light outside that long dark tunnel. 🙂

I’m excited to give my work out for everyone to benefit from. It is one solution, and there may be other better ways to go about it. At least it IS a working solution! I will do my best to make it easy to understand and follow.

Looking at my schedule, it looks to be next week before I will be able to write up that document. It will be written, as I need that for work too. It is far easier to read over one’s notes than to figure it all out from scratch – that’s true of the person that makes the notes. Good documentation saves a *lot* of time in the long run 🙂

[Daniel Murphy]

This is a major step for me. I have several projects that RELY upon being able to utilize this functionality.

I cannot imagine someone else that has less SQL experience or Cloverleaf experience trying to set this up. Thankfully, when I was first starting out in Software Engineering and DBA, he taught me to always think outside of the box; when you finally find a solution, try it over again and see if there is another approach that would be better.

Hopefully, in the next few days, I can put together a document that details out the process and my findings 🙂

[Daniel Murphy]

I finally got the entire process to work! Thanks again, Peter!

You need to be simple with stored procedures with Cloverleaf. It doesn’t like running a stored procedure that does multiple things before it returns back to Cloverleaf.

I had to basically separate all of my processes that work up to getting the data from the database before sending to Cloverleaf. After the Read is successful, it was pretty straight forward, but you need that pre-cursor setup in place for it.

I’ll make a write-up and post it of how I made this process work for those that come later to try and understand this process. There are a bunch of moving parts, and if someone tried to do this based on the documentation alone, I believe they would not fare well.

[Daniel Murphy]

Thank you Peter!

This gives me some insight and at least a new direction from which I can try to get this working.

Just to clarify: I am NOT wanting the MessageId from the messages generated within Cloverleaf itself. MessageId happens to be an Identity Primary Key and Index to my table in SQL Server. The MessageId from THAT table is what I would like to pass around and use to control updates to which messages were sent or not 🙂

Incidentally, I basically did what you suggested prior to my writing the initial post, but within a single execution of the stored procedure. All messages ready to be sent were queried and placed them into a variable table. After-which, it would update the actual table with the date sent and then return the contents of the variable table to Cloverleaf. Peculiarly, the variable table managed to get nothing to return; so no messages were sent but the date sent was applied. I believe there is an order of operations that took place that logically should not have. Either way, that method was flawed, and I knew that while writing it. The issue is that it assumed the messages were sent successfully all of the time, and that may not be the case. I was trying out different ideas, just to see what would and would not work.

I will edit the stored procedure for Read Success and change my backend logic – might need to add a bit flag to avoid making a new table *just* for this purpose. This will mark all unsent messages with the DateSent. Upon failure, nothing changes, and those will show back up in the next run. No clean-up will be needed 🙂

[Daniel Murphy]

I am using RHEL 6 as well and I had this issue with 6.1.2 not sending any messages if I did a query for what I needed to resend. After I selected the messages and resent them, it did the SAME as what you seen by notifying me it sent but nothing ever went.

If I did NOT search for what I needed and loaded all messages and selected them individually, then resent those, it would work. This is OK when you have a few messages to sort through, but you NEED the search and send feature.

This is an issue in 6.1.x through 6.1.2.x

There is a patch 6.1.3 that corrects this issue.

I highly recommend upgrading to 6.1.3. as it works as expected 🙂

[Daniel Murphy]

I don’t think you can use AD credentials to connect to the SQL Server Database. I created SQL Authentication Accounts in my database server; assuming you have control over your particular SQL Server.

I am using RedHat Linux 6.4 with Cloverleaf 6.1.3.

[Author]

Replies