% E E # #HE PRACTICE
Open Access
BUILDING CAPACITY
Building Capacity With the Right Mobile Inspection Device
Darryl Booth, MBA
mon requirements from a 12-month library of RFPs are: 1. Mobile Inspection Capability: The software must allow inspectors to conduct inspec- tions using mobile devices in the field, enabling data entry and access on-site. 2. Oine Functionality: The software should function oine to ensure inspections can be performed without internet connectiv- ity, with data synchronization occurring once connectivity is restored. 3. Generating Ocial Reports: Users need the ability to generate ocial inspection reports and other documentation (e.g., notices, citations) in customizable formats. 4. Photo Upload Capability: Inspectors must be able to take and upload photos during inspections to document their findings eectively. 5. Digital Signature Capture: The software should allow inspectors to capture digital signatures on-site to validate inspection results and reports. 6. Automated Scheduling and Notifications: The software must include features for automated scheduling of inspections and sending notifications to both inspectors and partners about upcoming inspections and required actions. 7. GIS Integration: The software should integrate with GIS to manage and visual- ize inspection assignments by geographic region and facility type. 8. Compliance With Regulatory Standards: The software should support compliance with relevant regulatory standards, such as completing checklists with specific mark- ings (e.g., in, out, N/A, no). With these requirements, an agency might select a software solution and then work
Editor’s Note: A need exists within environmental health agencies to increase their capacity to perform in an environment of diminishing resources. With limited resources and increasing demands, we need to seek new approaches to the practice of environmental health. Acutely aware of these challenges, the Journal publishes the Building Capacity column to educate, reinforce, and build on successes within the profession using technology to improve eciency and extend the impact of environmental health agencies. This column is authored by technical advisors of the National Environmental Health Association (NEHA) Data and Technology Section, as well as guest authors. The conclusions of this column are those of the author(s) and do not necessarily represent the views of NEHA, nor does it imply endorsement of any product, service, or resource mentioned. Darryl Booth has been monitoring regulatory and data tracking needs of environmental public health agencies for over 20 years. He serves as a technical advisor for the NEHA Data and Technology Section. Booth is the general manager of environmental health at Accela.
M odern environmental health data systems are built on three intercon- nected players or users. The three legs of this stool are: 1. Oce sta: They process applications, manage work, and conduct financial transactions. 2. Public: Individuals from the public check inspection results, pay fees, or submit forms. 3. Inspectors: Environmental health profes- sionals record inspection activities while in the field. Each of the three players has their work processes. For example, office staff will likely use desktop computers, hopefully
with large monitors and fast network con- nections. These computers are almost always Windows devices. Public users may use any device, ranging from budget phones to high- end desktops. Finally, the work processes can vary drastically for inspectors who use tech- nology in the field. This column is a round-up of 2024 hard- ware available to our field inspectors.
Field Inspection Software Requirements
After scanning requests for proposals (RFPs) for the previous 12 months, the following requirements emerge as the most common. Without regard to agency size, the most com-
24
%olume • um(er
Powered by FlippingBook