AWS Healthcare Global

Pfizer

Document Processing · Enterprise Knowledge Search

With Pfizer teams highly focused on ongoing technology projects, PACT addresses challenges around the bandwidth needed for prototyping. “With this collaboration, AWS brings in its prototyping teams to work with business and IT teams directly on relevant challenges,” says Bulusu.

16,000 hours
55% reduction
From PACT’s initial list of 14 projects, five ideas have moved into production so far.
The development of one drug can result in approximately 20,000 documents, and scientists often must look for data manually using a variety of tools to find historical data.

Reported impact

Business outcome

From PACT’s initial list of 14 projects, five ideas have moved into production so far. “Even though we are just doing prototyping and there’s no immediate revenue in it for AWS, AWS always brings forward its top teams,” says Bulusu. Key reported metrics include of search time saved annually 16,000 hours; 16,000 hours; in infrastructure costs 55% reduction.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

Learn how Pfizer and AWS are collaborating to build generative AI prototypes to help bring innovative therapeutics to market quickly. With a mission to transform healthcare for its 1.3 billion patients, Pfizer is always seeking to innovate using cutting-edge technology. To optimize the development of new medicines through cloud-based solutions, Pfizer and Amazon Web Services (AWS) have created the Pfizer-Amazon Collaboration Team (PACT) initiative. Under PACT, Pfizer has pursued 14 projects, including generative artificial intelligence (AI) and machine learning (ML) to save scientists up to 16,000 hours of search time annually and cut infrastructure costs by 55 percent. Pfizer uses a plethora of tools from AWS to explore new ideas, quickly build prototypes, and drive a passion for innovation in digital drug development. Source data enters the Pfizer workflow through its application services, processed with Amazon SageMaker, Amazon Bedrock, and delivered through Amazon Kendra.

Data flow

Source data enters the Pfizer workflow through its application services, processed with Amazon SageMaker, Amazon Bedrock, and delivered through Amazon Kendra.

Solution architecture

3 components · 2 layers
  1. Compute
    • Amazon SageMaker Supports model training, fine-tuning, evaluation, or managed inference for the customer workload.
    • Amazon Bedrock Hosts the foundation models and inference APIs that power the generative AI features.
  2. Serving
    • Amazon Kendra Indexes enterprise content and powers semantic retrieval over internal knowledge.

Architecture clues

  • Named components in the deployment include Amazon SageMaker, Amazon Bedrock, Amazon Kendra.

Evidence from the source

16,000 hours
55% reduction
From PACT’s initial list of 14 projects, five ideas have moved into production so far.
The development of one drug can result in approximately 20,000 documents, and scientists often must look for data manually using a variety of tools to find historical data.
The first use case sought to minimize the time spent in data discovery upto 80 percent for 1,500 PSSM scientists.
“If we were to do this ourselves, assuming we could find the bandwidth and people with appropriate skills, it would take at least 3 months,” says Bulusu.
Transparency Evidence & methodology 95/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    5 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. AWS

    Pfizer customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/pfizer-PACT-case-study/
    Source type
    Vendor-published customer story
    Published
    Aug 21, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.