The Hailie™ sensor is intended for single-patient use in the home environment as a medication reminder and electronic data capture accessory for recording actuations of prescribed inhaler usage. This may be used in the following applications: - In clinical trials, where researchers need to know when a patient has actuated their trial inhaler medication. - In clinical practice, where specialists, general practitioners, nurses, and educators need to know if a patient has actuated their prescribed inhaler medication. - In self-management, where patients need to track their medication use as part of their management plan. The Hailie™ sensor is compatible only with Bevespi Aerosphere® and is for use by adults. The Hailie™ sensor is not intended to indicate remaining quantity of medication in an inhaler and does not include a dose counting function.
Device Story
Hailie Sensor is a clip-on accessory for Bevespi Aerosphere inhalers; uses optical and mechanical sensors to detect inhaler presence and actuation; logs date/time of use via internal clock; features Bluetooth for data transmission to mobile apps; includes LED indicators and buttons for user interaction/reminders; used by patients for self-management or by clinicians/researchers to monitor adherence; provides usage history to support clinical decision-making; benefits patients by improving medication compliance.
Clinical Evidence
No clinical data. Substantial equivalence established via non-clinical testing, including biocompatibility (ISO 10993), electrical safety (IEC 60601-1), EMC (IEC 60601-1-2), software verification/validation, and summative usability testing.
Technological Characteristics
Clip-on inhaler accessory; optical and mechanical sensors for actuation detection; microprocessor-controlled; Bluetooth wireless connectivity; internal non-rechargeable battery; biocompatible materials per ISO 10993; compliant with IEC 60601-1 and IEC 60601-1-11 standards.
Indications for Use
Indicated for adults using Bevespi Aerosphere® inhalers for medication adherence tracking and reminders in home, clinical, or research settings.
Regulatory Classification
Identification
A nebulizer is a device intended to spray liquids in aerosol form into gases that are delivered directly to the patient for breathing. Heated, ultrasonic, gas, venturi, and refillable nebulizers are included in this generic type of device.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left, there is a symbol representing the Department of Health & Human Services - USA. To the right of this symbol, there is a blue square with the letters 'FDA' in white. Next to the blue square, the words 'U.S. FOOD & DRUG' are written in blue, with 'ADMINISTRATION' written in a smaller font size below it.
December 10, 2018
Adherium (NZ) Ltd Chris Mander Head of Regulatory & Ouality Level 2, 204 Quay Street Auckland, 1010 NZ
Re: K181405
Trade/Device Name: Hailie Sensor Regulation Number: 21 CFR 868.5630 Regulation Name: Nebulizer Regulatory Class: Class II Product Code: CAF Dated: October 31, 2018 Received: November 9, 2018
## Dear Chris Mander:
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. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. 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.
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
{1}------------------------------------------------
801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/CombinationProducts/GuidanceRegulatoryInformation/ucm597488.htm); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 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 comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/) and CDRH Learn
(http://www.fda.gov/Training/CDRHLearn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (http://www.fda.gov/DICE) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
# James J. Lee -S
for Tina Kiang, Ph.D. Acting Director Division of Anesthesiology. General Hospital, Respiratory, Infection Control, and Dental Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
#### DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration
## Indications for Use
510(k) Number (if known) K181405
Device Name Hailie™ Sensor
Indications for Use (Describe)
The Hailie™ sensor is intended for single-patient use in the home environment as a medication reminder and electronic data capture accessory for recording actuations of prescribed inhaler usage. This may be used in the following applications:
- In clinical trials, where researchers need to know when a patient has actuated their trial inhaler medication.
• In clinical practice, where specialists, general practitioners, nurses, and educators need to know if a patient has actuated their prescribed inhaler medication.
• In self-management, where patients need to track their medication use as part of their management plan.
The Hailie™ sensor is compatible only with Bevespi Aerosphere® and is for use by adults. The Hailie™ sensor is not intended to indicate remaining quantity of medication in an inhaler and does not include a dose counting function.
Type of Use (Select one or both, as applicable)
Prescription Use (Part 21 CFR 801 Subpart D)
X Over-The-Counter Use (21 CFR 801 Subpart C)
#### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
Image /page/3/Picture/1 description: The image shows the logo for Adherium. The word "adherium" is written in lowercase letters in a coral color. To the right of the word is a graphic of two pills, one coral and one white, that are angled to the right.
Adherium (NZ) Limited Level 2, 204 Quay Street, Auckland 1010, New Zealand PO Box 106-612, Auckland 1143, New Zealand Phone +64 9 307 2771 contact@hailie.com www.hailie.com
31 October 2018
## 510(k) SUMMARY
This summary of 510(k) information is submitted in accordance with requirements of 21 CFR 807.92:
#### (a)(1) Submitter Information
| Company Details: | Adherium (NZ) Ltd |
|------------------|------------------------------------------------------|
| | Level 2, 204 Quay Street, Auckland 1010, New Zealand |
| | PO Box 106-612, Auckland 1143, New Zealand |
| | Phone +64 9 307 2771 |
| | Contact Person: |
#### (a)(2) Name of the Device
| Device Name: | Hailie™ Sensor |
|----------------------|------------------------------------------------------------------------------------------------|
| Model Number: | NF0096 |
| Classification Name: | Nebulizer (Direct Patient Interface)<br>Anesthesiology Devices, 21 CFR 868.5630, Class II, CAF |
#### (a)(3) Identification of Legally Marketed Devices
The predicate device to which substantial equivalence is: K173310, SmartTouch™, manufactured by Adherium (NZ) Limited. The reference device which supports a substantial equivalence determination is: K133951, SmartTouch™, manufactured by Nexus6 Limited.
#### (a)(4) Description of the Device
The Hailie™ sensor is used to provide a medication reminder and actuation recording function for use as an accessory to the inhaler specified on the device label. Under the current 510(k), the Hailie™ sensor is indicated for use only with the Bevespi Aerosphere®.
The Hailie™ sensor is a clip-on device that attaches externally around the housing of the inhaler. Optical and mechanical sensors are used to detect the presence and actuation of the inhaler. The Hailie™ sensor contains an electronic clock and calendar that are used to log the date and time of inhaler actuation.
The user interface consists of three control buttons and three LED indicators to check device status, initiate communications functions, and provide reminder features. The Hailie™ sensor has a Bluetooth interface to wirelessly exchange medication and reminder setting data with a paired communications device and compatible mobile software applications.
{4}------------------------------------------------
## (a)(5) Statement of the Intended Use
The Hailie™ sensor is intended for single-patient use in the home environment as a medication reminder and electronic data capture accessory for recording actuations of prescribed inhaler usage. This may be used in the following applications:
- In clinical trials, where researchers need to know when a patient has actuated their trial inhaler . medication;
- . In clinical practice, where specialists, general practitioners, nurses, and educators need to know if a patient has actuated their prescribed inhaler medication.
- In self-management, where patients need to track their medication use as part of their . management plan.
The Hailie™ sensor is compatible only with Bevespi Aerosphere® and is for use by adults. The Hailie™ sensor is not intended to indicate remaining quantity of medication in an inhaler and does not include a dose counting function.
## (a)(6) Technological Characteristics Summary
Technological characteristics of the Hailie™ sensor are equivalent to the predicate and reference devices listed above. They are all electronic devices that clip on to an inhaler, using a combination of optical and mechanical sensors to detect inhaler use which is logged to compile a usage history.
The Hailie™ sensor has equivalent technological characteristics to the predicate device in terms of:
- Clip-on attachment around the outside of an inhaler housing. .
- Microprocessor control and use of an internal clock to log date and time of inhaler actuation. .
- Provision of medication reminders. .
- User interface controls design. .
- Sensor technology used to detect inhaler presence. .
- No interference with inhaler mechanism or operation. .
- Event storage capacity and memory management. .
- Power supply from an internal non-rechargeable battery and shelf life / service life. .
- Bluetooth communications technology for data upload. .
- Interface to a communications device to upload inhaler usage data. .
- Capability to provide inhaler usage data for further analysis using remote review software. .
The Hailie™ sensor has equivalent technological characteristics to the reference device in terms of:
- Sensor technology used to detect inhaler actuation. •
The Hailie™ sensor has differing technological characteristics from the predicate device in terms of:
- . User interface controls and indicators layout.
- Housing shape, which was modified to fit the Bevespi Aerosphere® inhaler. .
- Use of a sensor to wake the device from transport mode.
- Some different materials and colorants are used.
These minor design changes were verified by non-clinical testing to establish equivalent performance to the predicate device.
## (b)(1) Discussion of the Non-Clinical Tests
Non-clinical testing of the Hailie™ sensor has been carried out to cover biocompatibility testing, electrical safety and electromagnetic compatibility, software verification and validation testing, performance testing, and usability evaluation.
{5}------------------------------------------------
### Biocompatibility Testing
The biocompatibility evaluation for the Hailie™ sensor was conducted in accordance with the FDA guidance Use of International Standard ISO 10993-1, "Biological evaluation of medical devices - Part 1: Evaluation and testing within a risk management process" (16 Jun 2016), to meet requirements from the following standards: ANSI/AAMI/ISO 10993-1:2009 (biocompatibility), ANSI/AAMI/ISO 10993-5:2009 (cytotoxicity), ANSI/AAMI/ISO 10993-10:2010 (sensitization and intracutaneous irritation), and ANSI/AAMI/ISO 10993-12:2012 (sample preparation for biocompatibility testing).
## Electrical Safety and Electromagnetic Compatibility (EMC)
Electrical safety and EMC testing were conducted by external laboratories on the Hailie™ sensor. The device complies with the following standards and regulations: ANSI/AAMI ES60601-1:2005 +A1:2012, C1:2009, A2:2010 (general safety), IEC 60601-1-11:2015 (home-use safety), IEC 60601-1-2:2014 (electromagnetic compatibility), and ANSI C63.10:2013 / 47 CFR Part 15 (FCC regulations for radiofrequency (RF) devices). Information was provided according to FDA guidance Information to Support a Claim of Electromagnetic Compatibility (EMC) of Electrically-Powered Medical Devices (11 Jul 2016), and Radio-Frequency Wireless Technology in Medical Devices (13 Aug 2013).
### Software Verification and Validation Testing
Software verification and validation testing were conducted to ensure correct functionality for the Hailie™ sensor software release. Documentation was provided as recommended by FDA guidance Content of Premarket Submissions for Software Contained in Medical Devices (11 May 2005), Off-The-Shelf Software Use in Medical Devices (9 Sep 1999), and Content of Premarket Submissions for Management of Cybersecurity in Medical Devices (2 Oct 2014).
### Performance Testing
Performance testing was conducted to establish correct functionality and compatibility of the Hailie™ sensor with the Bevespi Aerosphere® according to requirements, covering:
- Optical inhaler presence detection sensor performance testing. .
- Pressure inhaler actuation detection sensor performance testing. .
- Bluetooth data transfer communications performance testing.
- General performance testing (shelf life, Bluetooth range). .
#### Usability Evaluation
Summative usability validation testing was carried out to evaluate critical tasks indicated by the usability risk analysis process. A description of the usability engineering process and the results obtained from the testing were provided in accordance with the FDA guidance Applying Human Factors and Usability Engineering to Medical Devices (3 Feb 2016).
## (b)(2) Discussion of the Clinical Tests
Clinical testing was not required for a determination of substantial equivalence of the Hailie™ sensor. The product functionality has been adequately assessed by non-clinical testing as above.
#### (b)(3) Conclusions Drawn from Non-Clinical and Clinical Tests
Finished device testing carried out for the Hailie™ sensor indicates it meets design and performance functional requirements. Software verification demonstrates that device functions are substantially equivalent to the predicate device. The device meets standard requirements for biocompatibility, electrical safety, electromagnetic compatibility, and wireless communications. The usability evaluation demonstrated that the Hailie™ sensor can be used successfully with the compatible inhaler.
This information indicates that the Hailie™ sensor is substantially equivalent to the predicate device.
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
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.