K122028 · Gn Otometrics · ETW · Oct 23, 2012 · Ear, Nose, Throat
Device Facts
Record ID
K122028
Device Name
AURICAL HIT
Applicant
Gn Otometrics
Product Code
ETW · Ear, Nose, Throat
Decision Date
Oct 23, 2012
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 874.3310
Device Class
Class 2
Indications for Use
The Aurical HIT Type 1082 is intended to be used by audiologists, technicians, and other professionals who perform hearing instrument testing. Used in conjunction with the OTOSuite software, the Type 1082 permits presentation of acoustic sounds and magnetic field stimuli in order to assess the audio processing and telecoil functionality of the hearing instrument.
Device Story
Aurical HIT Type 1082 is a hearing instrument test system; connects via USB to PC running OTOsuite software. Device features a test chamber with snap-on couplers for hearing instrument positioning; includes automatic battery pill recognition and reference microphone for reliable positioning. System presents acoustic sounds and magnetic field stimuli to assess audio processing and telecoil functionality. Used by audiologists and technicians in clinical settings to perform testing per ANSI/IEC protocols; also supports Probe Microphone Measurements (PMM) for pre-programming/pre-fitting without client presence. Output displayed via OTOsuite software; enables consistent evaluation of hearing instruments regardless of manufacturer. Benefits include standardized performance verification and efficient pre-fitting workflows.
Clinical Evidence
Bench testing only. Device tested against ANSI S3.22: 2003 and IEC 60118-7: 2005 standards. Electrical safety verified per IEC 61010-1; EMC verified per IEC 61326-1. Software validation and risk analysis performed.
Technological Characteristics
Hearing aid calibrator/analysis system. USB 2.0 connectivity; max power 2.5 W. Includes test chamber, snap-on couplers, and reference microphone. Software-controlled via OTOsuite. Standards: ANSI S3.22: 2003, IEC 60118-7: 2005, IEC 61010-1 (Safety), IEC 61326-1 (EMC).
Indications for Use
Indicated for use by audiologists, technicians, and professionals to assess audio processing and telecoil functionality of hearing instruments via acoustic and magnetic stimuli.
Regulatory Classification
Identification
A hearing aid calibrator and analysis system is an electronic reference device intended to calibrate and assess the electroacoustic frequency and sound intensity characteristics emanating from a hearing aid, master hearing aid, group hearing aid or group auditory trainer. The device consists of an acoustic complex of known cavity volume, a sound level meter, a microphone, oscillators, frequency counters, microphone amplifiers, a distoration analyzer, a chart recorder, and a hearing aid test box.
Special Controls
*Classification.* Class II (special controls). The device is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 874.9.
{0}------------------------------------------------
510(K) Summary, 510(k) K122028 Submitter: GN Otometrics A/S Hoerskaetten 9 Taastrup, DENMARK DK-2630 Registration number: 9612197 C/O GN Otometrics North America 50 Commerce Dr Ste 180 Schaumburg, IL 60173 (US) Phone: 847-534-2150 (US) Fax: 847-534-2153 Contact: Dan Sansonetti, Manager of Research and Development Date Prepared: October 16, 2012
**OCT**
2 3
2012
- Identification of the Device: 1. Proprietary-Trade Name: Aurical HIT Type 1082 Classification Name: Calibrator, hearing aid / earphone and analysis systems, Class II Common/Usual Name: Hearing aid calibrator
- 2. Product code: ETW
- Equivalent legally marketed devices: 510(K) Number K113831 PRIMUS HEARING 3. INSTRUMENT TEST UNIT, AUDITDATA A/S.
- Description of the Device: AURICAL HIT is designed for Hearing Instrument Testing and 4. Coupler-Based Fitting. AURICAL HIT connects via USB to a computer running the OTOsuite software. With the OTOsuite HIT Module one can perform traditional hearing instrument testing according to either the ANSI or IEC test protocols, and obtain a consistent picture of every hearing instrument, regardless of manufacturer or type. With the OTOsuite PMM Module one can perform Probe Microphone Measurements in a coupler for pre-programming and pre-fitting hearing instruments without the client being present. It is easy to position hearing instruments on snap-on couplers inside the AURICAL HIT test chamber and it is easy to access the hearing instruments in the test chamber during test without disturbing the test setup. The battery pill types are recognized automatically, and the reference microphone ensures reliable positioning in the test chamber.
- న. Indications for Use (intended use): The Aurical HIT Type 1082 is intended to be used by audiologists, technicians, and other professionals who perform hearing instrument testing. Used in ' conjunction with the OTOSuite software, the Type 1082 permits presentation of acoustic sounds and magnetic field stimuli in order to assess the audio processing and telecoil functionality of the hearing instrument.
- Safety and Effectiveness, comparison to predicate device. This device has the same indications 6. for use as the predicate device and employs similar technology to accomplish the same tasks.
- 7. Description of Testing: Testing consisted of non-clinical performance testing of the device against the applicable parameters specified in the following standards: ANSI S3.22: 2003, and IEC 60118-7:2005 The device passed UL Electrical Safety (IEC 61010-1) testing and EMC (IEC 61326-1) testing. Software validation and risk analysis was performed.
{1}------------------------------------------------
## Substantial Equivalence Chart 8.
1
. . ・・
| | Characteristic | Auditdata Primus K113831 | Aurical HIT Type 1082 |
|--|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Intended Use: | Hearing Aid Testing | Hearing Aid Testing |
| | Hearing-aid test-box characteristics: | | |
| | C/Tests | OSPL90 | OSPL90 & HFA-OSPL90 |
| | | Full on gain | Full on gain |
| | | Input/Output | Input/Output |
| | | Attack/Recovery time | Attack/Recovery time |
| | | Reference test gain | Reference test gain |
| | | Frequency response | Frequency response |
| | | Equivalent input noise | Equivalent input noise |
| | | Harmonic distortion | Harmonic distortion |
| | | Battery current drain | Battery current drain |
| | | TeleCoil | TeleCoil |
| | Test Level Range: | 50 - 90 dB SPL | 40 - 100 dB SPL |
| | Freq. Range | 125 Hz - 8 kHz | 125 - 10,000 Hz |
| | Standards met for Hearing | ANSI S3.22 | ANSI S3.22: 2003 |
| | Instrument Testing | IEC 60118-7 | IEC 60118-7: 2005 |
| | Electrical Safety | IEC 60601-1, Class 1, Type B | IEC 61010-1 |
| | EMC | IEC 60601-2 | IEC 61326-1 |
| | Power supply | USB, and external power supply<br>for elevated outputs | USB Max. 2.5 W |
| | Communication port | USB 2 | USB 2.0 |
| | PC minimum requirements | CPU Minimum 1.4 GHz processor<br>with 512 MB (1 GB recommended)<br>system RAM<br>Harddisk space 1 GB free harddisk<br>space for Primus<br>Operating system Windows XP<br>Professional SP2 (32-bit), Windows<br>Vista (32-bit) including: Vista Home<br>Basic, Vista Home Premium, Vista<br>Business, Vista Enterprise and Vista<br>Ultimate, Windows 7 (32-bit)<br>including Windows 7<br>Home Premium, Windows 7<br>Professional and Windows 7<br>Ultimate Graphics card 1024 x 768.<br>XVGA Connections CD drive and<br>USB 2.0 connection required | 1.5 GHz processor or higher (2 GHz<br>recommended) • 512 MB RAM (1 GB<br>recommended) for Windows XP, or 1<br>GB (1.5 GB recommended) for<br>Windows Vista and Windows 7 • 2.5<br>GB free disk space for installation of the<br>OTOsuite software. Additional disk<br>space is needed for installation of<br>prerequisites • Windows® XP (32 bit)<br>with SP3 or higher, or Windows Vista<br>(32 bit) with SP2, or Windows 7 (32 or<br>64 bit) • USB port for connecting<br>accessories, v. 1.1, or 2.0 • DVD or CD-<br>ROM drive • 32 bit color display,<br>1024x768 screen resolution • 32 MB<br>graphic memory • Windows-compatible<br>sound card • Supports NOAH 3.5,<br>NOAH 3.5 for ENTs, or higher, for<br>NOAH mode operation. |
{2}------------------------------------------------
## K122028
| Characteristic | Auditdata Primus K113831 | Aurical HIT Type 1082 |
|----------------|---------------------------------|------------------------------|
| Photo | Image: Auditdata Primus K113831 | Image: Aurical HIT Type 1082 |
- 9. Conclusion: The Aurical HIT Type 1082 meets applicable standards for hearing instrument testers: ANSI S3.22: 2003 and IEC 60118-7: 2005. Per the bench performance testing, software testing, and safety testing, we conclude that the Aurical HIT Type 1082 is as safe and effective as the predicate device, and has essentially the same indications for use, thus rendering it substantially equivalent to the predicate device.
{3}------------------------------------------------
Image /page/3/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a stylized eagle with three stripes forming its body and wing. The text "DEPARTMENT OF HEALTH & HUMAN SERVICES • USA" is arranged in a circular fashion around the eagle.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Room -WO66-G609 Silver Spring, MD 20993-0002
GN Otometrics A/S c/o Daniel Kamm. P.E. Regulatory Engineer, Submission Correspondent Kamm & Associates 8870 Ravello Ct. Naples, FL 34114
Re: K122028
Trade/Device Name: Aurical HIT Regulation Number: 21 CFR 874.3310 Regulation Name: Hearing aid calibrator and analysis system Regulatory Class: Class II Product Code: ETW Dated: September 11, 2012 Received: September 21, 2012
Dear Mr. Kamm:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
OCT 2 3 2012
{4}------------------------------------------------
Page 2 - Daniel Kamm. P.E.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807): labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please go to http://www.fda.gov/AboutFDA/CentersOffices/CDRH/CDRHQffices/ucm115809.htm for the Center for Devices and Radiological Health's (CDRH's) Office of Compliance. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/Resourcesfor You/Industry/default.htm.
Sincerely yours.
Edw. K. Underwood
Malvina B. Evdelman, M.D. Director Division of Ophthalmic, Neurological, and Ear, Nose and Throat Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{5}------------------------------------------------
K122028
## Indications for Use
510(k) Number (if known): K122028
Device Name: Aurical HIT Type 1082
Indications For Use:
The Aurical HIT Type 1082 is intended to be used by audiologists, technicians, and other professionals who perform hearing instrument testing. Used in conjunction with the OTOSuite software, the Type 1082 permits presentation of acoustic sounds and magnetic field stimuli in order to assess the audio processing and telecoil functionality of the hearing instrument.
Prescription Use X 801 Subpart D)
AND/OR
Over-The-Counter Use (21 CFR 807 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
Vassil Raich
(Division Sign-Off) Division of Ophthalmic, Neurological and Ear, Nose and Throat Devices
510(k) Number K122028
Page 1 of 1
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.