Notifications
Clear all
Topic starter
I have a runprocess button to print automatically with 1 click. What I'm wondering, can I tie that to an observation term? Basically I'm wanting proof it was printed (and not with the annoying handout was printed crap that fills up the document list). Seems like i've seen someone ask / do something like this in the past...
Posted : May 29, 2014 1:35 am
You can put as many instructions in the runprocess instructions of action button as you would like, including an OBSNOW write to whatever term you pick.
Posted : May 29, 2014 1:54 am
Topic starter
JClarkLRGH said:
You can put as many instructions in the runprocess instructions of action button as you would like, including an OBSNOW write to whatever term you pick.
Good to know, but I don't know how to make it write to an obs term...
Posted : May 29, 2014 1:55 am
I do this in a RUNPROCESS MEL Action button:
{
PRINTHANDOUT("Handouts\DIABPED\Height & Weight Status")
DOCUMENT.HWS="Height and Weight Status handout printed and given to patient"
}
Then I do this for the translation in the next blank text field
{CFMT(DOCUMENT.HWS ,"","","")}
But you could change the document variable for an obs term.
Posted : May 29, 2014 1:56 am
Topic starter
Posted : May 29, 2014 2:00 am
Topic starter
{
PRINTHANDOUT("Handouts\GRA\Allergy Action Plan")
OBSNOW("HOALLAP")="Allergy Action Plan was printed"
}
So I have the above as my RUNPROCESS, but it's not actually writing the value to the obsterm. If I click the print button then it prints and displays "Allergy Action Plan printed" like it should, but if I put it on hold and come back it's gone and clinical list changes doesn't have anything listed. Thoughts?
Posted : December 3, 2014 9:57 am
Topic starter
Anyone?
Posted : December 11, 2014 5:26 am
Topic starter
Anyone?!
Posted : January 5, 2015 10:04 am
Writing to an observation requires different syntax than writing to a document variable. Writing to OBS term requires you to define value as a parameter in the observation code.
You would need to write:
OBSNOW(“HOALLAP”,”Allergy Action Plan was printed”)
As an FYI, if you want to push the observation to a date other than date/time of associated update - you can add an additional third parameter to control the date that the obs is stored under. We use this to allow users to push historical data into the flowsheet under the actual date the information is from, often time with a document variable linked to a calendar type field:
OBSNOW(“HOALLAP”,"Allergy Action Plan was printed",DOCUMENT.DATEOFTEST)
Posted : January 14, 2015 5:34 am
Topic starter
Dirrrr! I've done that on several of my other forms, not sure why I didn't figure that out on my own. SMH. Thanks for your advice, I'm gonna go sit in the corner now 🙂
Posted : January 14, 2015 5:44 am
Chris,
If you haven't gotten the answer yet, here is the magic to writing to an OBS term. Instead of doing the assignment like a document variable, you need to embed the value you want to assign to the OBS term within the parentheses.
OBSNOW("HOALLAP", "Allergy Action Plan was printed")
As stated above, if you want the date of the obs term to be something other than today/right now, you could add a third parameter of the date for the observation.
OBSNOW("HOALLAP", "Allergy Action Plan was printed", <Date of Past OBS>)
Posted : June 13, 2016 7:21 am
