Integration FAQs

It shouldn't change, since there'll simply be http requests and most of the load would be on the embedded browser on the EHR.

We have rate-limiting per API key in case of extreme usage from a specific source, but it's mainly to avoid disruption of the service.

Nothing is stored locally at the EHR and the data is stored on Autoscriber servers.

Bandwidth usage would depend on the hospital's bandwidth limit itself, but anything from 10mbps would be good enough.

We use common http and https ports (80/443).

You can implement the wakeLock API of the browser. This way, the screen will stay on, and the computer does not lock. The one scenario that will bypass this, would be if the user switches tabs and then leaves the computer.

Would our server get an increase in load when using the autoscriber API?

Are there limitations per minute for APIs? Personalised

Where does Autoscriber process the data with an API-integration?

What is the bandwidth usage per minute for a user (on average)?

Could you elaborate on the ports used for the sending of data?

How can I prevent a screen timeout while the conversation is happening?