Office Ally Guide
Structuring LAM Queries for Office Ally
These forms need precise data formats and must pass strict validations. To maximize action success and avoid failures, follow these guidelines carefully.
API Request Structure
To interact with Office Ally, your request must include the following fields:
integration_id
: This specifies the type of response, such as filling out a medical form.properties
: This contains adata
field, which is an array of objects representing individual form entries. A maximum of 15 data objects are recommended per request.
OFFICEALLY01
This integration helps you add a person’s details in Office Ally Practice Mate portal.
Example API Request for adding a person
Validation and Rejection of Entries
If your request contains more than 15 objects in the data
array, the request will fail, and the rejected entries will be returned in the data.properties.failed
field of the response. Make sure to limit your requests to 15 objects per submission.
Ensure all data follows the correct format and passes the validations required by the Office Ally system. Incorrect data or formats will result in rejected requests.
By following these guidelines, you ensure that your API requests for the Office Ally integration meet all the necessary standards and validations required by medical service websites.
Was this page helpful?