I am trying to create a "Treatment Plan" for our physical therapist, and this plan needs to consist of several choices that are document variables. The plan is going to be a new observation. How do I add all of these different choices to an edit field connected to an observation? Can I also have a text component translate to that edit field as well? Thanks in advance.
OBSNOW("obsterm", DOCUMENT.variable1 + DOCUMENT.variable2 + DOCUMENT.variable3 + etc)
or
OBSNOW("obsterm", DOCUMENT.variable1 + " " + DOCUMENT.variable2 + " " + DOCUMENT.variable3 + etc)
or if you need to split it up later
OBSNOW("obsterm", DOCUMENT.variable1 + "~" + DOCUMENT.variable2 + "~" + DOCUMENT.variable3 + etc)
Thanks, that is what I needed, but I have one more question. I don't want the document variables to translate by themselves only in the observation, but I need to be able to add pretext and post text to the document variables in the translation in the observation. How do I go about doing that?
where it says DOCUMENT.variable?, replace it with the text translation from the corresponding edit field (minus the { & }), and remove the text translations from the fields.
OBSNOW("obsterm", CFMT(DOCUMENT.variable1, "", "pretext", "", "post text", "") + "~" + CFMT(DOCUMENT.variable2, "", "pretext", "", "post text", "") + "~" + CFMT(DOCUMENT.variable3, "", "pretext", "", "post text", "") + etc)
Thanks!, That worked with one slight problem. I am getting a \b or a \b0 in front of everything in the form and it is stored in the observation. The text translation looks fine. Here is what I have:
{!OBSNOW("PT PLAN", CFMT(DOCUMENT.FREQUENCY_, "", "Frequency: ", "B", "") + CFMT(DOCUMENT.DURATION_, "", " Duration: ", "B", "")
+HRET + CFMT(DOCUMENT.SERVICES_CH, "", "Services: ", "B", "")
+HRET + CFMT(DOCUMENT.REHAB_POTENT, "", "Rehab Potential: ", "B", "")
+HRET + CFMT(DOCUMENT.EDUCATIONAL_, "", "Educational Needs: ", "B", "")
+HRET + CFMT(DOCUMENT.EDUCATION_PE, "", "Education performed today: ", "B", "")
+HRET + CFMT(DOCUMENT.DISCHARGE_PL, "", "Discharge planning recommendations: ", "B", ""))}
I tried it with just one document variable and it does the same thing.
{!OBSNOW("PT HPI", CFMT(DOCUMENT.TEST_1, "", "Test 1 ", "B", ""))}
What am I missing?
Those are the bolding characters. They can't be used in form fields, only translations. Take the "B"s out of the code.
jjordet said:
where it says DOCUMENT.variable?, replace it with the text translation from the corresponding edit field (minus the { & }), and remove the text translations from the fields.
OBSNOW("obsterm", CFMT(DOCUMENT.variable1, "", "pretext", "", "post text", "") + "~" + CFMT(DOCUMENT.variable2, "", "pretext", "", "post text", "") + "~" + CFMT(DOCUMENT.variable3, "", "pretext", "", "post text", "") + etc)
I was looking for a sample DLG with the following functions you are describing. I onlyhave basic knowledge in VFE and hence most of my forms have checkboxes, lists etc (min MEL language). What was I was trying to do is build a multiline edit field (observation) which has a whole number of buttons that write into it (can be document variables). for example
the ROS or history forms built by patient link etc
(unable to do a print screen of what I am looking at, sorry). Hoping someone could help me
Joseph Mathews
Thank you for sharing.
This is what I was looking for. Gives me a jump start when I create the form
Thank you once again for the quick reply.
my email is [email protected] if you need any help in PT related stuff
Joseph
jjordet said:
or
In the forms 2, there is pre text:what was typed: post text coming into the translation. How to get that out??
Also could you let me know how a button with certain text translation could be dropped into the multiline field edit
Joseph
you can remove the pre/post text pieces from the code in the code window on the right.
action button...SETVALUES...click append...put the text to append in the field to the right of the MLEF you want it to go into.
I tried to send you more PT forms, but you're email address can't be found...