# HIQA Healthcare Guidance Metadata (`vixendata/hiqa-healthcare-guidance-metadata`) Actor

HIQA Healthcare Guidance Metadata with bounded official metadata and source attribution.

- **URL**: https://apify.com/vixendata/hiqa-healthcare-guidance-metadata.md
- **Developed by:** [Vixendata](https://apify.com/vixendata) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 source-linked publication/news/catalogue records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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.

# Actor input Schema

## `maxItems` (type: `integer`):

Maximum metadata rows from the first listing page only; does not expand historical coverage.

## Actor input object example

```json
{
  "maxItems": 20
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("vixendata/hiqa-healthcare-guidance-metadata").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("vixendata/hiqa-healthcare-guidance-metadata").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call vixendata/hiqa-healthcare-guidance-metadata --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vixendata/hiqa-healthcare-guidance-metadata"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/I7wo5p7x6Rjm8FwqV/builds/zOPj23v3GmKoA1saG/openapi.json