List Phlebotomy Orders
All phlebotomy orders for a patient, newest first — backs the Sent / Completed status chips on the Documents tab. Requisition has no equivalent list endpoint; this one exists because the chips need it.
sentAt/sentChannels are derived here, so an order faxed from the
Comms composer or shared to the portal shows as sent even though this
feature’s own flow never touched it.
Headers
The tenant you are making this request on behalf of
Your api key
Query Parameters
Response
Successful Response
Draw frequency on the OneBlood Form-96 phlebotomy order.
Rendered as checkboxes on the form but functionally exclusive — a single
selection, not independent booleans. OTHER carries free text in
PatientPhlebotomyOrder.other_frequency.
ONE_TIME, WEEKLY, EVERY_2_WEEKS, EVERY_4_WEEKS, EVERY_8_WEEKS, OTHER ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$Draw amount on the OneBlood Form-96 phlebotomy order.
Rendered as checkboxes on the form but functionally exclusive — a single
selection, not independent booleans. OTHER carries a free-text mL
amount in PatientPhlebotomyOrder.other_amount_ml.
ONE_UNIT, OTHER A channel a phlebotomy order's document went out on.
Derived, never stamped — each member corresponds to a link that already exists once the document leaves the building:
FAX: afax_attachmentrow references the documentEMAIL: anemail_attachmentrow references the documentPORTAL:document.shared_with_patientis set (a portal share, or the SMS that texts the patient a portal link)
An order can therefore be on several channels at once, which is why the response carries a list rather than one "how was it sent" value.
EMAIL, FAX, PORTAL 
