Noah ES API

The Noah ES API has been created so interested HIMSA member companies can integrate their applications directly to Noah ES accounts. If your company offers a Cloud-based product today or you are considering this direction, we hope that you will take a look at what the Noah ES API has to offer.

Q: If my Noah-compatible software uses the Noah 4 module API today, do I need to use the Noah ES API so that my customers can use my software with Noah ES?

A: No. Noah ES provides compatibility for Noah 4 modules via the Noah ES Client application. The Noah ES API can be used by applications, typically Cloud-based, to integrate directly to a specific Noah ES account controlled by a Hearing Care Business.

https://himsanoah.atlassian.net/wiki/spaces/AD/pages/568492193

Business System Integration Options

QA is currently on version 1.18. Noah ES Production US is using 1.17, EU is using 1.17

Current status = QA environment is working as expected.

What HIMSA Provides

A Noah ES account that will be based in our QA environment. This environment is based in Europe. U.S.-based developers will experience a little slower response time but not such that will cause issues. The HIMSA U.S. office often tests within the QA environment effectively. Using a virtual machine arranged by you and hosted in Europe is also another option.
Access to make use of HIMSA’s sample apps
Source code to the sample app Noah ES Development – HIMSA
Developers guide
Swagger UI (noah-es.com)

Requirement Noah ES Certification

All Noah ES Apps must obtain certification at least once per year and must be certified before they may be used in Noah ES production environments. Please see for further details.

How to Get Started

Request that a Noah ES account in QA be set up for your company. 1 Noah ES account per company. Make a request via the service desk application.
Setup your Noah ES account and your users by using the information available at http://noah-es.com
Make use of the HIMSA sample Apps with your Noah ES account to see how an App can work with the Noah ES API.
- The sample app is available as a web application at https://noahessampleapp.azurewebsites.net/. Version updated to 1.0.3
- The sample service app is available as a web application at https://noahessampleserviceapp.azurewebsites.net/
Utilize https://himsanoah.atlassian.net/wiki/spaces/AD/pages/3547168791/Examples+Using+Postman?atl_f=content-treefor examples of some of the most popular uses of the REST API
Provide HIMSA with your application registration information so that you can start developing your own App.

Important! The no cost Noah ES account that HIMSA provides for development and testings is only available within our QA environment. You are not allowed to use any real patient data within this Noah ES account.

HIMSA will never setup a hearing care business in QA but HIMSA is aware that some companies have internal clinics or access to patient data. HIMSA will not provide any terms of service nor compliance agreements (GDPR DPA or HIPAA BAA). If you need a Production account in the US or EU please contact HIMSA.

Coming in the near future

HIMSA does not have specific dates set but is working hard on the below features that will be coming soon.

Other Upcoming Changes

Recent Improvements

Noah ES Client and Activities. Features that will enable business systems to control which patient is active in the Noah ES client, along with other similar features. This set of features will be available with the release of Noah 4.15.