How can a pilot test a difficult routing boundary without expanding into a whole business?

A simulation engineer scopes a healthcare administration pilot around referrals that lack required booking information. REF-0286 contains an appointment request and a service code, but its authorisation field is empty. The generated policy distinguishes missing administrative documentation from a request requiring clinical review.

The intake agent links TASK-0193 to REF-0286 and assigns it to referral administration to obtain the missing authorisation. The referral changes from received to awaiting administrative completion. It does not enter the booking-ready queue, and the agent does not decide whether the requested care is appropriate.

The consequence is visible: booking actions remain unavailable until the administrative requirement is satisfied. A route to clinical review would be incorrect under this scoped policy because the task supplies no clinical question to resolve.

The buyer’s pilot request can specify this boundary, the required records and the condition that unlocks booking. MirrorFirm could generate the referral states and administrative policies needed to exercise it. The pilot excludes clinical triage and treatment decisions, keeping the first environment focused on whether the agent respects a clear administrative prerequisite.