Forum Replies Created
-
AuthorReplies
-
Yep, agreed. I added a time stamp to the A21 table as well. I’ve just gotta do a little research to see how long patients are typically on LOA. Then I’ll put in a cleanup routine.
Hi Charlie,
Thanks for the advice. I decided to do the following:
I’m writing the start of the LOA to the database when I receive an A21. Using a standard outbound database thread/translation.
I put a pre-proc on the orders route to check if the patient is on LOA, and if so, I kill the message(s), and write the order(s) to the database for later use.
I put a pre-proc on the A22 route to do the following:
- remove the entry in the A21 table (taking the patient off LOA)
- add the A22 to the dispList
- do a search for any orders which were stored
- add each order to the dispList as a continue
I’ve tested the code out in the testing tool and so far everything is working as expected. I’m going to add the code to the routes, and resubmit some messages to verify that it’ll work.
I realized what the problem was, I was looking at the variant for the type of message I was receiving, and comparing it with the translation. What I hadn’t noticed is, the translation uses a different message type, but the formats are very close to each other. I’m going to have to separate the translation for this message type from the others so that it’ll address the message correctly.
Thanks Jim
Hey Jim,
This is inside an if, but in an effort to eliminate that as the possible problem I removed it and found the same problem. I also tried to eliminate the iterate as the problem and hard coded it to pathcopy two IN1 and two IN2 segments to the correct addresses, and it failed as well. I attached the screenshot of the inbound and outbound message formats in the translation gui.
Hey Jim,
Here’s what I have for the Inbound HL7
3(0).0(0).IN1(0)
3(0).0(0).IN2(0)
3(0).0(1).IN1(0)
3(0).0(1).IN2(0)
Here’s what I have for the outbound:
1(0).0(0).IN1(0)
1(0).0(0).IN2(0)
what it should look like if there’s a second:
1(0).0(1).IN1(0)
1(0).0(1).IN2(0)
Finally figured out where the alert was coming from…it was an old server that we thought was shut down. Apparently there was a job on there that was sending out an alert. No wonder we couldn’t find it.
-
AuthorReplies