- Tags must be small enough to be embeddable within dentures while delivering full RFID function within standard denture materials.
- Embedded tags must be able to withstand regular exposure to oral bio-acids, as well as routine cleanings using standard dental cleaning products.
- All materials used in this application meet compliance with FDA bio-compatibility regulations.
Syrma Designs RFID Tag & Software for Denture ID
A global dental prosthetics maker envisioned a new method for identifying and tracking dentures, from the point of manufacture at the lab to end-use among residents at nursing homes and other care facilities. While 23 US states currently require some form of physical user identification on each denture, compliance has typically been deficient. The reason is that the added costs associated with engraving patient names on the dentures and a user’s typical reluctance to reveal themselves as a denture wearer. In nursing facilities, because most dentures lack user names, it’s often difficult to match individuals with their dentures after they’ve been routinely collected for cleaning and maintenance or misplaced. These facilities also face potential HIPAA medical confidentiality violations if a labeled denture is mishandled and user identity is exposed beyond facility personnel. With the high costs of custom-made dentures and their day-to-day necessity for the user, this common problem called out for an innovative technical remedy. Challenges The client looked at embedding miniature passive RFID tags into a denture, which could be wirelessly scanned, logged, and identified via a custom software app. They initially discussed this idea with us at a medical device tradeshow after learning of our past success with RFID tags, smaller and medical-grade tags combined with our own readers and software across multiple mobile tracking applications. Our product team then set about developing the necessary hardware and software to the customer’s specifications. Bringing the convenience of RFID technology to dentures meant tackling several unique requirements: