I’m concerned that a live user of our service could hit the 10MB APIM limit for the A&G worklist. They have ~1500 cases.
Is this in danger of hitting that limit?
Thanks
Sam
I’m concerned that a live user of our service could hit the 10MB APIM limit for the A&G worklist. They have ~1500 cases.
Is this in danger of hitting that limit?
Thanks
Sam
Hi @sam.carter,
There are the following related requirements in the SCAL which provide some detail:
A008-01 | Payload Filtering | The solutions API calls MUST be filtered where possible. Filters include Location, Specialty, Service and Clinician | The API call MUST filter on specialty and/or location where possible to avoid large payloads. Provider worklists can be large and the maximum payload is set to 10mb. |
---|---|---|---|
A008-02 | Payload Size | The solution MUST monitor payload size. Calls over 10MB will not be returned. | The solution MUST monitor payload size to avoid breaching set limits that will lead to the information being inaccessible. The limit is 10mb (which equivalates to approximately 7500 rows). Clinical Consideration: The supplier should work with the end user to understand local worklist management and ensure contingencies are in place should the API call exceed or be close to breaching the allowed limit. |
Note that 7500 is just an estimate/guide as the number of rows that will fit into 10MBs varies per worklist (as they return different amounts of data).
As per A008-02 your solution should be monitoring response payload sizes in order to warn your users and be able to avoid hitting the limit.
Regards,
Adam.
Hi @sam.carter - It may be worth engaging with the service here.
Is there a reason for 1500 active cases? Or is this a user who’s been added to every service workgroup?
Our guidance does state that clinical teams should ensure:
Thanks,
Z.