@proseid v1.0.0 US

OSHA fatality or severe-injury reporting determination

Determines whether a workplace outcome falls into the federal OSHA immediate-reporting track and records the facts, report status, and deadline outcome.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v1.0.0
Applies in: United States
Fields: 19
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

osha_severe_incident_reporting_20152015-01-01 → continues indefinitely

Current

Controlling sources

Legal references

Occupational Safety and Health Standards 29 CFR § 1904.39

Source ↗

Schema fields

19 fields

Field

Type

Description

Req

Report submitted to OSHA

Boolean

—

Opt

Submitted within the applicable 8- or 24-hour deadline

Boolean

—

Opt

Federal immediate-reporting exception

Select

Choices: None, Public Road Motor Vehicle Accident Outside Construction Zone, Commercial Or Public Transportation System, Uncertain Requires Review

Req

Federal OSHA reporting rules apply

Boolean

—

Req

Employer contact and phone

String

—

Req

Employer

String

—

Req

Affected workers

Number

—

Req

Brief incident description

String

—

Req

Federal reporting track

String

—

Opt

Time of the work-related incident

String

—

Opt

Date of the reportable outcome

Date

—

Req

Date of the work-related incident

Date

—

Req

The outcome occurred within its trigger window

Boolean

—

Req

The event was work-related

Boolean

—

Req

Names of workers with a reportable outcome

String

—

Opt

Most serious reportable outcome

Select

Choices: Fatality, Inpatient Hospitalization, Amputation, Loss Of Eye, Other

Req

OSHA-report submission date, time, and zone

String

—

Opt

Worksite location

String

—

Req

When the employer learned of the reportable outcome

String

—

Opt

Example payload

JSON

{
  "responses": {
    "osha_report_submitted": false,
    "submitted_within_deadline": false,
    "federal_reporting_exception": "",
    "federal_osha_applies": false,
    "contact_name_and_phone": "",
    "employer_name": "",
    "affected_workers_count": null,
    "incident_summary": "",
    "incident_time": "",
    "outcome_at": "",
    "incident_at": "",
    "outcome_within_trigger_window": false,
    "work_related": false,
    "affected_worker_names": "",
    "outcome": "",
    "osha_report_submitted_at": "",
    "worksite_location": "",
    "employer_learned_of_outcome_at": ""
  },
  "effective_at": "2026-07-23"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL

curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json

200 OK

{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}

422 Invalid

{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "osha_report_submitted",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}

A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions

Loading published versions…

Trust ledger

Crowd → credentialed

Provenance

Community publisher (unverified)

@proseid · latest v1.0.0

Community signal

0 votes

No votes yet.

Attestations · by version

0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments

to join the discussion.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

EU right-of-withdrawal record

SEC material cybersecurity incident disclosure record

California CCPA consumer-request lifecycle

HIPAA breach-notification determination