This guideline describes how the module is expected to function in specific situations.
General Points
- There must be consistency, for example as regards the manner in which icons, symbols, abbreviations, button text and shortcut keys are placed and used. There should be compliance with Windows standards and the ‘Noah 4 Standalone Features and User Interface Requirement Specification’ document (on the HIMSA website – www.himsa.com), wherever possible.
2. Running a module should not have an adverse effect on other programs.
3. To make modules Noah 4 compliant, they should be able to save data while still remaining open. HIMSA recommends the implementation of a Save toolbar button in addition to a Save command in the File control menu.
4. The module should be able to handle internal program errors and user errors in such a way that these are detected and communicated to the user in an informative and understandable way. When at all possible, the user should also be informed of the necessary course of action to solve the error.