# Changelog of Zimbabwe MCAZ Registered Medicines (`a-g-d/zw-mcaz`) Actor

- **URL**: https://apify.com/a-g-d/zw-mcaz/changelog.md
- **Full Actor documentation**: https://apify.com/a-g-d/zw-mcaz.md

## Changelog

All notable changes to this project are documented here. The format follows
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project adheres to
[Semantic Versioning](https://semver.org/).

### \[0.1.0] - 2026-10-21

#### Added

- The Medicines Control Authority of Zimbabwe (MCAZ) public registers of human (about
  3,170), veterinary (about 400) and complementary (about 490) medicines, read through the
  register grid's own data service. One item per registered medicine with English camelCase
  keys: category, application id, registration number, trade and generic names, active
  ingredients, strength, dosage form, route, supply category, applicant, principal,
  manufacturers (name and country), registration and expiry dates (ISO), registration
  status, source page and fetch time.
- Filters: categories, trade name, generic name or ingredient, registration number,
  manufacturer, applicant, supply category, registered since and expiring before. The
  register applies trade name, generic name, manufacturer and registered-since itself;
  every filter is also checked on each item.
- Privacy: an output allowlist; manufacturers reduced to company name and allowlisted
  country, the address between them never output; company names holding a digit, an e-mail
  address, a phone number or an address word output as null (fail closed); only the
  medicines registers are requested.
- Politeness: one request at a time with at least 1.5 s between requests, 500 rows per
  page, an honest User-Agent.
- Resilience: retries with exponential backoff and jitter inside a run-wide budget;
  per-register fail-soft (the run fails only when every requested register fails) and an
  `OUTPUT` summary per register; the run stops cleanly 20 s before its timeout and ends
  SUCCEEDED with what it stored; optional Apify Proxy.
- Pay-per-event billing: `product-record` per stored medicine, charged after storing; each
  batch is planned against the remaining spending limit and the run stops cleanly when it
  runs out.