With Noah Modules the established process has been in place for the entire history of the HIMSA certification program. The general premise is that certification process is highly encouraged but not mandatory under the terms of the integration license.
...
 | In this flow chart the member company wishes version 1.0 of the module to be certified and schedules a date for HIMSA to perform the testing. Before the software is submitted to HIMSA the member conducts conformance testing which stresses the software for the proper integration with Noah. During this process the member company will record the completion of each test step. The completion of the test steps can be performed by a human or automated tester. The member company will next submit a signed test report, test steps completed and software to HIMSA. HIMSA will then perform the test steps that HIMSA is responsible for. Generally, these test steps focus on the important integration points as well as ensure that the software does not impact other certified software in negative/critical manner. If the HIMSA testing is completed successfully the module will be granted certification. HIMSA will publicly list the module as certified and also make the module available to other HIMSA member companies should they wish to obtain a copy for testing and troubleshooting purposes. If the test is not completed successfully or the member company simply wishes to have HIMSA perform a preliminary test the certification will not be granted. |
Special case for critical issues found on business system test sites
As part of a module integration test the modules will be installed and tested for basic functionality on each of the certified business systems currently available. If a critical issue is discovered HIMSA will notify the member company as to the problem. HIMSA will still grant certification in these cases and inform the member company of the issue. The member company will then make their own determination if they wish to continue with the release.
...
A: In the past, business system suppliers performed their own integration testing (twice per year). It was later agreed that it would be better for HIMSA to perform the integration testing in house and also to test modules on each business system at time of integration testing to ascertain any issues. Having HIMSA perform this test gives manufacturers a warning to possible problems. Previously, manufacturers would release a module and then a few months later find out about issues.
Certification of Patches
A member company may occasionally find an issue that needs to be addressed after a software product has been certified and released. Member companies are able to submit a patch for certification if all of the below conditions are met. Certification of a patch is more desirable as testing time and cost is significantly lower.
...
A: Yes, the patched version will be listed as a new certification entry.
Scheduling and Turnaround Time for Patch Tests
Since patch testing requires much less testing time on behalf of HIMSA advanced scheduling is not necessary, although very much appreciated. When the conditions listed above have been met please submit the software and documentation to HIMSA. HIMSA will conclude with the results of the test as quickly as possible. HIMSA will conclude testing within 5 business days.
Editing and Adding Content
It is possible to allow NOAH certified software to update or provide dynamic content without needing to be processed through the HIMSA certification process fully. Content is defined as any type of file that is static and does not control or influence the execution of code. It is envisioned that updated content will be provided online but it is possible for the content to be distributed in any matter (e.g. via a CD update). Below are provided a list of example types of content files:
...