Create a prescription for an already-dispensed transaction (post-dispense flow)

Populated when the request supplied string? CreateMedicationRequestDto.InvoiceId and an estimate line item was created in the same call.

The estimate the dispense was attached to — either the one the caller supplied or one auto-created/resolved server-side. Lets a client that had no estimate of its own adopt the server's estimate instead of failing to reconcile the line.

The estimate the request's billable line was placed on at creation (in-house / same-day requests). Null for external (non-billable) requests.

The Pending estimate line created for this request at creation, if any.

The lifecycle MedicationRequest recorded for this operation. The compound endpoint applies capture → approve → dispense as far as the caller's permissions allow; string? MedicationRequestResultDto.RequestStatus says where it stopped.

Lifecycle status after this call: requested | approved | dispensed.