How ArisGlobal scaled generative AI inference on Amazon Bedrock ArisGlobal reversed the order of prompt caching in its NavaX adverse-event extraction engine on Amazon Bedrock, caching the shared prompt prefix instead of each source document, after the shared prefix grew about 150% over 6 months and per-case inference costs rose more than 200%. NavaX, which runs on AWS and uses Anthropic's Claude via Amazon Bedrock, extracts around 130 fields per adverse-event case and has processed over 1 million real transactions in regulated pharmaceutical environments, according to ArisGlobal's internal production telemetry. The change reduced effective input cost and let ArisGlobal add tenants without proportional cost growth. Artificial Intelligence https://aws.amazon.com/blogs/machine-learning/ How ArisGlobal scaled generative AI inference on Amazon Bedrock ArisGlobal, a provider of life sciences technology spanning pharmacovigilance, regulatory, medical affairs, clinical, and quality functions, developed NavaX, an AI engine purpose-built for life sciences on Amazon Bedrock https://aws.amazon.com/bedrock/ , to automate adverse-event case processing. ArisGlobal chose Amazon Bedrock for managed access to foundation models, EU geographic cross-Region inference, and managed prompt caching. As enterprise customers added distinct compliance requirements, the shared prompt prefix grew by about 150% over 6 months, while per-case inference costs increased by more than 200%. ArisGlobal first cached each source document because it was the largest part of a request. That left the growing shared prompt prefix outside the cache. By reversing the order and caching the shared prefix instead, ArisGlobal reduced effective input cost and supported additional tenants without proportional cost growth. Who is ArisGlobal? ArisGlobal is the creator of LifeSphere, a unified SaaS platform for pharmacovigilance, regulatory affairs, quality, and medical information. LifeSphere serves pharmaceutical companies globally, including multiple Top 20 pharma organizations by revenue source: ArisGlobal press release https://www.arisglobal.com/media/press-release/arisglobal-reports-strong-q1-2026-momentum-with-accelerating-enterprise-ai-transformation/ . The entire system runs on AWS. LifeSphere NavaX https://www.arisglobal.com/navax/ is ArisGlobal’s AI engine that transforms drug safety from a system of record into a system of strategic advantage. ArisGlobal productionized their first generative AI solution on Amazon Bedrock with Anthropic’s Claude https://aws.amazon.com/bedrock/claude/ in March 2025. According to ArisGlobal’s internal production telemetry, they have processed over 1 million real transactions in regulated pharmaceutical environments, handling billions of tokens across multiple enterprise tenants. Model availability varies by Region. See Model support by AWS Region https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html . How NavaX processes an adverse event case When a pharmaceutical company receives an adverse-event report, typically a multipage PDF describing a patient’s reaction to a medication, NavaX’s Dynamic Data Extraction DDE agent extracts around 130 fields. These fields include patient demographics, suspect drugs, reporter information, event timelines, seriousness criteria, and regulatory classifications. Because this content includes protected health information, ArisGlobal applies responsible-AI controls as a standard part of its production deployment. It draws on capabilities such as Amazon Bedrock Guardrails https://aws.amazon.com/bedrock/guardrails/ to filter content and detect or mask sensitive information. Extracted fields are also validated against the schema and grounded in the source document. This extraction happens across multiple sequential requests to the model. Each request focuses on a different section of the case form, and each carries: - System instructions — model behavior rules, output format specifications, and regulatory compliance constraints. - Customer-specific rules — per-tenant extraction logic, field mappings, and business rules that differ by pharmaceutical company. - Extraction schema — around 130 target fields with types, validation rules, and few-shot examples. - The source document — the adverse event PDF often 10–200 pages . Two inputs repeat at different scopes. The shared prompt prefix includes the system rules, extraction schema, and few-shot examples. It repeats across requests, cases, and tenants using the same agent. The source document repeats only for the requests associated with one case. The prompt bloat problem When NavaX launched with its first enterprise tenant, the system prompt was lean. As ArisGlobal onboarded additional pharmaceutical companies, each brought specific requirements: - Custom field mappings Tenant A maps reaction onset differently from Tenant B . - Regulatory jurisdiction rules EU ICSR compared with FDA MedWatch and PMDA formatting . - Company-specific business logic for seriousness assessment and causality. - Per-tenant few-shot examples calibrated to each company’s historical cases. Over 6 months, the shared prompt prefix grew from approximately 72,000 to 180,000 tokens, a 150% increase. With multiple sequential requests per case, per-case inference costs increased by more than 200%. The prefix grew with every tenant and was reprocessed on every request, so prompt growth compounded with transaction volume. Table 1 compares the original document-first request order with the production prompt-first design. | Aspect | First approach | Production design | | Request order | Per-case document, cache checkpoint, shared prompt prefix | Shared prompt prefix, cache checkpoint, per-case document | | Cached prefix | The document, which changes for every case | The shared prompt prefix, which repeats across requests | | Reuse scope | Only the remaining requests for one case | Requests across cases and tenants using the same agent | | Cost effect | The growing prompt is repeatedly processed at the full input rate | Fleet-wide prompt reuse supports sublinear cost growth | | EU routing | EU geographic cross-Region inference remains unchanged | EU geographic cross-Region inference remains unchanged | Amazon Bedrock prompt caching strategies Amazon Bedrock prompt caching reduces latency and input token costs by caching a contiguous prompt prefix from the start of a request through a cache checkpoint. A later request with the same prefix can read cached tokens at a reduced rate instead of processing them again. Cache entries have a time-to-live TTL that resets after a successful cache hit. Caching is prefix-based rather than block-based. Request sections are evaluated in sequence—tools, system, then messages—so changing an earlier section invalidates matching content that follows it. Cache checkpoints explicit control With explicit cache checkpoints, you can choose the exact prefix boundary. Supported Claude models allow up to four checkpoints per request. - Place each checkpoint after a stable, reusable prefix. - Meet the model-specific minimum prefix size. For Claude Sonnet 4.5 the minimum is 1,024 tokens see supported models and Regions https://docs.aws.amazon.com/bedrock/latest/userguide/models-supported.html . - Checkpoints are evaluated in this order: tools, system, and messages. - Changing an earlier section invalidates cache matches for later sections. - The default TTL is 5 minutes. Select models support a 1-hour TTL by setting "ttl": "1h" . Longer-TTL entries must precede shorter-TTL entries. Simplified cache management automated With simplified cache management https://docs.aws.amazon.com/bedrock/latest/userguide/prompt-caching.html , you place one checkpoint after static content. Amazon Bedrock searches backward from that point for the longest matching prefix, up to about 20 content blocks. - One checkpoint can locate the longest matching prefix automatically. - Use explicit checkpoints when stable content extends beyond the lookback range. What ArisGlobal cached, and what they deliberately did not ArisGlobal uses one explicit checkpoint immediately after the shared prompt prefix, which is sent first. The per-case document follows the checkpoint and is processed on each request. This reverses the initial request order. Because only a prefix can be cached, ordering determines which content can be reused. The launch design: Prioritizing document reuse The first design put the 10–200 page source document at the start of each request and placed the checkpoint after it. The shared prompt prefix and section-specific question followed the checkpoint. The design reused the document within one case: the first request wrote it to cache, and later requests for that case read it at the reduced rate. The next case used a different document and required a new cache write, so reuse never extended across cases or tenants. More importantly, the shared prompt prefix remained after the checkpoint and was processed at the full input rate on every request. The content driving the cost curve was excluded from the cache. The evolved production design: Prioritizing shared-prefix reuse The production design changed the order rather than adding another checkpoint: the shared prompt prefix comes first, the checkpoint follows it, and the document comes last. The same checkpoint now creates a reusable fleet-wide cache entry: - Before — the cached document prefix was unique to one case and the shared prompt was never cached. - After — the cached shared prompt prefix repeats across requests, cases, and tenants using the same agent. ArisGlobal gave up limited document reuse within one case and gained prompt reuse across the fleet. The shared prefix is also the part that grows as customers are added. Updated implementation For most active accounts, cases arrive about every 5 minutes per tenant and multiple tenants run concurrently. This traffic keeps the shared prefix warm during business hours because each cache hit resets the TTL. Caching both the prompt and the document A second checkpoint after the document would cache a combined prefix consisting of the shared prompt and that case’s document. The entry would still be unique to one case. ArisGlobal therefore prioritized the prefix whose reads amortize across the fleet. The shared prompt prefix scales across cases and tenants. The per-case document does not. In production, 65% of input tokens on a typical request are served from the shared prompt cache. Figure 1 shows cache reads consistently exceeding cache writes. Results Caching the shared prompt prefix produced the following results while the EU geographic cross-Region inference profile remained in place: - 65% of input tokens served from cache at the reduced read rate. - Up to 25% lower end-to-end latency on cached production requests. - Approximately 50% lower effective input cost. - Approximately 40% lower overall monthly inference spend at more than 19 billion tokens per month. - Around 15% more enterprise tenants onboarded without proportional cost increases. - EU geographic routing unchanged. Prompt caching operates within the existing inference configuration. Based on ArisGlobal’s production billing data, serving 65% of input tokens from cache reduced effective input cost by approximately 50%. At more than 19 billion tokens per month, this produced approximately 40% overall monthly savings in inference spend. Note: All performance and cost figures in this section reflect ArisGlobal’s production metrics as reported to AWS. Results will vary based on prompt structure, traffic patterns, and cache hit rates. Production learnings ArisGlobal’s experience offers guidance for many workloads with large, repeated prompt prefixes: Cache what repeats, not what is largest. A large per-case document offers limited reuse, while a byte-identical shared prompt prefix can serve requests across the fleet. Put stable content first. Order tool definitions, system instructions, schemas, and examples before the checkpoint. Place tenant identifiers, case data, and the per-request question afterward.