Noah Alert Dashboard
The Noah Alert Dashboard provides a visual software tool that makes it easy for Hearing Care Professionals (HCP's) to be made aware that there is important patient-related information. Noah provides many features used to convey the historical information for a patient but typically only when the patient record is selected in Noah by the HCP. The Noah Action Alert Dashboard provides an overview of information for all patients that are contained within a hearing care business's (HCB) Noah installation.
Title | User Story | Notes |
|---|---|---|
Entry is made into Alerts Dashboard by Manufacturer Back End System | A Manufacturer Back End System has the ability to provide data to a Noah installation that indicates to Noah that an entry is made into the Noah Action Alerts Dashboard. Precondition: Noah mobile has been enabled and the manufacturer's application (e.g. a manufacturer's back office system) has been approved by the HCB to exchange data with the HCB's Noah installation. | Q: Are Noah users able to create an entry in the alerts dashboard using a dashboard GUI feature? A: No. Q: Is it possible for a HIMSA member company to provide data to Noah, attach the data to a patient record but not have it be referenced in the alerts dashboard? A: Yes, in this case the data is represented in the Noah session browser. |
Manufacturer entry into the Noah Alert Dashboard includes unique patient ID | The exchange of patient data is done so with patient GUID's. The patient GUID is used to make sure that correct patient records are exchanged. Rationale: Very important to ensure that patient data is not being mixed up. | See Patient Record Matching for more details |
Manufacturer provides appropriate category | Manufacturer systems providing an action alert to Noah applies the most applicable category that is defined by Noah. Rationale: Categories are used to help HCP’s quickly and easily determine what type of action alert is being displayed. | See Remote Activity Categories Only one category can be applied to a single entry that will be shown in the Alerts Dashboard. Q: What should member company software do when multiple categories can apply to a given entry in the alerts dashboard? A: The member company will need to pick the more appropriate single category. At present the defined categories are related to remote hearing instrument related fittings. In the future it is possible that different groups of categories could be defined for different uses (e.g. IOI-HA questionnaires) |
Manufacturer provides additional text | Manufacturer software systems can provide additional text to further describe the action alert. Rationale: The text is displayed in a selected dashboard entry to provide additional summary data | Q: How much text can be provided? A: There is no limit except what Noah defines as the Action public data maximum, currently set to 3 MB) |
Application link | A Manufacturer provides linking information for each action alert entry. The linking information contains one or two links only. Rationale: Noah uses this information to request the appropriate application to be opened so that the HCP may review more information or utilize features provided by that application. | The linking information can result in opening:
The manufacturer makes the decision if they wish to support choices 1,2, or 3. |
Provide Noah with icon for use in Action Alert Dashboard | Manufacturers are able to provide Noah with an icon of the manufacturer's choice to be used in the Noah Action Alerts Dashboard. The manufacturers are able to provide and later update this icon. Rationale: Supports ease of use. | |
Provide Noah Action Alert Grouping information | As an option, the manufacturer back end system may provide Noah grouping information that associates with a Noah Action Alert. Rationale: This grouping information can be used to later visually enhance any Noah actions visible in the Noah Session Browser that are related to the Noah Action Alert. | |
Review Noah Action Alert entries even if the patient record is in use elsewhere. | HCP’s will be able to read all data available in a dashboard entry even if the patient record is open on another computing system where the Noah installation is sharing a common database. Rationale: HCP’s will find it frustrating to review alert information but cannot because the patient record is currently selected on another computer workstation. | Q: How will Noah react if the following conditions are present:
A: The HCP is still able to view the information in the Action Alert. However, if the patient is already opened on another workstation, they will not be able to open the module via the button in the dashboard or from the embedded session browser. |
If requested module is not installed on the computer workstation | If a manufacturer back end provides an application link that results in Noah asking a module to be opened, then it is technically possible that the module is not installed. By default, Noah reacts by showing a list of installed modules that are registered with Noah as supporting the data type associated with the action/activity. In the case of opening a module from the Noah alert dashboard, this would be Dashboard Notification data type (code = 303). See example 1 to the right. If there are no installed modules understanding this data type, then Noah provides an error message. See example 2. Q: Module developers sometimes need to retire old software and create a new module to show data created by the old module. Does Noah provide support for this situation? A: Yes, the Noah 4 module API provides for the ability to include a Module Alias with the installation of the new module. When the alias is in place, Noah will then use the new module by default. See ModuleAlias Object for more details. | Example 1, missing module with list of Modules that can read the data Type In this example, an audiogram action was activated from the Noah session browser; this action was created by an audiometer manufacturer. In this case the companies module is not installed. Noah has presented the below screen listing the modules that can read Audiograms. The user may now select a module to open the action.  Example 2, No installed modules Similar to example 1, in this case there are no audiogram modules installed. |