instead of using a large checkgroup, you can use a table instead like this ( see also the assessment template ) group-box 75x56 "" data [ slabel "The patient presents for" return table 70x40 "Presents with" options [ multi "reason" left .99 ] data [ "evaluation of " "recheck" "management of" "review of radiographic data ordered at the previous visit." ] ] This is a multi-select table, use the control key to help select more than one item.
Let's see the generated text, and also the same text once you've saved the document. On saving, a punctuation routine kicks in cleaning up extra punctuation marks. It may be missing something....
so Ive been splitting up my larger templates-still getting commas. also, i seem to have messed-up the included radio group... group-box 75x210 "" data [ table 75x210 "Presents with" options[ multi "reason" left .99 ] data [ "The patient presents for" "evaluation of " "recheck" none "management of" "review of radiographic data ordered at the previous visit." "followup of" "recheck and follow-up." "medication management" "recheck, follow-up and med mgmt." "recheck, follow-up and possible repeat procedure." "recheck, follow-up and the procedure scheduled at the last visit." "headaches. " "neck pain." none "neck and RUE pain. " "neck and LUE pain. " "RIGHT shoulder pain" "LEFT shoulder pain" "RIGHT UE pain" "LEFT UE pain. " "thoracic pain. " "low back pain. " "back and RLE pain. " "back and LLE pain. " "back and B/L LE pain. " "RIGHT hip pain. " "LEFT hip pain. " "B/L hip pain. " "RIGHT knee pain. " "LEFT knee pain. " "B/L knee pain. " "RIGHT shin pain. " "LEFT shin pain. " "RIGHT foot/ankle pain. " "LEFT foot/ankle pain. " "B/L foot/ankle pain. " ] ] at 68x0 group-box 68x200 "" data [ radio-group 60x15 data [ ". Injury occurred about" " Symptoms began about" " Pt. was last seen here about" ] ] at 72x22 radio-group 10x10 data [ "1" "2" ] radio-group 20x10 data [ "4" "a few" ] at 72x34 radio-group 40x26 data [ "days ago." "week(s) ago." "month(s) ago." "year(s) ago." "over one year ago." ] return at 68x60 group-box 66x140 "" data [ table 75x180 "Presents with" options[ multi "reason" left .99 ] data [ "At that time did undergo " "an initial evaluation." "follow-up for a procedure recently performed." " Also underwent medication management." "spinal manipulation." "cervical MBBs." "cervical MBRFA." "an initial cervical ESI." "a repeat cervical ESI." "a stellate ganglion block." "an AC joint injection." "a GH joint injection" "a shoulder bursa injection." "thoracic MBBs." "thoracic MBRFA" "a thoracic ESI." "a trochanteric bursa injection." "a hip injection." "an initial lumbar ESI. " "a repeat lumbar ESI." " epidural adhesiolysis." "a lumbar sympathetic block." "RF DRG treatments." "trigger point injections." ] ] any insight?
The point of using a table is that you can scroll thru the list conserving vertical space. It doesn't make that much sense making your table as high as all your data ...
unrelated. 1) Bedouins "migrate" in the desert (I think). 2) an edit list as opposed to the check box or table.
the difference is that an edit list only allows one choice. the table and check box can be mutiple choices.
Yes, I understand that. How would you suggest I approach making a template including all the above info/possibilities. I have already broken up one of my larger check group-dominated templates but am still having issues.. 1) making them fit on the m-series TPCs with 1024x768 res (even with the appropriate beta). 2) I believe the commas still exist in the generated text. I realize these are distinctly unrelated issues.
Do you use the TPC in portrait (taller than wider) or landscape (wider than taller) ? I love my Toshiba M200's HiRes screen []
I prefer landscape. I have 3 TPCs. 2 of the older M-series motions (1024x768) and a newer, high res LE-series. The LE has no probs with the templates.
If you create a template that is higher than your tablet's screen resolution, well, there is not a lot that Synapse can do. You could break your template into two parts. eg. call them .... visit-reason-1, and visit-reason-2 then create two text macros, *visit-reason-1* and *visit-reason-2* and define them as $visit-reason-1 and $visit-reason-2 You then create a new macro call visit reason, and it has *visit-reason-1* *visit-reason-2* so this will then bring up the gui templates as choices when doing the replacement.