The Noah Alert Dashboard is a graphical feature used by Hearing Care Professionals (HCP's) to help manage patient care situations that have deemed to be of greater importance, a topic that would require the HCP to act in some way.
The Noah Alert Dashboard is not an API. However, the only way for data to be fed into the Dashboard is by HIMSA member companies making use of a combination of the:
The main purpose of this collection of documents is to provide an introduction and summary of the application of the above APIs as they pertain to the Noah Alert Dashboard.
The Noah Alert Dashboard was first released with Noah 4.12
Scope and Responsibilities
This represents an HCP working in their office using Noah as they normally do today.
After selecting a patient record to work with, the HCP selects the appropriate fitting module. This is existing functionality.
The manufacturer is responsible for creating the fitting module. Each manufacturer has its own fitting modules.
The patient is at home (or other remote location) and is using the hearing instruments and App that is also created and controlled by a specific manufacturer.
You will notice that the diagrams are shaded in blue. The use of color is to make it clear what company is responsible for the development and control of the application software or device.
The manufacturer has created an App that will install on the patient's personal computing device, assumed to be a Phone or tablet.
The communication between the device and hearing instrument is assumed to be facilitated via BLE but could in theory be accomplished in other ways. The important point here is that the manufacturer is in control of deciding and controlling the method.
This icon is used to represent the general idea of a web conference. Typical features that exist are:
The presentation and the underlying conference service is provided by each manufacturer. This also means that the feature, if supported, will need to be included in both the applications used by the HCP and the patient.
For the purposes of this document, the icon is shown next to the fitting module. This implies that the web conference functionality could be directly embedded into the fitting module or could also be in another application controlled by the manufacturer.
The same applies to the conference service provided to the patient on the App. It is assumed that the manufacturer would wish to embed the communication into the app itself but is the choice of the manufacturer.
This is a summary of the explanations so far, showing the applications created and controlled by manufacturer ABC
The only main item that has not yet been discussed is the “Manufacturer Back End”. This icon is used to represent a system (e.g. Cloud, enterprise back end system) or collection of systems either owned or purchased by the individual manufacturer. The back end could be used to:
Help facilitate the web conference features between the HCP and the patient
Help facilitate the communication to the App and/or hearing instruments
Hold data temporarily or permanently.
In other words, the icon is used to represent that some coordination of facilities may be needed and that these facilities are provided (or arranged) by the manufacturer.
HIMSA is not pursuing any of these features.
Other manufacturers, such as Manufacturer XYZ, also control their own systems and are shown in orange in the diagram to stress this point.