Mark Phlebotomy Order Completed
Toggle the manual staff “did the draw happen” tick against the calling
provider. completed=False clears the tick (an accidental-tick undo).
Headers
The tenant you are making this request on behalf of
Your api key
Path Parameters
Body
Request body for PATCH /phlebotomy-orders/{id}/completed. completed
toggles the tick — True stamps completed_date/completed_by_provider_id
against the calling provider, False clears both (an accidental-tick undo).
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 
