Coming January 6, 2025: Changes to Patient History API throttling and default job latency

Starting January 6, 2025, we will apply the following changes to the Patient History API:

• Patient History API requests that do not supply a priority attribute will by default run through our bulk queue. This queue manages our load on Carequality and CommonWell and ensures that our request volumes do not adversely impact other responders. It prioritizes jobs on a FIFO basis and smooths the rate at which they are submitted to the networks to ensure we don’t create large bursts of requests. Depending on how large the queue is when you submit a job, it may take as long as or longer than 36 hours to run; however, most jobs will run within 24 hours.
• Patient History API requests that use “priority”: true will be throttled at a rate of 10 requests per minute per customer to prevent inadvertent traffic spikes on the EHR network.

We recommend that customers who expose the Patient History API to human users through a UI update their requests to use “priority”: true and account for throttling at a rate of 10 requests per minute. This will ensure that those users’ requests are honored immediately.

Customers that are submitting requests in bulk or through an asynchronous process don’t need to take any action – your requests will default to the bulk queue starting January 6th.

Customers that use our subscription-based packages and or submit requests through the Zus App need to take no action.