Mandatory knowledge

Owned by Scott Peterson
Last updated: Jul 03, 2023 by Anders Damkjaer Nielsen
3 min read



In order to use the Web Service Integration it is necessary to accept that:

  • Patient data to Noah must always contain all data elements:

    If a data element is NOT included in the XML from the back-end system when it is imported to Noah then the data element in Noah will be blanked out

  • When transmitting an action from Noah it is the Public part of the action that is transmitted

  • When using the GetPicture functionality that is released with Noah 4.3 – it is important that the Noah Server installation has an Audiogram Chart installed – this can be done in 2 ways:

    - Installing the Noah 4 Audiogram Module on the server.

    - Using the WSI installer - The version of the WSI installer that matches the version of Noah System 4 you are using.

Basic Overview of WSI

The WSI components

All necessary components for WSI will come with a normal Noah 4 installation – but they will first be initiated or started up when you run the “WSI installer”.

  • For Noah 4.14 and prior versions, the installer is to be downloaded from Web Service Integration Website. Copy the folder to the hard drive and run the “NoahWSISetup.exe”.

  • For Noah 4.15+, the NoahWSISetup.exe is found in the Noah installation, at C:\Program Files (x86)\HIMSA\Noah 4

An alternate way of setting up the WSI simply to set everything in the Noah Business System Integration Tool (NoahBSIntegServerTool.exe) that can be located in the Noah 4 folder on the hard drive.

To use the WSI functionality, the licensee needs to implement a BEWS following the guidelines in this document. HIMSA has developed a sample BEWS that can be downloaded, tested reviewed, copied from the HIMSA site.

The WSI license file

When WSI functionality is enabled on a Noah Server – then it is important that the WSI license exe has been run on the Noah Server computer as well – otherwise the WSI will not work. A WSI license file is created by HIMSA specifically for each new WSI Licensee and sent to the Licensees HIMSA contact.

A new WSI license file must be obtained from the Licensee every calendar year.

The licensee will be responsible for distributing this special license file to each one of the end-user sites. This license file is separate from the normal Noah 4 runtime license file. The license file is not unique for each end-user license site but rather one license file is used by all end-user sites receiving services from your company.

Important WSI license file information

The license file will be valid for one calendar year and the Licensee must have an updater from HIMSA every year to ensure that customers can keep using WSI functionality. Since the WSI license is created with a time limit (calendar year) it is very sensitive in respect to the user changing time/dates on the PC.

An example: If the user sets the time forward to “date X” to test something and then afterwards sets the time back to current date – then the License system will sense that the time is set back and will CEASE TO WORK until after “date X”. There is nothing HIMSA can do about this and the ONLY SOLUTION is to re-image the server or wait until “date X”.

Configuration of the WSI

When using the WSI installer it is necessary to set up the configuration of the WSI as well – there are many parameters to set up and they are specified in the “Configurations” section of this document. The WSI installer will take the user through all the different options.

The configuration of WSI can be done via import/export of configuration files. Note that there is one configuration file for each group of functionality. If the configuration needs to change this can be done using the “Noah Business System Integration Tool” (Default location on Windows 7 (64 bit): c:\Program Files (x86)\HIMSA\Noah 4\NoahBSIntegServerTool.exe))

Automated vs. Manual WSI

The focus in the first versions of WSI has been on the automated workflow – but with Noah 4.3 the full manual workflow was also introduced.

Automated workflow: Every time a valid action is saved in Noah it will automatically be transmitted to the BEWS.

Manual workflow: When the user selects to transmit an action in Noah then the export is performed.

It is possible to combine manual and automated WSI – which can nice when testing the setup.