SourceFinch Verified · Company registries

HHSC CCL Non-Compliance Data

Recent records from HHSC CCL Non-Compliance Data on data.texas.gov: up to 1,000 rows with stable identifiers for change monitoring. Contact columns are excluded.

Monitor this sourceAPI, CLI, SDK and MCP

What changedNo changes in 7 days

At a glance

Jurisdiction
data.texas.gov
Publisher updates
Updated by the publisher; typically daily or weekly
Recommended schedule
Daily for your monitor; SourceFinch verifies the recipe daily
Records per run
1,000 in the latest run
Record key
id
Acquired from
Open data portal: https://data.texas.gov/resource/tqgd-mf4x.json?$select=section_id,operation_id,activity_id,non_compliance_id,standard_number_description,standard_risk_level,corrected_at_inspection,corrected_date,date_correction_verified,narrative,technical_assistance_given&$limit=1000&$order=operation_id
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

Open data published on data.texas.gov as “HHSC CCL Non-Compliance Data”. Each daily run reads up to 1,000 rows through the portal's SODA API, naming only non-contact columns. A monitor reports new and changed rows inside the cohort. Leaving the cohort does not establish deletion. 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 `section_id`. The record key.
operation_idstring, nullablePublisher field `operation_id`.
activity_idstring, nullablePublisher field `activity_id`.
non_compliance_idstring, nullablePublisher field `non_compliance_id`.
standard_number_descriptionstring, nullablePublisher field `standard_number_description`.
standard_risk_levelstring, nullablePublisher field `standard_risk_level`.
corrected_at_inspectionstring, nullablePublisher field `corrected_at_inspection`.
corrected_datedatetime, nullablePublisher field `corrected_date`.
date_correction_verifieddatetime, nullablePublisher field `date_correction_verified`.
narrativestring, nullablePublisher field `narrative`.
technical_assistance_givenstring, nullablePublisher field `technical_assistance_given`.

Sample output

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

FieldRecord 1Record 2Record 3Record 4Record 5
id19554890231955489023195548902319555469541955489024
operation_id9408094080940809408094080
activity_id907784324907784324907784324907842836907784325
non_compliance_id10305037391030503738103050374010306504971030503744
standard_number_description749.2489(3) - Reports to Licensing-Agency submits information within 2 working days of putting foster home on inactive status or taking home off inactive status749.2539 - Verifications- May not make new placements of children into a home that is provisionally verified.749.2819(c) - Inactive Status-when a home is placed on or removed from inactive status, agency must inform licensing by submitting an agency home report form749.153(a)(1)(D) - Notification - At least 30 days in advance - Change in agency or branch office operating hours749.1335(1) - Service Plan Review and Update-To review and update a service plan, evaluate child's progress and effectiveness of strategies and techniques
standard_risk_levelMedium LowMediumMedium LowMedium LowMedium
corrected_at_inspectionNNNNN
corrected_date2022-08-10T00:00:00.0002022-08-10T00:00:00.0002022-08-10T00:00:00.0002025-03-04T00:00:00.0002024-06-04T00:00:00.000
date_correction_verified2022-08-16T00:00:00.0002022-08-16T00:00:00.0002022-08-16T00:00:00.0002025-02-25T00:00:00.0002024-06-28T00:00:00.000
narrativeThe home was placed on Inactive Status on 08/26/21 and as of 07/20/22 Licensing was not notified that the home was on active status and had placed an infant in the home.The home was placed on inactive status on 08/26/21 and began have preplacement visits of an infant on 2/12/22 then placing the child in the home on 3/10/22 with a plan for adoption in the home.The home was placed on Inactive Status on 08/26/21 and a report form was not submitted to licensing.Upon arriving at the facility for an unannounced inspection, licensing inspectors discovered that the operation was closed due to a staff meeting. It was determined that the operation had not communicated the alteration in operating hours to the licensing representative.A foster child's service plan review documented plans and goals for recreational and cultural activities, but not progress made toward these goals or descriptions of recreational and cultural activities already provided. The service plan is also missing documentation of vision and hearing screening services already provided to the foster child. Information about family visits is also not present in the service plan review.
technical_assistance_givenYESYESYESYESYES
Sample as JSON
[
  {
    "id": "1955489023",
    "narrative": "The home was placed on Inactive Status on 08/26/21 and as of 07/20/22 Licensing was not notified that the home was on active status and had placed an infant in the home.",
    "activity_id": "907784324",
    "operation_id": "94080",
    "corrected_date": "2022-08-10T00:00:00.000",
    "non_compliance_id": "1030503739",
    "standard_risk_level": "Medium Low",
    "corrected_at_inspection": "N",
    "date_correction_verified": "2022-08-16T00:00:00.000",
    "technical_assistance_given": "YES",
    "standard_number_description": "749.2489(3) - Reports to Licensing-Agency submits information within 2 working days of putting foster home on inactive status or taking home off inactive status"
  },
  {
    "id": "1955489023",
    "narrative": "The home was placed on inactive status on 08/26/21 and began have preplacement visits of an infant on 2/12/22 then placing the child in the home  on 3/10/22 with a plan for adoption in the home.",
    "activity_id": "907784324",
    "operation_id": "94080",
    "corrected_date": "2022-08-10T00:00:00.000",
    "non_compliance_id": "1030503738",
    "standard_risk_level": "Medium",
    "corrected_at_inspection": "N",
    "date_correction_verified": "2022-08-16T00:00:00.000",
    "technical_assistance_given": "YES",
    "standard_number_description": "749.2539 - Verifications- May not make new placements of children into a home that is provisionally verified."
  },
  {
    "id": "1955489023",
    "narrative": "The home was placed on Inactive Status on 08/26/21 and a report form was not submitted to licensing.",
    "activity_id": "907784324",
    "operation_id": "94080",
    "corrected_date": "2022-08-10T00:00:00.000",
    "non_compliance_id": "1030503740",
    "standard_risk_level": "Medium Low",
    "corrected_at_inspection": "N",
    "date_correction_verified": "2022-08-16T00:00:00.000",
    "technical_assistance_given": "YES",
    "standard_number_description": "749.2819(c) - Inactive Status-when a home is placed on or removed from inactive status, agency must inform licensing by submitting an agency home report form"
  },
  {
    "id": "1955546954",
    "narrative": "Upon arriving at the facility for an unannounced inspection, licensing inspectors discovered that the operation was closed due to a staff meeting. It was determined that the operation had not communicated the alteration in operating hours to the licensing representative.",
    "activity_id": "907842836",
    "operation_id": "94080",
    "corrected_date": "2025-03-04T00:00:00.000",
    "non_compliance_id": "1030650497",
    "standard_risk_level": "Medium Low",
    "corrected_at_inspection": "N",
    "date_correction_verified": "2025-02-25T00:00:00.000",
    "technical_assistance_given": "YES",
    "standard_number_description": "749.153(a)(1)(D) - Notification - At least 30 days in advance - Change in agency or branch office operating hours"
  },
  {
    "id": "1955489024",
    "narrative": "A foster child's service plan review documented plans and goals for recreational and cultural activities, but not progress made toward these goals or descriptions of recreational and cultural activities already provided.    The service plan is also missing documentation of vision and hearing screening services already provided to the foster child.     Information about family visits is also not present in the service plan review.",
    "activity_id": "907784325",
    "operation_id": "94080",
    "corrected_date": "2024-06-04T00:00:00.000",
    "non_compliance_id": "1030503744",
    "standard_risk_level": "Medium",
    "corrected_at_inspection": "N",
    "date_correction_verified": "2024-06-28T00:00:00.000",
    "technical_assistance_given": "YES",
    "standard_number_description": "749.1335(1) - Service Plan Review and Update-To review and update a service plan, evaluate child's progress and effectiveness of strategies and techniques"
  }
]

Evidence behind every value

  • Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash 5a102711aac0ce75c128ee56910dc81738aaaf457eafb697e6dc86b58d9f3b53.
  • 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 7c9ae353fe37e26dd240d8b832b62cb28e69a800a1b3a43b1d297133265b34a8, 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 725fbc594a19c77a…
AI-preference signals
None observed at review
Public record
Yes. Municipal/state open data portal dataset tqgd-mf4x on data.texas.gov.
Reviewed
November 17, 2026; next review May 17, 2027
Licence basis
Publisher's terms of use
Commercial use
Allowed
Redistribution
Allowed
Attribution
Required (text below)

Published on the data.texas.gov open data portal for public use. Anonymous SODA API access needs no key. Portal robots.txt typically allows /resource/ with a crawl delay. Contact-name columns are not requested by this recipe.

Texas open data (data.texas.gov). 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
1.3 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": "HHSC CCL Non-Compliance Data",
  "url": "https://data.texas.gov/resource/tqgd-mf4x.json?$select=section_id,operation_id,activity_id,non_compliance_id,standard_number_description,standard_risk_level,corrected_at_inspection,corrected_date,date_correction_verified,narrative,technical_assistance_given&$limit=1000&$order=operation_id",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "section_id",
      "narrative": "narrative",
      "activity_id": "activity_id",
      "operation_id": "operation_id",
      "corrected_date": "corrected_date",
      "non_compliance_id": "non_compliance_id",
      "standard_risk_level": "standard_risk_level",
      "corrected_at_inspection": "corrected_at_inspection",
      "date_correction_verified": "date_correction_verified",
      "technical_assistance_given": "technical_assistance_given",
      "standard_number_description": "standard_number_description"
    },
    "required": [
      "id"
    ],
    "types": {
      "corrected_date": "datetime",
      "date_correction_verified": "datetime"
    }
  },
  "schedule": "daily",
  "key_field": "id"
}

source.json

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

{
  "name": "HHSC CCL Non-Compliance Data",
  "url": "https://data.texas.gov/resource/tqgd-mf4x.json?$select=section_id,operation_id,activity_id,non_compliance_id,standard_number_description,standard_risk_level,corrected_at_inspection,corrected_date,date_correction_verified,narrative,technical_assistance_given&$limit=1000&$order=operation_id",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "section_id",
      "narrative": "narrative",
      "activity_id": "activity_id",
      "operation_id": "operation_id",
      "corrected_date": "corrected_date",
      "non_compliance_id": "non_compliance_id",
      "standard_risk_level": "standard_risk_level",
      "corrected_at_inspection": "corrected_at_inspection",
      "date_correction_verified": "date_correction_verified",
      "technical_assistance_given": "technical_assistance_given",
      "standard_number_description": "standard_number_description"
    },
    "required": [
      "id"
    ],
    "types": {
      "corrected_date": "datetime",
      "date_correction_verified": "datetime"
    }
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "texas-hhsc-ccl-non-compliance-data",
    "version_id": "1a24ff4a-d336-46a8-a8c3-ae04e9f33306"
  }
}

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/texas-hhsc-ccl-non-compliance-data -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 texas-hhsc-ccl-non-compliance-data --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("texas-hhsc-ccl-non-compliance-data");
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 HHSC CCL Non-Compliance Data: get_catalog_source texas-hhsc-ccl-non-compliance-data,
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 Texas open data and in company registries.

SourceFinch is independent and is not affiliated with or endorsed by Texas open data. This page describes hhsc ccl non-compliance data as SourceFinch acquires it.