Page Comparison

Noah can display the manufacturer logo on the module button, on actions in the session browser created by the module, a description of the module in the module button mouse-over text etc. In order for this to work, some special resources need to be added to the project. A description how to do this can be found in appendix B of this guide Adding a Logo, Patient Manager font and colors, and the module description to the Application.

Q: Does HIMSA have any visual requirements for a logo?

A: No but it does have other resource requirements, please see Adding a Logo, Patient Manager font and colors, and the module description to the Application.

Additional features and things to keep in mind

After this, it is just a matter of adding the features that you want the module to support. Furthermore, many things might be a good idea to keep in mind.

A few examples will be mentioned briefly here:

• A print handler makes it possible for the module to deliver patient reports, generated by the module, onwards to Noah for the user to print. It is recommended that this feature is included in the modules

• Inter Module Communication (IMC) makes it possible for two modules to communicate with each other

• It is also best practice to make sure, that when the user uninstalls the module, the module will unregister itself from Noah.
  The preceding chapters will describe the module development process in more detail.