Reporting data issues

If a record looks wrong, report it. A person checks every report against the primary source and either corrects the data or explains why it stands. Reports are free on every plan.

curl -X POST https://api.healthcare.dev/v1/issues \
  -H "Authorization: Bearer $HDEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "dataset": "icd10cm",
    "record_id": "E11.22",
    "field": "display",
    "expected": "Type 2 diabetes mellitus with diabetic chronic kidney disease",
    "evidence_url": "https://www.cms.gov/medicare/coding-billing/icd-10-codes"
  }'

The response carries the report's id, its status (open, then fixed or rejected) and target_fix_by, when we aim to have fixed or answered it. Agents can file the same report with the MCP tool report_issue; the SDK has client.issues.report(...).

• Point evidence_url at a primary source (CMS, FDA, NLM, the payer's own page): it's the fastest way to a fix.
• Never include patient information. Reports that look like they contain it (Social Security numbers, dates of birth, record numbers) are refused with 400 invalid-request.
• An account can file 100 reports a day.

Open issues and fix timeCopy Anchor Link

GET /v1/issues/stats (no key needed) returns how many reports are open, how many were resolved in the last 90 days, their median fix time in hours, and our target.