Version 1
: Received: 31 March 2019 / Approved: 1 April 2019 / Online: 1 April 2019 (13:38:50 CEST)
Version 2
: Received: 12 May 2019 / Approved: 14 May 2019 / Online: 14 May 2019 (07:37:04 CEST)
How to cite:
Abrams, S. A Clinical Challenge & Solution: Detecting Cracks in Teeth Using PTR-LUM-The Canary System; A Case Report. Preprints2019, 2019040017. https://doi.org/10.20944/preprints201904.0017.v2
Abrams, S. A Clinical Challenge & Solution: Detecting Cracks in Teeth Using PTR-LUM-The Canary System; A Case Report. Preprints 2019, 2019040017. https://doi.org/10.20944/preprints201904.0017.v2
Abrams, S. A Clinical Challenge & Solution: Detecting Cracks in Teeth Using PTR-LUM-The Canary System; A Case Report. Preprints2019, 2019040017. https://doi.org/10.20944/preprints201904.0017.v2
APA Style
Abrams, S. (2019). A Clinical Challenge & Solution: Detecting Cracks in Teeth Using PTR-LUM-The Canary System; A Case Report. Preprints. https://doi.org/10.20944/preprints201904.0017.v2
Chicago/Turabian Style
Abrams, S. 2019 "A Clinical Challenge & Solution: Detecting Cracks in Teeth Using PTR-LUM-The Canary System; A Case Report" Preprints. https://doi.org/10.20944/preprints201904.0017.v2
Abstract
Detecting cracks in teeth is a clinical challenge. Patients may complain of diffuse pain on chewing, pain, at times, on temperature change and pain that occurs episodically. Common diagnostic tools such as radiographs and visual examination may not detect cracks. This case report shows how PTR-LUM in The Canary System can detect cracks in teeth not seen with other devices. In this clinical situation, the crack involved a portion of the mesial and distal surfaces of a mandibular second molar.
Keywords
marginal ridge staining; enamel crack; detecting cracks in teeth; PTR-LUM
Subject
Medicine and Pharmacology, Dentistry and Oral Surgery
Copyright:
This is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
