Hi, Does anyone have a suggestion on how to re-push the same height (as previously recorded) to the flowsheet so the flowsheet shows the height was recorded 'today'...and not 4 years ago when it was originally recorded?
The only thing I've come up with is to enter something different in the height field, tab to next field, then go back and re-enter the previous height. I don't think this is a good idea as there is room for user error.
Not sure if a quick text could be designed to re-push the current height to the flowsheet or not. Anyone have ideas? thank you!
Hi Laryssa,
If you have access to the source code for your form you can add the following to the MEL Workspace:
{obsnow("HEIGHT",obsany("HEIGHT"))}
This will push the last value to today's date automatically. You can also use the same code within a quicktext to accomplish the same thing, but if you don't want it to actually return any text when used you will want to modify it to read:
{obsnow("HEIGHT",obsany("HEIGHT"))
str("")}
*using obsany instead of obsprev will prevent you from overwriting the current value if the quicktext is used accidentally after a new, valid value is entered.
Hope that helps,
Ryan
I realize height doesn't change much in most cases, but as a matter of policy and accuracy, I would think it would be a bad idea to document an observation for a date that it wasn't made.
We have a button on our Nurse Intake form labelled "HEIGHT UNCHANGED". When clicked, it executes the following: OBSNOW("HEIGHT (CM)", OBSPREV("HEIGHT (CM)"))
Brilliant! Thank you so much for the code!!
In response to the concern or policy and accuracy, our vitals form (vital signs 2- CCC) does not push the height to the flowsheet if you enter the same value as previously recorded. So when you look at the flowsheet, even if you confirm the height is the same at every visit and you enter the same value as previsouly recorded, the flowsheet is not updated to reflect that you verified and entered the height today. The flowsheet only reflects the date when the value was originally recorded. The form is a bit flawed in that regards.
Ah that's good to know Laryssa. I wasn't aware of that. Thanks for the follow-up.