The following table lists all of the guidance points in order.
Click on a guidance ID to find it in the guide.
| ID |
Guideline |
Compliance |
| MSP-0010 |
Do not allow the prescribing area to occlude the Patient Banner
|
Mandatory |
| MSP-0020 |
Allow a patient's current medications to be accessed whilst prescribing,
preferably by allowing current medications to be displayed simultaneously
|
Recommended |
| MSP-0030 |
Support switching to, or simultaneous presentation of,
other views without losing prescription information entered so far
|
Recommended |
| MSP-0040 |
If it is possible to navigate away from the prescribing area
before completing a prescription, ensure that a clear indication
that there is an incomplete prescription remains displayed on screen
|
Recommended |
| MSP-0050 |
Do not allow the prescribing area to be positioned such that it
separates the controls (such as those on a toolbar) from the view
to which they relate (see Design Guidance –
Medications List)
|
Recommended |
| MSP-0060 |
Support the display of a Quick List containing preselected drug names
|
Mandatory |
| MSP-0070 |
Minimise the frequency with which the contents of the Quick List change
|
Recommended |
| MSP-0080 |
When one or more Quick Lists are provided, display one by
default when the prescribing process is started
|
Mandatory |
| MSP-0090 |
Include a description of the contents of the Quick List at the
top or bottom of the list
|
Mandatory |
| MSP-0100 |
Display the Quick List below (or as a drop-down list extension of)
the search text input box
|
Recommended |
| MSP-0110 |
Do not support navigation (such as expanding and collapsing
or drilling down) within a Quick List
|
Mandatory |
| MSP-0120 |
Limit the number of drugs in the Quick List such that they can be
displayed in full without a scroll bar
|
Mandatory |
| MSP-0130 |
Allow only items that can be displayed in a search results
list to be included in a Quick List
|
Mandatory |
| MSP-0140 |
Supplement Quick List entries with shortcut keys
|
Mandatory |
| MSP-0150 |
Display shortcut keys to the right of each entry in the Quick List
|
Mandatory |
| MSP-0160 |
Use alternate row shading in the Quick List, as in the search results list
|
Recommended |
| MSP-0170 |
Display a notification when the contents of a Quick List have
changed since it was last presented to the current user
|
Mandatory |
| MSP-0180 |
Provide a control for closing the Quick List notification
|
Mandatory |
| MSP-0190 |
Provide a control for disabling the notification so that it is
not displayed again (until the Quick List is changed again)
|
Mandatory |
| MSP-0200 |
Display the Quick List notification every time the Quick List is
displayed (until the user selects an option that disables it)
|
Mandatory |
| MSP-0210 |
Do not display the notification such that it obscures the contents
of the Quick List
|
Recommended |
| MSP-0220 |
Close the notification automatically when either a drug is selected
from the Quick List or text is entered into the search text input box
|
Recommended |
| MSP-0230 |
Do not allow a drug to be selected from the Quick List by using
the keyboard until the notification has been closed
|
Mandatory |
| MSP-0240 |
Limit the number of Quick Lists that are available to an
individual user to the minimum that are contextually appropriate
|
Recommended |
| MSP-0250 |
When multiple Quick Lists are available to a single user,
provide a means of navigating between them
|
Mandatory |
| MSP-0260 |
When multiple Quick Lists are necessary, display the currently
selected Quick List in the control that is used to select a Quick List
|
Mandatory |
| MSP-0270 |
When multiple Quick Lists are necessary, use the words 'Quick List'
in a label for the Quick List control or within the control
|
Recommended |
| MSP-0280 |
Do not allow the search results list to be positioned such that it is
separated from the search text input box by other controls or by a
significant space
|
Mandatory |
| MSP-0290 |
Clearly describe the scope of the search
|
Mandatory |
| MSP-0300 |
Use an in-field prompt in the search text input box to describe
the scope of the search
|
Recommended |
| MSP-0310 |
Do not support entry of codes in the search text input box. (This does
not preclude the use of spelling matching or the provision of an
alternative box for entering codes)
|
Mandatory |
| MSP-0320 |
Do not provide auto-complete in the search text input box
|
Mandatory |
| MSP-0330 |
Retain focus in the search text input box until a selection
is made in the search results list
|
Mandatory |
| MSP-0340 |
When focus is first switched to the results list, set focus to
the first entry in the list by default
|
Mandatory |
| MSP-0350 |
When space is limited (such that the search results lists may obscure
other information), support the replacement of the search text input box
with an input control in which the selected drug name is displayed
|
Recommended |
| MSP-0360 |
When a search results list has been replaced with a control in which the
selected drug name is displayed, re-display the search text input box,
the search criteria and the search results list when this control is selected
|
Recommended |
| MSP-0370 |
Display results using progressive matching where possible
|
Recommended |
| MSP-0380 |
In the absence of progressive matching, provide a static search that
submits text in the search text input box by pressing the ENTER key
and/or activating a control (such as a button) to submit the search
|
Recommended |
| MSP-0390 |
Require a minimum of two characters before displaying search results
|
Mandatory |
| MSP-0400 |
When only one character has been entered, display a message that
explains why there are no results and reports the two-character minimum
|
Mandatory |
| MSP-0410 |
When two or more characters have been entered and no matches were found,
display a message that clearly indicates a search has been performed and
no matches were found
|
Mandatory |
| MSP-0420 |
When a message is displayed, maintain a minimum height equivalent to at
least three rows of results and a width that is at least as wide as the
search text input box
|
Recommended |
| MSP-0430 |
Display search results in a list that is only as high as needed to show
the successful matches or up to a defined maximum height
|
Mandatory |
| MSP-0440 |
When the number of matches is too large to be displayed in the maximum
list height, display a message at the end of the search results list that
contains counts of the displayed results and total matches
|
Mandatory |
| MSP-0450 |
When the number of matches is too large to be displayed in the maximum
list height, place a control for displaying the full list at the end of
the search results list
|
Mandatory |
| MSP-0460 |
Allow the height of the search results list to grow to an upper
limit to accommodate the number of results matched
|
Mandatory |
| MSP-0470 |
When a limited list has been extended by selecting the control to
display a full list, extend the list by providing a scroll bar
|
Mandatory |
| MSP-0480 |
Keep search results 'flat'. Do not provide expand or collapse
mechanisms or tree-style browsing within the search results
|
Mandatory |
| MSP-0490 |
When a selection has been made in a search results list that has a
scroll bar, allow the scroll bar to be used such that the selection
can be scrolled out of view
|
Mandatory |
| MSP-0500 |
Match the text in the search text input box to generic drug
names and brand names respectively
|
Mandatory |
| MSP-0510 |
Match text entered into the search text input box to beginning
of any word (and not to substrings or endings of words)
|
Mandatory |
| MSP-0520 |
Support multiple word searching by allowing the entry of letters
separated with a space and matching those against multiple words
|
Mandatory |
| MSP-0530 |
List search results in matched order, such that matches are prioritised by
proximity to the beginning of the drug name and matches in generic drug names
are prioritised above matches in brand names
|
Mandatory |
| MSP-0540 |
Where relevancy ranking is not implemented, list search results alphabetically
within each set that have the same text matched
|
Mandatory |
| MSP-0550 |
For specific searches that return significantly more results (most
of these will be three or four character searches), support the
display of groups in the search results list
|
Recommended |
| MSP-0560 |
When a group is displayed in a search results list, provide a control
(such as a button) that, when selected, replaces the original text in
the search text input box with the full title of the group and replaces
the original search results with the results within the group
|
Recommended |
| MSP-0570 |
Support spelling matches
|
Recommended |
| MSP-0580 |
Support synonyms such that a drug name for which a synonym has been
defined is displayed when the synonym is matched
|
Recommended |
| MSP-0590 |
When there are spelling matches or synonyms to display, list them
along with other results in the search results list
|
Recommended |
| MSP-0600 |
Supplement co-drugs with text that lists the ingredients of the co-drug
|
Mandatory |
| MSP-0610 |
Format text that lists the ingredients of co-drugs such that it
is differentiated from the drug name
|
Mandatory |
| MSP-0620 |
Display prioritised results in a separate section that appears
above other results in the list
|
Recommended |
| MSP-0630 |
Separate the prioritised results from standard matches with a horizontal line
|
Recommended |
| MSP-0640 |
Provide a label for the prioritised results that
gives a brief indication of how they are prioritised
|
Recommended |
| MSP-0650 |
Ensure that the labels are sufficiently different from list
items in the search results
|
Recommended |
| MSP-0660 |
Label results that are not prioritised with
'Standard Matches'
|
Recommended |
| MSP-0670 |
When there are no prioritised matches, omit the
prioritised section, horizontal line and label
|
Recommended |
| MSP-0680 |
Display keyboard shortcuts for prioritised matches only
|
Recommended |
| MSP-0690 |
Display keyboard shortcuts on the same line as each match.
Display them right-aligned after each match
|
Recommended |
| MSP-0700 |
Where drug names associated with mis-selection errors are listed
in the search results, use formatting to draw attention to them
|
Mandatory |
| MSP-0710 |
Where drug names associated with mis-selection errors are listed
in the search results, highlight the row with a pale background colour
|
Recommended |
| MSP-0720 |
Where drug names associated with mis-selection errors are listed in
the search results, supplement the drug name with a brief warning message
|
Mandatory |
| MSP-0730 |
Display mis-selection warning messages in grey italics and in a
smaller font size than the drug name
|
Recommended |
| MSP-0740 |
Use background colour to highlight differences in characters
between text that has been entered and spelling matches
|
Recommended |
| MSP-0750 |
When spelling matches are displayed, ensure that there is sufficient
colour and contrast differences between text and both background
highlighting and spelling matching highlighting
|
Mandatory |
| MSP-0760 |
When spelling matches are displayed, ensure that there is sufficient
colour and contrast differences between background highlighting and
spelling matching highlighting
|
Mandatory |
| MSP-0770 |
For drug names that are displayed when matched on a synonym, supplement
the drug name with a message that includes the synonym
|
Mandatory |
| MSP-0780 |
Use subtle alternate shading of matches in the search results list
|
Mandatory |
| MSP-0790 |
Avoid the use of strong horizontal lines to separate individual list results
|
Mandatory |
| MSP-0800 |
Re-start alternate shading at the beginning of a new
section in a search results list
|
Mandatory |
| MSP-0810 |
When brand names that have a generic name are matched, display the
generic drug name and supplement it with the brand name
|
Mandatory |
| MSP-0820 |
Separate generic drug names and brand names with a hyphen that has a
space either side
|
Mandatory |
| MSP-0830 |
Do not display brand names unless they have been matched with
text entered in the search text input box
|
Mandatory |
| MSP-0840 |
Display generic and brand names in the same order as described in Design Guidance –
Medication Line
|
Recommended |
| MSP-0850 |
Display a cascading list on the selection of drug name and up to
two further cascading lists for basic prescription attributes
|
Mandatory |
| MSP-0860 |
Present a second list when a selection is made in the search results list
|
Mandatory |
| MSP-0870 |
Allow the width of the search results list to extend into available
space to accommodate the longest entry when first presented
|
Mandatory |
| MSP-0880 |
Allow different cascading lists (such as route and form or route and
strength) to be presented depending on the drug selected
|
Recommended |
| MSP-0890 |
Limit the options presented within cascading lists to those that are
relevant to the previous selection
|
Mandatory |
| MSP-0900 |
When a cascaded list is displayed and the search results list remains open, reduce
the width of the search results list as necessary (following Design Guidance –
Medication Line for wrapping)
|
Recommended |
| MSP-0910 |
Do not allow any of the results or cascaded lists to obscure one another
|
Mandatory |
| MSP-0920 |
Maintain visibility of selections, and the list from which they were
selected (including the search results), throughout the cascade select,
as long as there is enough space to do so without obscuring other information
|
Recommended |
| MSP-0930 |
When the width of the search results list is reduced and a scroll
bar is displayed, expand the list to show all results
|
Recommended |
| MSP-0940 |
Include a list item in each cascading list that provides access
to values that are not in the list (where they exist)
|
Mandatory |
| MSP-0950 |
Place the list item that provides access to values that are not
in the list last in the list and separate it from the rest of the
list items with a horizontal line
|
Mandatory |
| MSP-0960 |
Do not provide keyboard shortcuts for the item that provides
access to values that are not in the list
|
Mandatory |
| MSP-0970 |
Where relevant, allow a selection to be made from a cascading list
that differentiates preparations with different bio-availability
properties (such as modified release)
|
Recommended |
| MSP-0980 |
When a brand name is selected for which generic equivalents are
available, present a cascading list that includes options for the
selected brand and for generic equivalents
|
Mandatory |
| MSP-0990 |
When a brand name is selected for which there are no generic
equivalents displayed, present template prescriptions for the
brand (or proceed to a step-by-step approach)
|
Mandatory |
| MSP-1000 |
When a cascading list is presented that includes options for the
selected brand and for generic equivalents, include the drug names
(generic and brand respectively) in the cascading list
|
Recommended |
| MSP-1010 |
When a cascading list includes options for the selected brand and for
generic equivalents, divide the list into two parts
|
Recommended |
| MSP-1020 |
Display generic equivalent options above specific brand
options in cascading lists
|
Recommended |
| MSP-1030 |
Require at least drug name and route (or attributes from which the type
of medication can be derived) to be selected before template prescriptions
are displayed
|
Mandatory |
| MSP-1040 |
Display template prescriptions only after selections have been made
(manually or automatically) in all other cascading lists
|
Mandatory |
| MSP-1050 |
Keep the number of template prescriptions displayed to a
practical and useful minimum
|
Recommended |
| MSP-1060 |
When a selection has been made in the last cascading list, display a selection trail
|
Mandatory |
| MSP-1070 |
Where space is limited such that text within the list of template
prescriptions may wrap onto a new line, display the whole list of
template prescriptions on a new line (below the other input controls)
|
Mandatory |
| MSP-1080 |
When an item in a selection trail is selected, reopen the
lists for all the items in the selection trail
|
Recommended |
| MSP-1090 |
When lists are reopened before a template prescription has been
selected, remove the list of template prescriptions from view
|
Recommended |
| MSP-1100 |
When lists are reopened, display them all as they were before
the template prescriptions were displayed
|
Recommended |
| MSP-1110 |
Present template prescriptions in a list without column headings
|
Mandatory |
| MSP-1120 |
Where necessary, combine attributes into a
single column to reduce the number of columns
|
Recommended |
| MSP-1130 |
Display dose or a dose equivalent at the beginning of each template prescription
|
Mandatory |
| MSP-1140 |
When space is limited, display template prescriptions in
the style described in Design Guidance –
Medication Line
|
Recommended |
| MSP-1150 |
Do not allow horizontal scrolling of a list of template prescriptions
|
Mandatory |
| MSP-1160 |
Display only template prescriptions relevant to
the drug and selections from cascading lists
|
Mandatory |
| MSP-1170 |
Minimise (where possible, avoid) the number of template prescriptions
that have only one attribute that is different from other template
prescriptions in the same list
|
Mandatory |
| MSP-1180 |
Where possible include dose (or equivalent) and frequency
in template prescriptions
|
Recommended |
| MSP-1190 |
Include strength in template prescriptions when it is required for this drug
|
Recommended |
| MSP-1200 |
Include brand in template prescriptions when it is required for this drug
|
Recommended |
| MSP-1210 |
When a template prescription includes supplementary information,
display this information in grey italics
|
Recommended |
| MSP-1220 |
Keep the number of attributes defined by a template prescription to a minimum
|
Recommended |
| MSP-1230 |
Include an option to proceed directly to the prescription
form without selecting a template prescription
|
Mandatory |
| MSP-1240 |
Display the option for proceeding directly to the prescription form
at the end of the list and separate it from the template prescriptions
with a horizontal line
|
Mandatory |
| MSP-1250 |
After a template prescription has been selected,
display editable pre-filled input controls for each
of the data values defined by the template prescription
|
Mandatory |
| MSP-1260 |
After a template prescription has been selected (and
one or more fields are displayed as a result) provide
a control that allows the list of template prescriptions
to be reopened
|
Mandatory |
| MSP-1270 |
After a template prescription has been selected, allow
the selection of an alternative template prescription
|
Mandatory |
| MSP-1280 |
When the control for re-opening template prescriptions
has focus or is activated, draw attention to the fields
that are defined by the template prescriptions
|
Recommended |
| MSP-1290 |
When the template prescription control is selected,
provide visual cues to draw attention to the fields
that are defined by the template
|
Recommended |
| MSP-1300 |
When there are no template prescriptions to display and
a known set of safe values are available (for example, for
dose and frequency), present selection lists for those fields
sequentially (step by step)
|
Recommended |
| MSP-1310 |
Require the selection of at least drug name and route (or
attributes from which the type of medication can be derived)
before presenting input controls for any other values
|
Mandatory |
| MSP-1320 |
After selections have been made in all cascading lists,
if there are no template prescriptions, display any required
fields that will not be pre-filled
in sequence such that a
field is displayed when the previous one has been completed
|
Mandatory |
| MSP-1330 |
If a selection from a cascading list (such as frequency of
'as required') requires a further field to be completed,
display that field before the remaining required fields
|
Recommended |
| MSP-1340 |
Provide a control (such as a button) for switching to a detailed
view from which input controls for all valid fields for this
prescription can be accessed
|
Mandatory |
| MSP-1350 |
Disable the control for displaying all valid input controls until
at least a drug name and route (or attributes from which the type
of medication can be derived) have been selected
|
Recommended |
| MSP-1360 |
Provide a control that allows the switch to a more detailed
prescription form to be undone, thus returning to the previous
view containing only the required fields
|
Mandatory |
| MSP-1370 |
Restrict the number of input controls to the minimum
required to enter information needed to complete the
prescription
|
Recommended |
| MSP-1380 |
When presenting fields step by step, support pre-filling
of one or more of the fields that are already displayed
when a selection is made in a related field
|
Recommended |
| MSP-1390 |
When presenting fields step by step, allow the contents of
all fields to be reselected such that a pre-filled value,
previous choice or text entry can be changed (even if the
associated selection list has only one option)
|
Recommended |
| MSP-1400 |
Do not display optional fields, or controls for accessing
optional fields (apart from the button for accessing a more
detailed prescription form)
|
Recommended |
| MSP-1410 |
Ensure that no data is lost whilst switching from one form to another
|
Mandatory |
| MSP-1420 |
Minimise the number of controls that are needed for navigation
|
Recommended |
| MSP-1430 |
Ensure that no data is lost whilst switching from one form to another
|
Recommended |
| MSP-1440 |
Minimise the number of controls that
are needed to navigate between forms
|
Recommended |
| MSP-1450 |
Use sentence layout when fields are displayed
in an area with much greater width than height
(a thin horizontal strip)
|
Mandatory |
| MSP-1460 |
Use sentence layout for cascading lists and
whenever selection lists are presented step by step
|
Recommended |
| MSP-1470 |
When using sentence layout, for fields that
have labels, incorporate labels into the fields
|
Recommended |
| MSP-1480 |
When using sentence layout, wrap
fields onto a new line as necessary
|
Mandatory |
| MSP-1490 |
When grouping fields in sentence layout,
start a new line after each group
|
Recommended |
| MSP-1500 |
When using sentence layout, allow fields to grow
in width to fit the text entered or value selected from a list
|
Mandatory |
| MSP-1510 |
When using sentence layout, allow fields
to shrink in width when a value is changed
|
Recommended |
| MSP-1520 |
Provide labels for controls whose contents could
be interpreted as belonging to a different control
|
Recommended |
| MSP-1530 |
Display fields (and controls for accessing individual
optional fields) in a consistent order for all
prescriptions
|
Mandatory |
| MSP-1540 |
Minimise the number of different types of
input controls displayed in any one view
|
Recommended |
| MSP-1550 |
Do not allow the drug name to be scrolled out
of view. Keep the drug name visible at the top
of the prescription form, even when the form has
a scroll bar
|
Mandatory |
| MSP-1560 |
When displaying a prescription form with fields
arranged in a column, display field labels right-aligned
and on the left with the fields left-aligned and on the right
|
Recommended |
| MSP-1570 |
When placing fields labels above input controls, display
the labels left-aligned and in a
smaller font than the text displayed in the control
|
Recommended |
| MSP-1580 |
In a detailed prescription form, require the selection of drug
name and route (or drug name and attributes that allow the type
of medication to be determined) before fields are displayed in
the rest of the detailed prescription form
|
Mandatory |
| MSP-1590 |
Present the required fields by default when
a detailed prescription form is opened
|
Mandatory |
| MSP-1600 |
Provide access to a detailed prescription form that
presents the most important attributes by default and
from which all fields can be accessed
|
Mandatory |
| MSP-1610 |
Provide controls such as tabs or buttons for navigating
between areas of the detailed prescription form
|
Mandatory |
| MSP-1620 |
Provide controls for accessing all areas of the detailed
prescription such that there is no area that can only be
accessed by selecting an item (such as edit administration
times) from a selection list
|
Mandatory |
| MSP-1630 |
When displaying the input controls in a detailed
prescription form, include an appropriate set of
controls for accessing optional fields
|
Recommended |
| MSP-1640 |
When displaying a detailed prescription form,
combine the drug name and route (or drug name
and attributes that allow the type of medication
to be determined) into a single control
|
Recommended |
| MSP-1650 |
When the combined drug name and route field is
selected, provide an option to change the drug
name and route
|
Recommended |
| MSP-1660 |
Do not rely on disabling fields (or controls for accessing
optional fields) to impose an order
|
Mandatory |
| MSP-1670 |
After selections from cascading lists have been completed,
do not automatically open a selection list for a control in
the detailed prescription form unless a change to a field has
triggered the need to confirm or re-enter
values in related fields
|
Mandatory |
| MSP-1680 |
Display the drug name and route (or drug name and
attributes that allow the type of medication to be
determined) in a section at the top of the detailed
prescription view
|
Mandatory |
| MSP-1690 |
Display the first field in each section on a new line
|
Mandatory |
| MSP-1700 |
When section labels are provided, display them
at the top of the section
|
Recommended |
| MSP-1710 |
Label at least each input control,
group of input controls or section
|
Mandatory |
| MSP-1720 |
Only when it is important to encourage the completion
of an optional field, promote it by displaying an
input control for it
|
Recommended |
| MSP-1730 |
When an optional input control is promoted, support
the entry or selection of a null value and require
it to be completed
|
Recommended |
| MSP-1740 |
Display in-field prompts for fields that have
to be completed by the user and would otherwise
be blank. (A field does not have to have an
in-field prompt if
it contains a label)
|
Mandatory |
| MSP-1750 |
Use a phrase that begins with a verb for
in-field prompts in
fields that have to be completed by the user
|
Recommended |
| MSP-1760 |
Provide access to individual optional fields by placing
a control in the place where the field will appear when
the control is selected
|
Mandatory |
| MSP-1770 |
If the value selected for an optional field causes
it to increase in width, allow it to wrap onto a
new line if necessary
|
Recommended |
| MSP-1780 |
When necessary, display more than one optional field on
activation of a control for displaying an optional field
|
Recommended |
| MSP-1790 |
Use formatting to reduce the relative
emphasis on optional controls
|
Recommended |
| MSP-1800 |
Allow values entered in optional fields to be removed such
that the optional field or control is returned to the state
it was in when the prescription form was opened
|
Recommended |
| MSP-1810 |
Use other formatting to mark required fields
(or their labels) in a detailed prescription
form where necessary to ensure consistency
with other areas of the application
|
Recommended |
| MSP-1820 |
Allow some input controls to be defined that are only displayed
when certain values are selected in another input control
|
Mandatory |
| MSP-1830 |
When determining the order in which to display input
controls, prioritise the placement of fields whose values
determine which other fields may be displayed in the form
|
Recommended |
| MSP-1840 |
When determining the order in which to display input
controls, prioritise the grouping together of controls
whose values affect the options available in other controls
|
Recommended |
| MSP-1850 |
When an input causes new input control(s) to appear,
allow other input controls to move so that the new one
can be placed correctly and consistently
|
Recommended |
| MSP-1860 |
When an input causes new input control(s) to appear,
place the new input controls next (at least in sequence
if not in layout) to the control that caused it to appear
|
Recommended |
| MSP-1870 |
Allow the ESC key to be used to close a selection list
|
Mandatory |
| MSP-1880 |
Combine controls (such as check boxes and
text entry boxes) into a single list control
where this achieves a usability benefit
|
Recommended |
| MSP-1890 |
Do not empty other fields when a selection list is reopened
|
Mandatory |
| MSP-1900 |
Where possible, encourage the selection of an item
from a selection list before allowing free text to be entered
|
Recommended |
| MSP-1910 |
When there is supplementary information to display for
an entry in a selection list, display the information
in grey italics
|
Recommended |
| MSP-1920 |
Prioritise the items displayed in a selection
list by separating them into sections
|
Recommended |
| MSP-1930 |
Limit the options available in the first section
of a selection list (and in automatically presented
cascading lists) to relevant values
|
Recommended |
| MSP-1940 |
Where there are further choices than are displayed
by default in a prioritised list, provide access to
further options with an additional section of the list
|
Recommended |
| MSP-1950 |
When a more detailed view is available for
defining the values in a prioritised list
(such as one for editing individual
administration times), include a single
list item for accessing that view at the
end of the selection list
|
Recommended |
| MSP-1960 |
Where relevant, use supplementary text in a drop-down
list of options if the selection will affect other
options in the form
|
Recommended |
| MSP-1970 |
Where data is available, update the contents of a
selection list based on selections made in related fields
|
Mandatory |
| MSP-1980 |
When displaying list items that are not valid in
relation to values selected in other fields, list
them in a separate section in the selection list
|
Recommended |
| MSP-1990 |
When a list item is selected that is not valid in
relation to values selected in other fields (and
data is available to support this) clear the other fields
|
Mandatory |
| MSP-2000 |
As far as possible, present input controls for
fields that are inter-dependent close to one another
|
Recommended |
| MSP-2010 |
In a system that cannot validate entered values (because
decision support checking is not available), when a
selection list is reopened and a different value selected,
clear entries in all input controls that are interdependent
|
Recommended |
| MSP-2020 |
Support pre-filling of fields (or sets of fields) when they
are first displayed and ensure that the pre-filled values are
based on at least the drug name and route (or attributes from
which the type of medication can be derived)
|
Mandatory |
| MSP-2030 |
Allow the contents of all fields to be reselected such that a
pre-filled value, previous choice or text entry can be changed
(even if the associated selection list has only one option)
|
Recommended |
| MSP-2040 |
When a value is selected in a field, pre-fill appropriate
fields that have defaults (or only one possible value) based
on the selected value (for example, pre-fill administration
times when a frequency is selected)
|
Recommended |
| MSP-2050 |
Use formatting (such as highlighting) to draw attention to a
field whose contents have changed automatically rather than
directly by the user
|
Mandatory |
| MSP-2060 |
Pre-fill administration times and time of first dose (or
equivalent for once only and as required medications) when
frequency has been selected
|
Recommended |
| MSP-2070 |
When a dose field (or equivalent) is displayed, also display
a label for the dose (either within or outside of the input control)
|
Mandatory |
| MSP-2080 |
If possible, do not allow the selection of a unit of measurement
for a dose that would result in an invalid value when combined
with the number entered for the dose amount
|
Recommended |
| MSP-2090 |
When a strength field is displayed, also display a label for
the strength field or a group label including the word
'strength'
|
Mandatory |
| MSP-2100 |
Do not present strength and dose input controls next to each
other (side by side) in a detailed prescription form
|
Mandatory |
| MSP-2110 |
When displaying a list of administration times,
display the dose for the first scheduled
administration in bold
|
Mandatory |
| MSP-2120 |
Do not display a horizontal (text-only) list of
administration times for schedules containing more
than six administration events in 24 hours
|
Recommended |
| MSP-2130 |
Provide a selection list containing predefined
sets of administration times
|
Recommended |
| MSP-2140 |
Do not display input controls for entering or editing
individual administration times within the view that
shows all the required fields for a prescription
|
Mandatory |
| MSP-2150 |
For all prescriptions, require a date and time to be defined (or pre-filled)
for: the first dose (for regular medications), the starting date and time (for
as required medications), the only dose (for once only medications)
|
Recommended |
| MSP-2160 |
Use unique labels for the following fields: the first dose (for regular
medications), the starting date and time (for as required medications),
the only dose (for once only medications)
|
Recommended |
| MSP-2170 |
Do not provide a check box for fields with two opposite states when one of
those states causes a related field to be presented. (For example, do not
provide a check box to set 'as required' to on or off if a setting
of 'on' requires another field to be presented to qualify the
conditions for administration)
|
Recommended |
| MSP-2180 |
Provide a control for displaying a preview
|
Mandatory |
| MSP-2190 |
Include all values defined as part of the prescription in a preview
|
Mandatory |
| MSP-2200 |
Adhere to guidance in
Design Guidance – Medication Line
for the display of drug details in a preview
|
Mandatory |
| MSP-2210 |
Do not introduce a preview as a compulsory step before a
detailed prescription form has been opened
|
Recommended |
| MSP-2220 |
Require a preview to be presented before a prescription
can be authorised when the prescription details are
distributed over more than one screen such that a
navigation control (such as a button or tab) is needed
to move between screens
|
Mandatory |
| MSP-2230 |
Do not display the medication line within a preview as
a long line of text extending for longer than 120
characters without wrapping onto a new line
|
Recommended |
| MSP-2240 |
Where relevant, display some prescription attributes
in a preview using a format similar to that used in
other medications views (though different to the format
used for the input control)
|
Recommended |
| MSP-2250 |
Provide a control for closing the preview and
returning to the prescription form (such that
the prescription can be amended)
|
Mandatory |
| MSP-2260 |
Set default focus to the control that closes the preview
|
Mandatory |
| MSP-2270 |
Place the preview button before the authorise button
and reflect this in the tabbing order
|
Mandatory |
| MSP-2280 |
Provide a button for authorising the prescription
and label it 'Authorise'
|
Mandatory |
| MSP-2290 |
Place the Authorise button at the bottom right of the
prescription form such that it may be out of view if
the form is long enough to need a scroll bar
|
Mandatory |
| MSP-2300 |
Do not set the focus to the Authorise button by default
|
Mandatory |
| MSP-2310 |
Disable the Authorise button until all required
fields have been completed
|
Mandatory |