The composite request is a convenience function that allows you to create an electronic prescription and order in a single request, and optionally also create a patient and/or prescriber. The request body can contain the following objects: patient, prescriber, electronic_prescription, order. While no single entity is required (the composite request can be used to create a standalone order or electronic prescription), it is designed to be comprehensive. If any single entity creation fails, the entire request will fail and no entities will be created.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
If 'true', always create a new order even if a mergeable order exists for the patient. Default is 'false', which merges into existing open orders when available.
true
An electronic prescription object. Please refer to the Create a New Electronic Prescription endpoint for more information on required fields.
An order object. Please refer to the Create an Order endpoint for more information on required fields.
A patient object. If you pass new patient data, a new patient will be created. Or you may reference an existing patient by id or external_id. Please refer to the Create a Patient endpoint for more information on required fields.
A prescriber object. If you pass new prescriber data, a new prescriber will be created. Or you may reference an existing prescriber by id or npi. Please refer to the Create a New Prescriber endpoint for more information on required fields.
Response from composite entity creation. Only includes keys for entities that were provided in the request. For example, if only patient and order were requested, only those keys (plus summary) will be present in the response.