@proseid v1.0.0 US

HIPAA breach-notification determination

Documents the threshold assessment for a suspected breach of unsecured protected health information and records the individual, HHS, media, or covered-entity notices that follow.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

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

Legal history

Time periods

hipaa_omnibus_breach_rule2013-09-23 → continues indefinitely

Current

Controlling sources

Legal references

HIPAA Breach Notification Rule 45 CFR §§ 164.400–414

Source ↗

Schema fields

22 fields

Field

Type

Description

Req

Largest number affected in one state or jurisdiction

Number

—

Opt

Breach affecting fewer than 500 logged for the annual HHS submission

Boolean

—

Opt

Under-500 breach reported to HHS within 60 days after the calendar year ended

Boolean

—

Opt

Applicable 60-day notices sent on time

Boolean

—

Opt

A documented four-factor assessment found a low probability of compromise

Boolean

—

Req

The applicable 60-day notice deadline has been reached

Boolean

—

Opt

Covered entity notified by the business associate

Boolean

—

Opt

Mitigation and steps individuals should take

String

—

Opt

Date the incident was discovered

Date

—

Req

Affected individuals notified

Boolean

—

Opt

Required media outlets notified

Boolean

—

Opt

Entity assessing the incident

String

—

Req

What happened

String

—

Opt

Notification track

String

—

Opt

HIPAA role

Select

Choices: Covered Entity, Business Associate

Req

Number of affected individuals

Number

—

Req

There was an impermissible use or disclosure of PHI

Boolean

—

Req

Contact procedures for questions or more information

String

—

Opt

Available affected-person and notice information supplied to the covered entity

Boolean

—

Opt

Types of PHI involved

String

—

Opt

The PHI was unsecured

Boolean

—

Req

HHS Secretary notified

Boolean

—

Opt

Example payload

JSON

{
  "responses": {
    "largest_state_or_jurisdiction_resident_count": null,
    "small_breach_logged_for_hhs": false,
    "small_breach_hhs_reported_by_annual_deadline": false,
    "applicable_60_day_notices_sent_on_time": false,
    "documented_low_probability": false,
    "applicable_60_day_deadline_reached": false,
    "covered_entity_notified": false,
    "mitigation_and_protection": "",
    "discovered_at": "",
    "individuals_notified": false,
    "media_notified": false,
    "entity_name": "",
    "breach_description": "",
    "entity_role": "",
    "affected_individuals": null,
    "impermissible_use_or_disclosure": false,
    "notice_contact_procedures": "",
    "available_individual_information_sent_to_covered_entity": false,
    "phi_types": "",
    "unsecured_phi": false,
    "hhs_notified": false
  },
  "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": "largest_state_or_jurisdiction_resident_count",
        "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

OSHA fatality or severe-injury reporting determination

SEC material cybersecurity incident disclosure record

California CCPA consumer-request lifecycle