A Facial Recognition Mobile App for Patient Safety and Biometric Identification: Design, Development, and Validation
Bibliographic record
Abstract
BACKGROUND: Patient verification by unique identification is an important procedure in health care settings. Risks to patient safety occur throughout health care settings by failure to correctly identify patients, resulting in the incorrect patient, incorrect site procedure, incorrect medication, and other errors. To avoid medical malpractice, radio-frequency identification (RFID), fingerprint scanners, iris scanners, and other technologies have been implemented in care settings. The drawbacks of these technologies include the possibility to lose the RFID bracelet, infection transmission, and impracticality when the patient is unconscious. OBJECTIVE: The purpose of this study was to develop a mobile health app for patient identification to overcome the limitations of current patient identification alternatives. The development of this app is expected to provide an easy-to-use alternative method for patient identification. METHODS: We have developed a facial recognition mobile app for improved patient verification. As an evaluation purpose, a total of 62 pediatric patients, including both outpatient and inpatient, were registered for the facial recognition test and tracked throughout the facilities for patient verification purpose. RESULTS: The app was developed to contain 5 main parts: registration, medical records, examinations, prescriptions, and appointments. Among 62 patients, 30 were outpatients visiting plastic surgery department and 32 were inpatients reserved for surgery. Whether patients were under anesthesia or unconscious, facial recognition verified all patients with 99% accuracy even after a surgery. CONCLUSIONS: It is possible to correctly identify both outpatients and inpatients and also reduce the unnecessary cost of patient verification by using the mobile facial recognition app with great accuracy. Our mobile app can provide valuable aid to patient verification, including when the patient is unconscious, as an alternative identification method.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".