Audiogram Metadata Released
Introduction
Aug 2, 2019
HIMSA is pleased to announce the formal publication of the Audiogram Metadata data standard. This data standard is provided to allow the storage of additional information about audiometric data. As for the first release the data storage covers:
Predicted Accuracies via AMTAS Qualind ™
Non-standardized audiogram accuracy
Audiogram Classification via AMCLASS ™
Non-standardized audiogram classification
HIMSA is open to further inclusion of similar data if needed.
Q: Is this data standard the same as the Audiogram data standard?
A: No, HIMSA has created a new data standard and data type called "Audiogram Metadata".
Q: Why is this Metadata being stored separately vs. just including the data as revision of the current audiogram data standard?
A: HIMSA has taken this approach for the following reasons:
The audiogram data standard is already very large and fairly complex and it would seem wise to try to contain changes of this standard to actual test data.
Whenever a new format revision is published, HIMSA must create and distribute a run-time data converter to ensure that existing software can still function with newer formatted data. In the specific case of the audiogram standard, this process presents some extra special challenges that HIMSA would rather avoid if possible.
Most Importantly! This plan will result in the quickest and easiest deployment. HIMSA can more easily introduce the standard into Noah versions 4.8 and newer without needing to update Noah.
Availability in Noah 4
Noah version 4.13 and newer will automatically include support for the Audiogram Metadata data standard. HIMSA does provide a simple to run utility that can be used to update Noah version 4.8 and newer so that it is possible to use the metadata standard.
Q: How will Noah compatible measurement systems then store this data into Noah and how will it impact the view as seen by the HCP?
A: Measurement systems saving data using the audiogram metadata standard will simply save an additional action to Noah. The metadata will then be referenced (as can be seen by the dashed lines to the right) to make it easy in the future for other applications to match up the metadata to the correct audiogram.
Additional information to the diagram
The session July 1 is used to demonstrate how audiogram data will be stored without any metadata - how things are done today. In this case the session list will show an audiogram and other actions (e.g. Immittance)
The session August 1 is to show how it would look with the inclusion of an Audiogram Metadata action.
The session September 1 is used to show the same as August but the application developer has indicated to Noah that the metadata action is to be hidden from view. The data is still present but just represented in the GUI.
Whether a Noah action is visible or not in the session list is completely up to the application developer.
Q: Are there licensing issues that impact the AMCLASS and AMTAS data?
A: HIMSA has made an official agreement with Audiology Incorporated that specifies that there are no license issues with HIMSA providing means for data to be stored in Noah using a publicly defined data standard. Further there are no issues with any application readings and making use of this data (e.g. in the hearing instrument fitting process or by including the data in hearing reports). Companies wishing to store this data must contact Audiology Incorporated for business requirements. HIMSA will not become involved with business relationships between Audiology Incorporated and another HIMSA member company.
Data Details
How to read data maps
Please take a few minutes to understand what is meant by different graphical representations
Description | |
|---|---|
 | A box with a dashed line represents a data element that is optional to be saved. |
 | A box with a solid line represents a data element that is mandatory. Please note that if a parent (always shown to the left of the data element) is optional then the diagram can be read as "The parent is optional, but if the parent element/data is stored, then the child elements marked with a solid line are mandatory. |
Represents a choice. The data that is stored will only be one of the elements shown to the right | |
Represents a sequence. The data to the right represents further structured details. |
Automated Audiograms
True means that the measurement was collected via an automated fashion. The measurement system defines if the test was automated. This standard does not consider if the measurement was 100% or partially automated.
Data Element | Type | Notes |
|---|---|---|
AutomatedMeasurement | True/False | Setting to True provides a clear indication that the audiometric data contained was gathered by an automated process. |
Predicted Accuracies
As an option, predicted inaccuracy of an audiogram can be represented in 2 ways
Qualind ™ / the predicted accuracy can be recorded as fixed values of Good, Fair, or Poor as defined by Qualind.
As an option, a free form text entry can be stored in the Disagree element indicating that the professional did not agree with Qualind.
In a non-standardized listing, this is a simple free form text field. It does not follow a standardized approach.
It is possible to store one or many predicted accuracies.
Audiogram Classification
As an option, the classification of an audiogram can be represented in 2 days.
AMCLASS ™ / Complete details listed below
In a non-standardized subjective listing, this is a simple free form text field. It does not follow a standardized approach.
It is possible to store one or many predicted accuracies.
Symmetry
Data Element | Type |
|---|---|
Symmetry | Fixed Choices of:
|
For the Left and Right Ear the following storage will be supported
Data Element | Type |
|---|---|
SiteOfLesion | Fixed Choices of:
|
ConfigurationSeverityChoice | See details below. |
Configuration Severity Choice Details
Data Element | Type |
|---|---|
NormalHearing | "NA" "N/A" is present to denote that there is no legitimate entry for Normal Hearing |
FlastHearingLoss |
|
SlopingHearingLoss |
|
RisingHearingLoss |
|
TroughShapedHearingLoss |
|
PeakedHearingLoss |
|
Other |
|