Test Mode

Build your integration with a test client. Test clients call the same host and routes as live clients, with the same validation, but no document is processed and results come from fixtures.

Test client IDs start with amh_test_, and live client IDs start with amh_live_. Every batch and document has liveMode, which is false in test mode. Test and live data are separate: a test token cannot read a live batch, and /fhir/R4 returns 403 to a test token.

Test content is validated for size, type, and checksum, then discarded. Test batches are kept until you delete them.

Simulated Timeline

After submit, each document moves through the same statuses as a live document, on a simulated clock. Poll as you would in live mode.

From	To	Delay
pending	queued	2–5 seconds
queued	processing	5–15 seconds
processing	succeeded or failed	2–5 seconds, or 2 minutes for amh-test: slow

The number of documents in progress at once is capped at the same limit as live mode.

Fixtures

Succeeded documents return entities from a fixture of real pipeline output for a synthetic note. The same content always returns the same entities.

Test Markers

Start the content with a marker line to force an outcome. Any other amh-test: line is rejected.

First Line	Outcome
amh-test: conversion_empty	failed with conversion_empty
amh-test: pipeline_failed	failed with pipeline_failed
amh-test: not_processed	failed with not_processed
amh-test: duplicate	succeeded with the standard fixture
amh-test: slow	succeeded after 2 minutes in processing