SourceFinch Verified · Professional & business licensing

Exposure Incident Notification Data 2025-2026

Open CKAN records from Exposure Incident Notification Data 2025-2026 via https://open.canada.ca: up to 1,000 rows with stable identifiers for change monitoring. Personal contact columns are excluded.

Monitor this sourceAPI, CLI, SDK and MCP

What changedNo changes in 7 days

At a glance

Jurisdiction
Canada
Publisher updates
Updated by the publisher when the CKAN dataset changes
Recommended schedule
Daily for your monitor; SourceFinch verifies the recipe daily
Records per run
121 in the latest run
Record key
id
Acquired from
Open data portal: https://open.canada.ca/data/en/api/3/action/datastore_search?resource_id=42ebcc57-a886-42a4-a796-ff0e1d4739d9&limit=1000
Recipe
v1.0.0, approved November 17, 2026
Version notes
First Verified version generated 2026-11-17 from batch backlog.
Verified since
November 17, 2026
Last green run
November 17, 2026
Changes, last 7 days
0 · see what changed

What the data contains

Dataset “Exposure, non-exposure and other reporting data from licensed facilities in Canada” published on https://open.canada.ca (resource 42ebcc57-a886-42a4-a796-ff0e1d4739d9). Each daily run reads up to 1,000 rows through the portal's keyless JSON API (datastore_search). A monitor reports new and changed rows inside the cohort. SourceFinch is independent of the publisher.

Fields and types

Every record has these fields. The key field id identifies a record across runs, so changes are reported field by field.

FieldTypeDescription
idkeystringPublisher field `_id`. The record key.
Animal_related_bites_scratchesstring, nullablePublisher field `Animal_related_bites_scratches`.
Biological_agent_involvedstring, nullablePublisher field `Biological_agent_involved`.
Biological_agents_knownstring, nullablePublisher field `Biological_agents_known`.
Categorystring, nullablePublisher field `Category`.
Containment_levelstring, nullablePublisher field `Containment_level`.
Date_report_submittedstring, nullablePublisher field `Date_report_submitted`.
Equipment_relatedstring, nullablePublisher field `Equipment_related`.
Exposure_due_tostring, nullablePublisher field `Exposure_due_to`.
Exposure_incident_typestring, nullablePublisher field `Exposure_incident_type`.
Insect_relatedstring, nullablePublisher field `Insect_related`.

Sample output

The first 5 of 121 records from SourceFinch's own run on November 17, 2026, exactly as delivered.

FieldRecord 1Record 2Record 3Record 4Record 5
id12345
Animal_related_bites_scratchesNoNoNoNoNo
Biological_agent_involvedBrucella melitensisShigella sonnei—Cryptococcus gattiiEscherichia coli O157:H7
Biological_agents_knownYesYesNoYesYes
CategoryMandatory reportMandatory reportVoluntary reportMandatory reportMandatory report
Containment_levelContainment Level 2Containment Level 2Containment Level 2Containment Level 2Containment Level 2
Date_report_submitted2025-04-022025-04-022025-04-032025-04-252025-04-14
Equipment_relatedNoNoNoNoNo
Exposure_due_toInadvertent productionOtherOtherInadvertent possessionOther
Exposure_incident_typeExposureExposureExposureExposureLaboratory Acquired Infection - Suspected
Insect_relatedNoNoNoNoNo
Sample as JSON
[
  {
    "id": 1,
    "Category": "Mandatory report",
    "Insect_related": "No",
    "Exposure_due_to": "Inadvertent production",
    "Containment_level": "Containment Level 2",
    "Equipment_related": "No",
    "Date_report_submitted": "2025-04-02",
    "Exposure_incident_type": "Exposure",
    "Biological_agents_known": "Yes",
    "Biological_agent_involved": "Brucella melitensis",
    "Animal_related_bites_scratches": "No"
  },
  {
    "id": 2,
    "Category": "Mandatory report",
    "Insect_related": "No",
    "Exposure_due_to": "Other",
    "Containment_level": "Containment Level 2",
    "Equipment_related": "No",
    "Date_report_submitted": "2025-04-02",
    "Exposure_incident_type": "Exposure",
    "Biological_agents_known": "Yes",
    "Biological_agent_involved": "Shigella sonnei",
    "Animal_related_bites_scratches": "No"
  },
  {
    "id": 3,
    "Category": "Voluntary report",
    "Insect_related": "No",
    "Exposure_due_to": "Other",
    "Containment_level": "Containment Level 2",
    "Equipment_related": "No",
    "Date_report_submitted": "2025-04-03",
    "Exposure_incident_type": "Exposure",
    "Biological_agents_known": "No",
    "Biological_agent_involved": null,
    "Animal_related_bites_scratches": "No"
  },
  {
    "id": 4,
    "Category": "Mandatory report",
    "Insect_related": "No",
    "Exposure_due_to": "Inadvertent possession",
    "Containment_level": "Containment Level 2",
    "Equipment_related": "No",
    "Date_report_submitted": "2025-04-25",
    "Exposure_incident_type": "Exposure",
    "Biological_agents_known": "Yes",
    "Biological_agent_involved": "Cryptococcus gattii",
    "Animal_related_bites_scratches": "No"
  },
  {
    "id": 5,
    "Category": "Mandatory report",
    "Insect_related": "No",
    "Exposure_due_to": "Other",
    "Containment_level": "Containment Level 2",
    "Equipment_related": "No",
    "Date_report_submitted": "2025-04-14",
    "Exposure_incident_type": "Laboratory Acquired Infection - Suspected",
    "Biological_agents_known": "Yes",
    "Biological_agent_involved": "Escherichia coli O157:H7",
    "Animal_related_bites_scratches": "No"
  }
]

Evidence behind every value

  • Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash de2c3617ff185e37ee1abd752381a56de57484dddba212b6feed2560e0c25708.
  • Every value records where it came from in that response: a JSON Pointer into the retained capture.
  • Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is 396e8203f9efc2f189b17c4c8024c38f03891c8e21f9036312254c95f3d356b0, timestamped November 17, 2026.
  • The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
  • Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch: sourcefinch verify-bundle run.wacz.

Terms posture and usage rights

Terms
Automated access permitted · publisher's terms
robots.txt
Allows this path · SHA-256 4790aba35e5672c4…
AI-preference signals
None observed at review
Public record
Yes. CKAN dataset c2b10948-097d-4cbf-ab07-8581a77a95d5 on https://open.canada.ca.
Reviewed
November 17, 2026; next review May 17, 2027
Licence basis
Open data licence (OGL-Canada-2.0)
Commercial use
Allowed
Redistribution
Allowed
Attribution
Required (text below)

Published on https://open.canada.ca under open government terms. Anonymous JSON/CSV API access needs no key. Robots policy is checked at generation.

Government of Canada (https://open.canada.ca). SourceFinch is independent of the publisher.

Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.

Reliability

Runs, last 30 days
1
Green
100%
Failed
0
Median run time
0.8 s
Latest run
success, November 17, 2026

Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: November 17, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.

Use it

Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).

Console

Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.

Portable recipe

Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.

{
  "schema": "sourcefinch/source@1",
  "name": "Exposure Incident Notification Data 2025-2026",
  "url": "https://open.canada.ca/data/en/api/3/action/datastore_search?resource_id=42ebcc57-a886-42a4-a796-ff0e1d4739d9&limit=1000",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "result.records[*]",
    "fields": {
      "id": "_id",
      "Category": "Category",
      "Insect_related": "Insect_related",
      "Exposure_due_to": "Exposure_due_to",
      "Containment_level": "Containment_level",
      "Equipment_related": "Equipment_related",
      "Date_report_submitted": "Date_report_submitted",
      "Exposure_incident_type": "Exposure_incident_type",
      "Biological_agents_known": "Biological_agents_known",
      "Biological_agent_involved": "Biological_agent_involved",
      "Animal_related_bites_scratches": "Animal_related_bites_scratches"
    },
    "required": [
      "id"
    ]
  },
  "schedule": "daily",
  "key_field": "id"
}

source.json

The request body used by the API, CLI and SDK examples.

{
  "name": "Exposure Incident Notification Data 2025-2026",
  "url": "https://open.canada.ca/data/en/api/3/action/datastore_search?resource_id=42ebcc57-a886-42a4-a796-ff0e1d4739d9&limit=1000",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "result.records[*]",
    "fields": {
      "id": "_id",
      "Category": "Category",
      "Insect_related": "Insect_related",
      "Exposure_due_to": "Exposure_due_to",
      "Containment_level": "Containment_level",
      "Equipment_related": "Equipment_related",
      "Date_report_submitted": "Date_report_submitted",
      "Exposure_incident_type": "Exposure_incident_type",
      "Biological_agents_known": "Biological_agents_known",
      "Biological_agent_involved": "Biological_agent_involved",
      "Animal_related_bites_scratches": "Animal_related_bites_scratches"
    },
    "required": [
      "id"
    ]
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "ckan-open-canada-exposure-incident-notification-data-2025-2026",
    "version_id": "10402be7-089d-40f9-8c23-6ca8659a4098"
  }
}

REST API

Create an API key under Console → API keys. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/ckan-open-canada-exposure-incident-notification-data-2025-2026 -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

CLI

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get ckan-open-canada-exposure-incident-notification-data-2025-2026 --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

TypeScript SDK

The SDK is not on npm yet; see /docs/sdk.

import { SourceFinch } from "@sourcefinch/sdk";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("ckan-open-canada-exposure-incident-notification-data-2025-2026");
const source = await sf.sources.create({
  catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

MCP

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Exposure Incident Notification Data 2025-2026: get_catalog_source ckan-open-canada-exposure-incident-notification-data-2025-2026,
then create_source with its create_source_args (dry run first), then run_source."

Pricing

Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.

More from Government of Canada and in professional & business licensing.

SourceFinch is independent and is not affiliated with or endorsed by Government of Canada. This page describes exposure incident notification data 2025-2026 as SourceFinch acquires it.