HIMSA Certification
The WSI contract that your company signed with HIMSA does not stipulate that your solution pass HIMSA's certification procedure but it is highly recommended. The certification procedure is designed to better ensure that your solution will act as you intend it to. Passing the procedure also provides your company to state that your system is certified by HIMSA, something that many hearing care professionals have come to place a great deal of faith in.
Please see https://www.himsa.com/members-2/certification-materials/web-services-integration-certificaiton-material for more details
Noah System
 | The WSI API requires that the hearing care business use Noah System. It is possible that they are currently using another Noah compatible business system. If they are currently using another Noah compatible business system, the business will need to convert from the full business system integration to Noah System. For these instances, it is best that they speak with their current supplier for the best way to move to Noah System. See https://www.himsa.com/products/noah-compatible-products/noah-compatible-management-systems/ for a complete list of systems. The "Type" column will list "business" or "WSI" |
Site License
Noah System is licensed on a site basis. In basic terms this means that each physical office location needs a separate Noah System license. Please see https://www.himsa.com/support/noah-4-knowledge-base/preparing/types-of-noah-4-licenses/noah-4-end-user-license/ for more details. If a business needs to purchase more licenses they can do so via any of HIMSA's distributors, see https://www.himsa.com/about-himsa/where-to-find-a-distributor/ for a complete list. As a HIMSA member company, you may also become a distributor as well, please contact your HIMSA representative for more information. The site license enables offices to install Noah on as many computers as they wish for that 1 physical office.
Please note the site license concept also applies to the WSI license fees
WSI License Fees
This section is provided as a quick summary. Please refer to your HIMSA contract for full details
The license structure comes in two different main options:
Unlimited number of sites for a fixed yearly fee
Variable pricing that is determined on the number of sites using your implementation of WSI. HIMSA will ask you each quarter how many sites have utilized WSI during any part of the quarter and then send your company an invoice.
Q: Does HIMSA make special considerations for free site licenses for beta and release testing?
A: No.
Noah System Support
Your company is not obliged to provide support services for Noah System (e.g. installation, upgrade, network troubleshooting). In this case the company that sold them Noah System is responsible. HIMSA does not provide support directly to businesses but rather provides 2nd level support to the company that is providing support.
Your company is responsible for providing support to WSI integration as the first level support engineers will have no idea how this works. HIMSA is prepared to provide 2nd level support to your support engineers.
If you wish to provide support for Noah System as a service you are of course welcome to. Before doing so please have your technical staff complete the HIMSA support certification program which is online and provided at no cost to your company. Please see https://www.himsa.com/distributor/distributor-support-resources/online-support-training-for-distributors/ for more details.
Introduction to Audiology
Many developers and technical support staff have had little direct experience with audiology before. For this reason, HIMSA's Amanda O'Donnell, a U.S. licensed Audiologist, has put together a set of courses to provide an overview of audiology for these new employees.
The training material is not designed for audiologists but rather individuals who need a quick but thorough introduction to audiology.
This is also a free online course.
Getting your system setup
Typically, it is desired that the hearing care office have their Noah System installation networked, meaning that all workstations in the office are using the same shared database. If this is not done it may complicate your setup. Not all offices have a shared database.
Next steps are:
Install the WSI installation on the Noah Server in the office (please see SDK for further details). During this process, several configuration choices will be made. You will need to consult with your development team on what has been implemented.
Install your companies WSI runtime license
Perform testing
The WSI runtime license is a license tied to your companies account. The same license installation program is used on each of your customer's installation. The runtime license file is good for 1 year and HIMSA will create a new file to you each Spring. It is your company's responsibility to distribute this new license file. However, if the Noah System server is connected to the internet the installation will attempt to perform this function.
Who to contact if you have questions or needs help with an installation setup
WSI support is handled by our web based support system.
***Note: If you are seeing a message stating the EndPoint cannot be found, these directions should fix this issue too.
Launch the NoahBSIntegServerTool.exe. This tool can be found in the following location C:\Program Files (x86)\HIMSA\Noah 4. Once the NoahBSInegServerTool utility is open select Window>Configuration>Web Service Settings. Change the backEndWebServiceName to the new server name, an IP address can be used too. Restart the machine for these new settings to take effect.
***Note: This will not fix whatever caused the patient record to be flagged by WSI and sent to the Conflict Resolution Screen. This will only make it so the Conflict Resolution Screen does not pop up every time Noah 4 System is opened.
If you are unable to update or create a new patient within the Conflict Resolution screen and you just want the screen to go away, there are two ways to clear out the Conflict Resolution screen.
a.) If you only have a handful of patient records caught in the Conflict Resolution screen follow these directions. Launch the NoahBSIntegServerTool.exe. This tool can be found in the following location C:\Program Files (x86)\HIMSA\Noah 4. Once the NoahBSInegServerTool utility is open select Window>Inbox. Then select the “Get data” button. Finally select the “Set Flag” button
b.) If you have many patients listed in the Conflict Resolution Screen please follow these directions. Stop the Noah 4 System window services and rename the WSI database. The WSI database is located in program data\Himsa\NoahBS and is called NOAHBSIntegServerDatabase.sdf. Rename it to something like oldNOAHBSIntegServerDatabase.sdf. Restart the Noah services and the WSI database will be recreated. Next rerun the WSI installation. Select “Repair” when prompted by the WSI installer. Once the WSI installer has finished repairing your WSI, reboot the machine for the new settings to take effect.
a.) One of the most common reasons format 500 data cannot validate against the xsd file is the namespaces are wrong.
b.) Create a full backup of the Noah System 4.x database using the backup database tool in the Noah Console.
c.) Delete all Patient Record from within the Noah 4 System GUI.
d.) Import the .nhax format file you created in step one back into Noah System 4.x.
***Note: The Noah System 4 export utility will remove all the BESPIDS by design. Then the deleting of the patient records from within Noah System 4 allows for all Users IDs and preferences to be saved. The final result will be patient records that contain no BESPIDS and all user settings will still be in Noah.