Share this
DNAF Lessons Learned When Creating Rapid DNA Booking Stations
by Tracey Berkowitz on Apr 15, 2026 5:29:35 PM
From blood testing in the 1920s to DNA profiling in the 1980s, forensic science has undergone significant advancements. Today, Rapid DNA technology can generate a profile in under 90 minutes—revolutionizing how booking stations across the U.S. process arrestees.
But with speed comes new complexity. As Rapid DNA testing becomes more widely adopted in booking stations across the U.S., forensic labs are facing new operational challenges—especially around tracking arrestee data and ensuring seamless integration with DNA databases. For agencies preparing to implement Rapid DNA, understanding what works (and what doesn’t) is key to success.
In this short video clip from a recent InVita webinar, Mark Smith, Supervising Forensic Scientist at the Arizona Department of Public Safety, shares valuable lessons learned during the design and deployment of Arizona’s Rapid DNA Booking Station system. His insights offer a practical roadmap for jurisdictions navigating similar implementations.
How Arizona Launched Rapid DNA Without Waiting for Grants
Arizona was the first state agency in the country to implement a Rapid DNA program for law enforcement. Amazingly, they accomplished this feat without a dedicated funding stream. Instead of waiting for formal grants, the team leveraged existing lab budgets and one-time legislative funds to cover the costs of hardware, instruments, and integration. This flexible approach allowed them to move forward without waiting for formal grants—though final deployment is pending an Attorney General’s opinion.
Keeping Arrestee Data Secure Without Overcomplicating Access
One of the most critical planning decisions Arizona made was how to securely manage personally identifiable information (PII) without creating unnecessary barriers. To avoid transferring sensitive data to instruments or external systems, the team chose not to generate an Arrestee Enrollment File (AEF). Instead, all PII remains on a secure, access-restricted data exchange server—eliminating the need for background checks on instrument engineers and reducing risk.
Designing a Network That Simplifies Connectivity Across Agencies
Networking architecture played a significant role in the design of Arizona's Rapid DNA system. Arizona opted to place the CODIS Rapid Enrollment (CRE) server and application at the state level, simplifying connectivity and avoiding agency-specific firewall complications. This centralized setup allows the data exchange server to communicate directly with the CRE server, streamlining operations and reducing IT overhead.
Simplifying Sample Intake with Barcode-Enabled Collectors
To enhance Rapid DNA sample tracking, the team redesigned their BODE collector to include a barcode. This allows the sample to be registered at the time of collection at the booking station and later scanned into the STACS Database upon receipt—creating a seamless link between the sample and the individual. This improvement in Rapid DNA sample tracking ensures a reliable chain of custody from the booking station to the forensic lab.
Lessons Learned from Testing Multiple Rapid DNA Instruments
For CODIS to accept a data profile submission from a booking station, the law enforcement agency must have the following:
- Automated fingerprint capture
- Criminal history integration
- Qualifying offense integration
Per the FBI, there are only 2 approved Rapid DNA devices:
- ANDE 6C Series G
- Thermo Fisher's RapidHit™ ID DNA Booking System
However, different Rapid DNA instruments presented unique challenges.
- The ANDE system includes either a barcode or an RFID tag on the swab
- The Thermo Fisher system includes a barcode on the outer packaging and an RFID tag on the ACE cartridge
Even after taking all of this into account, Arizona was still experiencing issues with the Thermo Fisher device due to the barcode being on a shiny foil packet, which made it difficult to scan.
Solving Scanning Challenges Through Collaboration with Louisiana
Since the Rapid DNA Act of 2017 was signed into law, several state agencies, including those in Arizona, California, Florida, Louisiana, and Texas, as well as the FBI, have worked to implement pilot programs that help shape booking station standards.
When Arizona encountered scanning issues with Thermo Fisher’s Rapid DNA device, they turned to these states for support. Louisiana had developed a custom RFID scanner and generously shared its design and programming. Using this blueprint, Arizona built in-house scanners for both live scan stations and Rapid DNA instruments, allowing staff to simply hover the cartridge over the reader to register the RFID chip in the system automatically.
Closing the Gap in DNA Sample Processing
As more booking stations adopt Rapid DNA testing, labs must be ready to manage the influx of data and samples efficiently. Manual entry of arrestee demographics and sample swabs into laboratory databases is time-consuming and prone to errors, creating bottlenecks that disrupt daily workflows.
InVita’s Rapid DNA Booking Station integration solution, developed in partnership with the Arizona Department of Public Safety, automates the transfer of critical data—including arrestee demographics, fingerprints, SIDs, and DNA profiles - from booking station to lab. It also ensures seamless management of samples that fail to generate a DNA profile, giving analysts valuable time back and reducing the risk of manual errors.
With CODIS access on the horizon, now is the time for labs to future-proof their workflows. InVita’s integration bridges the operational gap in Rapid DNA sample processing—delivering greater accuracy, efficiency, and transparency across the criminal justice system.
- DNA, Forensics (3)
- Hit Tracking (3)
- Sexual Assault Kit Tracking (3)
- CODIS Hits (2)
- CODIS Hit Outcome Tracking (1)
- FSHOT: Forensic Hit Outcome Tracking System (1)
- Forensic Hit Outcomes (1)
- Forensic Science Hit Outcome Tracking (1)
- SAK Tracking (1)
- Sexual Assault Awareness Month (SAAM) (1)
- Track-Kit SAK Tracking System (1)
