Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Current »

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

 General description

This API is HIMSA’s original business system integration option that entails that the Noah System GUI front end is replaced by a GUI provided by the business system developer.

Additionally, the database storage, user authentication and networking capabilities are provided by the business system

See Developers Guide for more details

 General description

This API is a purely data exchange API. This means the users will work with the Noah System 4 GUI and the business system GUI Separately

See General Overview for more details, also pushing and pulling data

 General description

This API is a purely data exchange API. This means the users will work with the Noah System 4 GUI and the business system GUI Separately

Noah mobile provides a secure data relay between the Service App and the patient database that resides within a Noah System 4 installation. This installation typically being on-premise within the hearing care business office.

The relay provides easy access without needing to setup access through firewalls.

See Developers Guide for more details

 General description

This API is also mostly a data exchange API where the business system can request data from Noah ES as well as ad data to Noah ES

Noah ES is a cloud based service hosted by HIMSA.

As of February 2022 the API is currently in development and will be published for comments as soon as possible.

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

 Further details

Limited to Audiometric, Immittance,Real ear measurement, Hearing instrument test,Hearing instrument and remote selection,fitting (just date of fitting)

Currently only available in format 500

Additional data made available with Noah 4.15: Announcement Noah WSI - Additional Data Support Conformance level 4 and higher

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

 More details

What the Noah licensing requirements for each office location or per user or PC

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

 More details

The ability to assign patients to office locations or other logical groups and then manage what users have access to those patients within the group.

Possible if supported by business system

No

No

Yes

GUI Integration with Noah

Tight, Noah reusable 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

 More details

The most widely used API used with Noah 4 is the Noah 4 module API. Hearing instrument, measurement equipment manufacturers create windows desktop application that integrate with Noah.

This API relies heavily on a Noah Client to be present for both data exchange and GUI

When new GUI features are created or new API method are made available an updated version of the Noah Client is made available as well and does impact the business API’s in different ways

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 within 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 version 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 version 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 time frame.

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:

  • Noah 4 Full Business System API

  • WSI - only with unlimited site plan

  • Noah Mobile Service App

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

 Click here to expand...

Can the system determine if other apps can create patients, control other applications access to data

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

 Limited to

Audiometric, Immittance, Real ear measurement, Hearing instrument test,Hearing instrument and remote selection,fitting (just date of fitting)

Currently only available in format 500

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 application

No feature in Noah System but could exist in the business system application

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

 Details

When a business system is used and a HCP is working with a patient it would be normal for the HCP to first be reviewing the patient information in the business system and then proceed into the Noah ES client for measurements and fittings.

In this case it would be very helpful if the business system is able to ask the Noah ES client to open and to then be set with the correct patient record, with no user interaction

Yes

Yes

No

Yes

Noah Client Patient Selected Changes

 Details

If the patient record changes or is set then a message will be made available for Apps letting them know what patient record is now selected.

Rationale: A requested feature from at least business system developers. They would like the ability to cooridnate having the same patient selected in their application for ease of HCP workflow.

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:

  • Patients added

  • Actions added/edited

Yes - does not really apply as the business system is always aware of these activities

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

  • No labels