Notifications
Clear all
Topic starter
I have noticed on my custom forms that single line edit fields do not translate to the Text of the document until you navigate to another field on the form or a separate form in the encounter. Is there a way to set them up to auto-translate in the same manner that the multi-line edit fields do?
I have one encounter that contains a single form. Sometimes that single line edit field might be the last field that a user has input for. It's silly for them to have to navigate to an additional field to have it translate. Granted it populates when the encounter is put on hold or signed but the provider may want to review the Text before closing the document and when it doesn't show in the Text it causes confusion.
I can set it up as a multi-line edit field with 1 line but that seems asinine.
Posted : June 7, 2017 6:11 am
Yeah, the Single line fields tend to do that. They also don't allow Quicktext to be used inside of them, so if you want a single line field with Quicktext abilities, you have to make a multiline and set it to 1 line.
Not sure if anything can be done about it, but I feel your pain.
Posted : June 7, 2017 11:45 am
I wonder if we need to report this to Logical Innovations.....
Posted : June 8, 2017 1:32 am
I wonder if this is a vfe issue or if it is a bug/limitation in the way the UI works in Centricity?
Posted : June 8, 2017 2:12 am
Topic starter
I just tested a CCC form and found that the single line fields behave in the same manner as my VFE forms and do not auto-translate the text. Disappointing.
Posted : June 8, 2017 3:30 am
This is a limitation of the EMR/Windows API. While the edit field is in use, it has complete focus. Translations only occur when focus is transferred elsewhere. Historically, this has never been an issue since closing the form meant that the field lost focus. It wasn't until CPS introduced the current form-translation layout where you can swap between the two, that it became visible, thus your comment. Unfortunately, it is not an easy thing for GE to remedy since the idea of being able to swap came with the ability to 'keep your place' in the form, a truly nice feature that Oracle EMR users are not afforded.
As a workaround, you might consider placing a 'fake' record button that, when clicked, does nothing but move the focus out of the edit field. Your users will be none the wiser and the translation will appear. Alternatively, you could train them to tab out of the field prior to viewing the documentation, which will force the translation as well. Lastly, you might consider the use of the edit field. I would assume that the reason they want to review the text is because the text exceeds the size of the field. Unless you are controlling character counts, you might consider changing this to a multi-line edit field instead, one that is taller than a single line to eliminate the need to swap views and review the text note.
Posted : June 8, 2017 4:45 am
