Sending @VGR command by itself

[Scott Morris]

As you may or may not know, in VGR, you can trigger another VGR iForm by placing an "@VGR=myNextForm" command in your orderstring.  This works great when it's being placed with one or more orders before it, but it seems to have trouble when placing it by itself.  For example, if you have an iForm with a number of orders and a trigger for a follow-up iForm, it works great if the user chooses one or more order and the iForm, but if they choose the iForm and none of the other orders, it throws an error.

The error is along the lines of "unable to open VGR file mynextform^^^.vgr"  Up to this point, we've gotten around this issue since each of the iForms had a "tracking order" on it and so there would always be at least one order.  However, we're trying to phase out the tracking order.

Has anyone found a good way to fix this?

[Russ Garlow]

You can launch one by itself all day long if you make a linkable outline for it. Little more setup time, but it's pretty much bulletproof.

[Michael Hudson]

Russ,

By linkable outline, do you mean an outline with only one order item st to order with previous, as the first item when the outline loads? If so, that would require an outline being built for each iform correct? If not by this method, of what method do you speak?

Michael

On Thu, Feb 7, 2013 at 10:43 AM, Russ Garlow <russg...@gmail.com> wrote:

You can launch one by itself all day long if you make a linkable outline for it. Little more setup time, but it's pretty much bulletproof.

--
You received this message because you are subscribed to the Google Groups "HEO iForms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heo-iforms+...@googlegroups.com.
To post to this group, send email to heo-i...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/heo-iforms/-/9k21z8_qvOUJ.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Russ Garlow]

That's exactly what I mean Michael, anything that's common use here gets a linkable outline set up when it's made. Lately I've been stringing the VGR load commands together, but it's much quicker for me to use the outlines if it's just one or two in the middle of another form rather than setting up the CAT orderstring and making sure the tracking order is first (I'm used to making that the last order).

[Michael Hudson]

Thanks Russ! I might give this a try for the common iforms.

Michael

--
You received this message because you are subscribed to the Google Groups "HEO iForms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heo-iforms+...@googlegroups.com.
To post to this group, send email to heo-i...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/heo-iforms/-/MPP_LXXKqVkJ.

[Scott Morris]

I think I just came up with the way to do this without having to build an outline for every one of my iForms.  In HEO, there are two orders with the order_type = 's': the "RETURN (29998)" and "EMPTY (29999)" orders.  There should be one empty and one return for each facility.  I'm not 100% sure what their main purpose is (and I'm still playing around with them), but I know that one of the uses of the empty order is to be placeholders on outlines for remarks and [spacer]s.

I found that if you can find your empty order's OIS, you can order it via VGR and it will ignore it.  It won't show up on the ADC pane, it won't show up in the order confirmation screen, and it doesn't go into the orders table of the database.  Effectively, it does nothing.

However, you can use it to make sure that there's always an @LOAD_ORDER command in front of your @VGR command.  So, for instance, where

@VGR=ivfadult

would give you the "can't find ivfadult^^^.vgr" error message, if you place the order as

@LOAD_ORDER=OIS=290283@VGR=ivfadult

(assuming that your EMPTY order's OIS is 290283), then it works just fine.

[Michael Hudson]

Scott,

I have found the orders and am using them in one iform and it works perfectly! I wonder if there is any downstream effect, such as HPF or anything. I am going to have the HPF analyst look for this 

Mike

--

You received this message because you are subscribed to the Google Groups "HEO iForms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heo-iforms+...@googlegroups.com.
To post to this group, send email to heo-i...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/heo-iforms/-/2reUTRY2BgAJ.

[Scott Morris]

After placing this order on a test patient, I looked in the database to see if there was any trace of it and I didn't see it there so I was pretty confident that it's safe, but I appreciate more eyes looking at it just to be sure.

[Michael Hudson]

Scott,

I have validation that nothing goes to HPF. I was doing some digging and the Return (29999) equates to the hidden facility order to launch an outline (Found in o_outline) and Spacer (29999) is the remark or spacer you place in an outline (found in o_outline). So baaed in this information as well, these are safe to use. 

You are brilliant Scott!

Thanks,

Michael

On Thu, Feb 21, 2013 at 10:15 AM, Scott Morris <scott.r...@gmail.com> wrote:

After placing this order on a test patient, I looked in the database to see if there was any trace of it and I didn't see it there so I was pretty confident that it's safe, but I appreciate more eyes looking at it just to be sure.

--

You received this message because you are subscribed to the Google Groups "HEO iForms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heo-iforms+...@googlegroups.com.
To post to this group, send email to heo-i...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/heo-iforms/-/OtJWsbI2LOIJ.

[C.E. Coleman]

I think I may have a way to fix this. I'll have to look at the code and see what it is doing and make sure its doing what you need. Ill try to post it as quick as I can get to it.

C.E. Coleman