...
This feature comparison is created for companies interested in creating an integration between a business system and Noah.
Feature | Noah 4 Full Business System API (OAS) | WSI API | Noah Mobile Service App (SAI) | Noah ES Service App | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
General Description | 
|
|
|
|
| 
| ||||||||||||||||||||||||||||||||||
Level of supported data, What kinds of data can the application exchange with Noah | All Patient demographic and Noah Action data | All Patient demographic data. Limited to public formatted data for most popular data
|
| All Patient demographic and Noah Action data | All Patient demographic and Noah Action data | |||||||
Type of API | .Net 4 | SOAP | REST | REST | |||||
Market Availability | Worldwide | Worldwide | Worldwide (Data relay services based out of Europe or USA) | Currently United States and Europe (EAA) | |||||
Data Resisdency for Noah Patient and Action Data | Controlled by the Business System Developer | Within control of the HCB, usually on-premise or LAN/WAN by HCB other service provider | Within control of the HCB, usually on-premise or LAN/WAN by HCB other service provider. Data only passes through the Azure data center as a relay. No data is stored. | Europe businesses are contained within Europe. USA business contained within US | |||||
Requires always available Internet | No | No | Yes Precondition: the Noah Server within the business must be on and connected to exchange data. There are no offline support featues. | Yes | |||||
Noah runtime license requirement
| Noah Site License | Noah Site License | Noah Site License | Included in per Noah ES subscription which is based on user accounts. Each hearing care professional is required to have a user account. | |||||
Scaleability - of Noah | only limited to what the BS can handle | 40 Concurrent Workstations, supported and tested workload | 40 Concurrent Workstations, supported and tested workload | Unlimited (using increased MS Azure based services) | |||||
Location/Office/Group Segmentation Support
| Possible if supported by business system | No | No | Yes | |||||
GUI Integration with Noah | Tight, Noah resulable GUI components can be visually incorporated | Separate | Separate | Separate, BS logo incorporated with Noah ES Client software | |||||
Noah Client application for module compatility / New Noah Client Version Impact
| This API is strongly bound to a specific version of the Noah Client (Engine) (e.g. 4.12). The business system adoption of new versions is withing the business systems sole control Noah Client updates doe usually entail additional work for the business system developer, often for features that are not enjoyed by the business system directly. | Noah Client version controlled by the verison of Noah System that is used. New releases of Noah do not generally have any impacted on the business system unless they wish to make use of a new feature. New version of Noah System 4 do need to be deployed or installed in each office and on each PC. Networked installations of Noah System must have the server and client on the same version of Noah 4. | Noah Client version controlled by the verison of Noah System that is used. New releases of Noah do not generally have any impacted on the business system unless they wish to make use of a new feature. New version of Noah System 4 do need to be deployed or installed in each office and on each PC. Networked installations of Noah System must have the server and client on the same version of Noah 4. | The Noah Client has been modified and called the “Noah ES Client” New major releases of the Noah ES Client are mainly made for GUI features. The Noah ES Client can have many types of updates made automatically without interaction from users or IT staff. When a new Noah Client full version is released each PC eventually needs to be updated but not all at the same time and usually within 6 months timeframe. Changes to the Noah ES Client do not impact the API used by Apps in any way. | |||||
Identity and Authentication for Noah Users | Controlled and provided by the developer of the BS. | Noah System provided or Microsoft Active Directory (on-premise active directory) | Noah System provided or Microsoft Active Directory (on-premise active directory) | Noah ES provided, Azure Active Directory, OpenID Connect or SAML 2 (SAML 2 coming in the future) | |||||
API supported in Noah ES | No | No | No but the REST API is very similar | N/A | |||||
HIMSA Membership and Licensing Fees | Initial Fee 82,650 DKK Annual Fee 42,400 DKK No additional fees for sites or users | Initial Fee $27,040 USD Annual Fee $21,630 USD (unlimited sites) OR Initial Fee $1,080 Annual Fee $1,080 (includes 4 site licenses) Fee per Site $270 per year (invoiced $67.50/quarter) Discounted rates for 25 or more sites. | Initial Fee 165,600 DKK Annual Fee 132,600 DKK No additional fees for sites or users | Included with the following licenses:
No additional fees for sites or users |
Feature Specific
Feature | Noah 4 Full Business System API | WSI | Noah Mobile Service App | Noah ES UI or Service App - As Main Patient | |||||
|---|---|---|---|---|---|---|---|---|---|
Patient Management and Demographic Data | |||||||||
Read Patient Demographic Data | Yes, the data is in the business system database | Yes | Yes | Yes | |||||
Can Control Patient Management
| Yes | No | No | Yes | |||||
Patient record linking Ability for the business system to attach its ID to Noah patient ID | Does not apply | Yes | Yes | Yes | |||||
Action Data Access Creation and Management | |||||||||
Apps can Read and Write Action Public (format) Data | Yes | Yes
| Yes | Yes | |||||
Apps can Read and Write Action Private (format) Data | Yes | No | Yes | Yes | |||||
Noah ES Locations and Groups | |||||||||
Read Only Locations and Groups | If the business system supports | No feature in Noah System but could exist in the business system applicaiton | No feature in Noah System but could exist in the business system applicaiton | Yes, optional | |||||
Read and Manage (Create, Update, Delete) | If business system supports | Yes, optional | |||||||
Manage Locations and Groups will be disabled if Managed by Business System | If business system supports | Yes, optional | |||||||
Read and Manage (Create-Assign, Update, Delete) Locations/Groups patients are assinged to | If business system supports | Yes, optional | |||||||
Disable the Noah ES Client feature to manage patient assignment to Locations/Groups | If business system supports | Yes, optional | |||||||
Noah GUI Control | |||||||||
Business System Sets Noah ES Active Patient Record
| Yes | Yes | No | Yes | |||||
Noah Client Patient Selected Changes
| Yes - does not really apply as the business system always is in control of this aspect | No | No | Yes | |||||
App Can Ask for the Noah ES Client for Current Selected Patient | Yes - does not really apply as the business system always is in control of this aspect | No | No | Yes | |||||
Open / launch member modules and apps from Noah GUI | Yes | No | No | Yes | |||||
Event Messages | |||||||||
Notified of:
| Yes - does not really apply as the business system is always aware of these activites | Yes | Yes, actions only | Yes | |||||
Query Noah for data | Yes - does not really apply as the business system has all the data in the business system database | Yes, Patient and supported action data | Yes, both patient and action data | Yes, both patient and action data |