What does a reseller pilot look like for a healthcare administration pack?

A product lead at a data marketplace wants a healthcare administration listing for their catalogue. They ask for a pilot covering specialist referral intake at a clinic network.

The pilot scope names one case type, referral `REF-1180`. A referral needs a signed referral letter, a current coverage record and a clinical summary. The generated set includes cases where the coverage record has lapsed, the letter is unsigned or the summary belongs to a different patient record.

The delivery is a JSONL release with a schema and a manifest, plus a small environment with `get_referral`, `read_document` and `send_request` actions.

A data operations analyst runs the marketplace's acceptance checks. They re-derive outcomes for a hand-picked set of cases, find all links resolve, and note that request wording is too uniform for one subtype. That is sent back with case identifiers.

The product lead then sends the revised sample to one prospective customer for a trial evaluation. The customer reports back on scoring hooks and schema clarity.

The pilot closes with a written decision: list the pack with a narrower description, and keep three licensing questions open for discussion with MirrorFirm. These cover sublicensing, restrictions to pass to customers and handling of updates.

**What it teaches:** a pilot should end with a decision and a list of unresolved terms. The data remains generated, so the plan includes a disclosure review before any customer sees it.