Changelog
Product updates, API changes, and announcements.
We have made updates to the behavior of Prescriber management.
- When sending or updating state licenses (qualifications), you no longer need to send all existing qualifications. Only those with updates (e.g., expiration date) need to be sent.
- An update of a license number for an existing state will deactivate any prior state license and replace with the new number.
- If you attempt to create a prescriber who already exists (as determined by prescriber NPI), the existing prescriber will be returned. If the prescriber is not associated with your customer, the prescriber will be associated. To update prescriber data please use the update/edit capabilities.
The
price field has been removed from prescription and non-prescription products. Previously it was a required field.If your customer account allows, you may send a
custom_shipping object during new order creation or order update, providing a prepaid label and other shipping details.You may choose to include
We have improved patient handling logic within the new order creation endpoint. When creating a new order, you may now send:
electronic_prescription_ids (an array of IDs) in the creation of a new order. This is an optional convenience field and is not required; however if you are using the Electronic Prescriptions endpoint to create prescriptions, for your own record-keeping or to optimize prescription matching, you may send your resulting electronic prescription ID values along with a new order.Electronic Prescription IDs will also be returned in any single order GET request (as electronic_prescription_ids). They will not be returned in Get Orders.We have improved patient handling logic within the new order creation endpoint. When creating a new order, you may now send:
patient_idto match an existing patient;patient: {"id": "{UUID}"}to match an existing patient;patient: {"external_id": "{external_id_value}"}to match an existing patient (by your own ID); orpatient: {new patient data}to create a new patient within the new order workflow
patient or patient_id is required.Multiple
medication entities can now be sent (as a medications array) in a single Electronic Prescription request, if all other aspects of the prescription (patient, prescriber, order) are the same across medications. A single medication can still be sent as a standalone object.Blend webhooks can now be optionally authenticated via an
Authorization: Bearer header. Once you generate a secret, it will be sent in all webhook events.For easier testing and integration, you can now manually send sample webhooks to any webhook endpoint, or preview any event webhook payloads.
You can now update an order’s address so long as it is not already shipped (or if shipping is not in process). In the same request you can also choose to update the patient’s address on-file, if the change is permanent.
Added support for creating a New Patient within the
POST body of a New Order. (Previously a Patient would need to be created in a separate request, and referenced in the New Order creation.)You can now direct-submit an electronic prescription in JSON format. Previously the
<SCRIPT> format was required for direct submission of electronic prescriptions.Orders can be paused, unpaused, or cancelled from within the customer dashboard or via API. Only orders that are in a
received state can be paused or cancelled. For orders already in processing, you must contact Blend for special exception handling.