The Noah 4 module development process is described, providing: an overview of the Noah 4 software architecture and the steps required to develop a Noah 4-compatible module a set of guidelines and additional information sources for each step in the development process There is no information on designing a module’s user interface or determining a module’s feature set. However, some style recommendations are listed in Style Recommendations. It is suggested that module developers design their module interface to be compatible with Microsoft Windows guidelines and with the Noah 4 software. For more information on the Noah 4 graphical user interface, refer to the ‘Noah 4 Features and User Interface Requirement Specification’ on the HIMSA website – www.himsa.com. IMPORTANT: The source code supplied is “pseudo” code for example purposes only – that is, the code will most likely not work if copied directly into the developer’s module. It is assumed that the developer has a solid general knowledge of the Microsoft .NET Framework 4.0 or later. None. GUI Graphical User Interface IMC Inter-module communication MS Microsoft OAS Office Automation System SB Session BrowserOverview
User Prerequisites
The module developer must also have a good understanding of how the user interface of the Noah 4 software functions.References
Abbreviations
General
Content
Integrations