HIQA Healthcare Guidance Metadata

Extracts the first healthcare-service guidance catalogue page. One row per canonical publication URL. Listing only: no details or documents requested. Twelve cards were observed in the 6 October 2026 fixture, not a completeness promise. Missing values are null; attachmentUrls is empty because enrichment is disabled. Updated dates remain updated dates, never silently relabelled publication dates.

Input and output

maxItems: integer 1–30, default 20. Output includes title, url, publicationKind, dateType, sourceDate, sourceDateRaw, serviceCategory, attachmentUrls, listingUrl, retrievedAt, source, attribution, licence and licenceUrl. No advice or compliance conclusions. RUN_REPORT distinguishes bounded_complete from stopped and gives request, byte and item counts. Errors fail the run; partial emitted data is retained.

Access and reuse

Fixed https://www.hiqa.ie/guidance-providers/healthcare-services/guidance only, after robots.txt; serial requests, at least 2 seconds apart (longer robots delay honored), no redirects, retries, proxy rotation, credentials or bypass. 32 requests, 2 MB per response, 8 MB aggregate and 480-second request-start/response-loop budget (an in-progress socket read may add up to its timeout); 25-second socket timeout. Standard runtime networking is retained. Reports-and-publications and selected detail probes returned 503 in research and are deliberately never requested.

HIQA permits reuse under applicable Irish PSI conditions: https://www.hiqa.ie/disclaimer . Attribute HIQA, preserve accuracy and original title/date/source URL. Excludes third-party content, logos and images. No endorsement or clinical recommendations.

Qualification

CompliantCare specifically covers HIQA monitoring (https://safework.place/modules/compliance-monitoring/); Fedvol distributes HIQA guidance to service providers. Official Store domain/full-name searches found no dedicated HIQA Actor on 6 October 2026, within bounded search results. Generic regulatory and page-change monitors remain alternatives; demand evidence is not a paid-buyer commitment.

Run and test

Install requirements.txt; run python main.py with normal Apify SDK environment. Run python -m unittest discover -s tests. Bundled source HTML fixture tests are portable. Deployment needs main.py, requirements.txt, Dockerfile, README.md and the three .actor JSON files only. Local SDK live smoke and independent review are recorded separately; this source package does not assert a cloud deployment.

Pricing and budget limits

The paid unit is one source-linked metadata record saved to the default dataset. The current Store price is $1 per 1,000 records, plus $0.00005 per run start; usage is included. Check the Store pricing panel for the price applying to your run. Source coverage, filters, availability and your spending limit can reduce the number returned; no minimum record count or historical completeness is guaranteed.

The SDK automatically handles record charges. Before source requests, the Actor checks whether the record budget is already exhausted; after each write it counts only records accepted by paid billing and stops at the limit. RUN_REPORT status budget_limit_reached means the spending limit stopped further work; coverage may be partial. The report is not an invoice. Local/non-monetized runs retain normal dataset counting. Zero matches can still incur the run-start charge.

Memory is capped at 256 MB, matching a successful hosted run. Source changes or different inputs may still cause failure; this is not a performance guarantee.