Dinesafe Knowledge Base
  • Welcome
  • Return to DineSafe.com
  • Benchmarking
    • Introduction
      • The Importance of Food Safety
      • Introduction to Our Benchmarking System and Its Purpose
      • Why Food Safety Benchmarking Matters: A Stakeholder Overview
    • Methodology & Systems
      • The Metrics We Use
        • Reports per 100 Stores
        • Reports per $1M Revenue
        • Persons Reported Sick per 100k Customers Served
      • Data Sources & Methodology
        • How We Gather Data
        • Estimating Data When Exact Figures Aren't Available
        • Ensuring Accuracy and Transparency
      • Our Benchmark Indexing System
        • Why We Use Indexing
        • Index Composition
        • Index Calculation Process
        • Understanding Index Comparisons
    • Case Study
      • Case Study - Chipotle Mexican Grill
    • Applications
      • Global Applicability of Our Benchmarking System
      • Product-Specific Benchmarking for Food Producers
    • Service Information
      • Why Subscribe to Our Benchmarking Service
      • Limitations & Considerations
      • Conclusion
      • FAQ
        • Q1: How often are the benchmarks updated?
        • Q2: Are the food poisoning reports reviewed before being included in the benchmarks?
        • Q3: How do you account for differences in restaurant size when comparing benchmarks?
        • Q4: Can restaurants submit their own data to improve the accuracy of the benchmarks?
        • Q5: How do your benchmarks relate to official health inspections and ratings?
        • Q6: How can businesses improve their benchmark scores?
  • Data Dictionary
    • Introduction
    • Primary Fields
    • Specialized Fields
    • Delivery Methods
    • Glossary
    • Further Questions
  • IWP Reporting Widget
    • Introduction
    • Why Our Widget? Key Features & Benefits
    • Embedding the Widget
      • How to Embed the Code
      • When to Use Simple Embedding Code vs Advanced Embedding Code
        • Benefits of the Advanced Embedding Code
        • Considerations When Using the Advanced Embedding Code
      • Test the Code
      • Standalone URL Option
      • Customization Options
      • Language Support
      • Mobile-Friendly Link
    • Data Management and Access
    • Compliance with FDA’s Voluntary National Retail Food Regulatory Program Standards
    • Examples of Embedded Widgets
    • FAQ
      • Q1: Who can use the Iwaspoisoned.com reporting widget and what is it?
      • Q2: How do I embed the widget on my website?
      • Q3: Is the widget customizable?
      • Q4: How do I access the reports?
      • Q5: How does the widget support FDA compliance?
  • Email Notifications
    • Introduction
    • Widget Email Alerts
Powered by GitBook
On this page
  • Data Flow Overview
  • Accessing the Data

Was this helpful?

  1. IWP Reporting Widget

Data Management and Access

Data Flow Overview

Data collected via the widget is securely transmitted and stored in the Iwaspoisoned.com database. Here’s a brief overview of the process:

  1. Data Submission: Residents submit foodborne illness reports through the widget.

  2. Secure Storage: Data is stored in a secure database, with access restricted to authorized county personnel.

  3. Ring-Fenced Data: For data originated by your embedded form, access is automatically ring-fenced to your jurisdiction.

Accessing the Data

Your county can access and review the data through a secure portal provided by Iwaspoisoned.com. This portal allows you to:

  • View Reports: Access detailed reports submitted by residents.

  • Analyze Trends: Utilize built-in tools to identify trends and patterns in the data.

  • Export Data: Download data for further analysis or record-keeping.

PreviousMobile-Friendly LinkNextCompliance with FDA’s Voluntary National Retail Food Regulatory Program Standards

Last updated 7 months ago

Was this helpful?