gnumed-doc 1.1.7-1 / usr / share / doc / gnumed / user-manual / GmManualGuiElements.html

<h1><a name="Fields_and_Elements_used_in_the"></a>  Fields and Elements used in the GNUmed User Interface </h1>
<p />
<div class="twikiToc"> <ul>
<li> <a href="#Menu_items"> Menu items</a>
</li> <li> <a href="#Shortcuts"> Shortcuts</a>
</li> <li> <a href="#Buttons"> Buttons</a>
</li> <li> <a href="#Input_fields"> Input fields</a> <ul>
<li> <a href="#The_Phrasewheel"> The Phrasewheel</a> <ul>
<li> <a href="#start_of_phrase_suggestions"> start-of-phrase suggestions</a>
</li> <li> <a href="#start_of_word_suggestions"> start-of-word suggestions</a>
</li> <li> <a href="#substring_suggestions">  substring suggestions</a>
</li> <li> <a href="#Phrasewheel_types"> Phrasewheel types</a> <ul>
<li> <a href="#selection_only_input"> selection-only input</a>
</li> <li> <a href="#free_text_input"> free-text input</a>
</li></ul> 
</li></ul> 
</li> <li> <a href="#The_Date_Timestamp_field"> The Date-Timestamp field</a>
</li></ul> 
</li></ul> 
</div>
<p />
<h2 class="twikinetRoundedAttachments"><span class="twikinetHeader"><a name="Menu_items"></a> Menu items </span></h2>
<p />
Menu items are in some cases hard-coded. They can also be dynamically added to the bottoms of menus and submenus by plugins.
<p />
<h2 class="twikinetRoundedAttachments"><span class="twikinetHeader"><a name="Shortcuts"></a> Shortcuts </span></h2>
<p />
There exist two levels of shortcuts, "direct accessor keys" and "active letters". More information can be found in <a href="http://lists.gnu.org/archive/html/gnumed-devel/2009-06/msg00240.html" rel="nofollow" target="_top">this -devel posting</a>.
<p />
<h2 class="twikinetRoundedAttachments"><span class="twikinetHeader"><a name="Buttons"></a> Buttons </span></h2>
<p />
Some buttons, for example the "Action&#8230;" button inside the Measurements plugin, open to display a submenu of options. The first element of such menus may only inform about usage, and does nothing else even if selected.
<p />
<h2 class="twikinetRoundedAttachments"><span class="twikinetHeader"><a name="Input_fields"></a> Input fields </span></h2>
<p />
<h3><a name="The_Phrasewheel"></a> The Phrasewheel </h3>
<p />
A phrasewheel is a special kind of text field which makes suggestions as you type-in phrases. Most of the time, you will notice this when inputting data into a form, say, when creating a new patient. The suggestions offered often come directly from your current GNUmed database. This way, the phrasewheel learns which words and phrases <strong>you</strong> and <strong>your group</strong> use, and adapts to that. Where some of the examples below mix different kinds of content, they do so purely for illustrative purposes&#8230; all matches within any one phrasewheel will be context-sensitive. A phrasewheel for entering family names will not suggest drugs, and vice versa.
<p />
In order for items (like episode names) to be included in dropdown lists, their names must be at least two characters in length.
<p />
If in doubt whether a particular text field really is of phrasewheel type (because you think it ought to offer suggestions, but doesn't appear to do so) you can type the <code>*</code> (asterisk) into the empty field (or simply press the <em>&lt;Cursor-Down&gt;</em> key). If the field is a phrasewheel it should dropdown a list of <strong>all</strong> available suggestions (on account of your not having typed anything, everything will match). Note that this may take rather long, especially when the programmer did not take care to constrain the maximum number of suggestions returned.
<p />
Also note that if you are a rapid typist, some phrasewheels may not appear to bring up suggestions. That is so because suggestions are only generated after a brief period of inactivity (eg. no typing) which is typically configured to something like 300 milliseconds.
<p />
The phrasewheel uses three strategies to search for suggestions:
<p />
<h4><a name="start_of_phrase_suggestions"></a> <em>start-of-phrase</em> suggestions </h4>
<p />
This is used when you have typed only very few characters. It will make suggestions which <strong>start</strong> with what you have already typed. That way the list of suggestions for <code>su</code> will include
<p /> <ul>
<li> in a patient search <ul>
<li> <code>sullivan</code>
</li> <li> <code>sutherton</code>
</li> <li> <code>Surber</code> (yes, case insensitive)
</li></ul> 
</li></ul> 
<p /> <ul>
<li> in a filtering among document types <ul>
<li> <code>summary of stay</code>
</li></ul> 
</li></ul> 
<p />
but neither of, for example in a patient search
<p /> <ul>
<li> <code>McSullivan</code> (not at start of phrase)
</li> <li> <code>The Sutherton Clan</code> (start of word but not start of phrase)
</li> <li> <code>Smith</code> (<em>sm</em> does not match <em>su</em>)
</li> <li> <code>foo bar</code> (well ... <img src="rsrc/TWiki/SmiliesPlugin/smile.gif" alt="smile" title="smile" border="0" /> )
</li></ul> 
<p />
The above will usually appear after you had typed just one or a few characters.
<p />
<h4><a name="start_of_word_suggestions"></a> <em>start-of-word</em> suggestions </h4>
<p />
If you keep on typing more characters, the phrasewheel assumes the list of suggestions isn't adequate. It starts searching for suggestions matching at <strong>word boundaries</strong> within phrases. Given the above example, both of
<p /> <ul>
<li> <code>The Sutherton Clan</code> (start of second word matches)
</li> <li> <code>in the sullen landscape of Italy</code> (<em>sullen</em> matches)
</li> <li> <code>Discharge Summaries</code> (<em>Summaries</em> matches)
</li></ul> 
<p />
would be <strong>added</strong> to the list of suggestions for <code>su</code> depending on the actual additional characters entered.
<p />
This added mode usually kicks in after typing 3-5 characters.
<p />
<h4><a name="substring_suggestions"></a> <em>substring</em> suggestions </h4>
<p />
Still the suggestions may not contain anything helpful to you so you keep on typing away. The phrasewheel then starts making suggestions based on matches <strong>anywhere</strong> within a phrase. So the following suggestions are added to the list:
<p /> <ul>
<li> <code>McSullivan</code>
</li> <li> <code>insulin regime</code>
</li> <li> <code>the insurgency rises</code>
</li></ul> 
<p />
This sort of generating suggestions typically becomes added after you type more than 5 characters.
<p />
<em>Note that you can always bring up the list of <strong>all</strong> suggestions by typing <code>*</code> within an empty phrasewheel.</em>
<p />
<h4><a name="Phrasewheel_types"></a> Phrasewheel types </h4>
<p />
There are two <strong>types</strong> of phrasewheels: Those in which you must use a phrase that's on the list of suggestions (<em>selection-only</em>) and those which will accept new input, too (<em>free-text</em>).
<p />
<h5><a name="selection_only_input"></a> <em>selection-only</em> input </h5>
<p />
Here you must either select a suggestion from the list or enter a term <strong>exactly</strong> as it appears on the list of suggestions. Basically this is akin to a drop-down list field which lets you type what you mean and drops down a narrowed down list of possible matches. You can always drop down the entire list of possible inputs by entering <code>*</code> into the empty field or pressing the <em>&lt;Cursor-Down&gt;</em> key.
<p />
A typical use would be in selecting a document type out of a list of pre-configured types.
<p />
<h5><a name="free_text_input"></a> <em>free-text</em> input </h5>
<p />
This phrasewheel will not constrain what you enter. If the phrase you type is not on the list of suggestions GNUmed will happily use it anyways. This may lead to a new phrase ending up in the database ready for being suggested the next time around. This is how GNUmed learns your language habits.
<p />
Here a typical use would be entering the street of an address. New streets are learned by GNUmed as addresses are entered.
<p />
<hr />
<p />
<h3><a name="The_Date_Timestamp_field"></a> The Date-Timestamp field </h3>
<p />
This is a special version of the phrasewheel. It allows entering dates in various formats and - as you type - makes suggestions for dates you might mean. Those suggestions make sense medically. It is possible to enter fuzzy timestamps where you don't know the month, day, or time of day. Explicit offset definitions (+6w = +6 weeks) are possible.
<p />
Separators ( - / . ) are likely to have the following effect:
<p /> <ul>
<li> - (hyphen): forces processing as (yy)yy-mm-dd
</li> <li> / (slash): forces processing as mm-dd-yy(yy)
</li> <li> . (dot): accepts yyyy.mm.dd, otherwise treats the end-portion as year
</li></ul> 
<p />
The suggestions offered by GNUmed are affected by whether or not the  mxDateTime module is available on the user's machine. For historical dates within the past 70 years, the century (if omitted) is assumed. Archival reference: <a href="http://lists.gnu.org/archive/html/gnumed-devel/2011-07/msg00285.html" rel="nofollow" target="_top">here</a>.
<p />
Presently, when time precision is not required in a value that accepts time, GNUmed has been auto-assigning a time of 11:11:11 with the aim of reducing date changes across GMT-offset time zones.
<p />
<p />
<em>Next:</em> <strong><a href="GmManualBasicEmrConcept.html" class="twikiLink">Understanding the GNUmed EMR</a></strong>
<p />
<hr />
<p />
<hr />