Becton Dickinson · Rate Limits
Becton Dickinson Rate Limits
BD does not publish public rate limits for the BD Incada or Pyxis connected-care APIs. Capacity is provisioned per hospital tenant on AWS-backed infrastructure and tuned to the connected-device fleet. No numeric values are asserted here.
Becton Dickinson Rate Limits is the machine-readable rate-limit profile for Becton Dickinson on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring varies.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Healthcare, Medical Devices, Connected Health, and Rate Limiting.
2 Limits
Throttle: 429
HealthcareMedical DevicesConnected HealthRate Limiting
Limits
Per-tenant ingestion rate hospital-tenant
sized to connected-device fleet; see BD Incada implementation runbook
Telemetry from infusion pumps, monitors, and Pyxis stations is ingested per tenant; capacity is provisioned at deployment.
HL7 FHIR API throttle integration
see BD-EMR integration documentation
FHIR endpoint capacity governed by EMR connector and BD-side configuration.
Policies
Backoff Strategy
Use exponential backoff with jitter on throttled responses; honor Retry-After when present.
Per-Hospital Provisioning
Capacity tuned at deployment to device fleet and EMR throughput; not enforced via a public per-second number.
Clinical Safety Constraints
Connected-device APIs operate inside a regulated clinical environment; integration changes and load profiles must follow the hospital's biomed/IT and pharmacy change-control process.
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.