health-supervision-decisions

name: health-supervision-decisions description: Query Health Board supervision and precept pages for regulatory decisions, enforcement actions, and public-health oversight context.

Health Supervision Decisions

Use when

• You need Health Board supervision/enforcement decision context.
• You need official precept/public oversight publications.

Avoid when

• You only need disease incidence trends.

Inputs

• Supervision topic, entity scope, and period.

Outputs

• Structured supervision-decision dataset and evidence links.

Primary endpoints

• Precepts page: https://www.terviseamet.ee/ettekirjutused
• Supervision page: https://www.terviseamet.ee/jarelevalve

Workflow

1. Retrieve relevant supervision/precept publication entries.
2. Extract decision date, subject, and enforcement details.
3. Normalize entity/topic categories.
4. Return structured output with legal-context notes.

Human setup (when needed)

• If decision details are document-based and not directly exportable, guide user through downloading/opening the files and continue from provided content.

Quality checks

• Keep decision date and reference IDs where available.
• Separate announcement text from enforceable decision details.

Access reality

• Public access type: UI page with direct downloadable files.
• Verification run: 2026-02-24.
• https://www.terviseamet.ee/ettekirjutused (HTTP 200, text/html;, file links detected: 27)
• https://www.terviseamet.ee/jarelevalve (HTTP 200, text/html;, file links detected: 38)

Request contract

• Use the listed primary endpoints as authoritative entry points.
• If API/query parameters are only visible in-browser, preserve exact request URL, params, and headers in output metadata.
• If endpoint is UI-only, document click path and extraction method used.

Output schema expectations

• Keep at least: source URL, retrieval timestamp, publication/update date (if available), title/record label, and extracted governance-relevant fields.
• Preserve original field names when present in downloadable/API output.

Limits and caveats

• Confirm whether data is open-download, UI-only, or authenticated before claiming full access.
• Separate narrative/guidance text from measurable records.

Verification hooks

• Validate endpoint reachability and content type before extraction.
• Validate that each extracted claim is linked to a concrete source URL.