MongoDB Healthcare Denmark

Novo Nordisk

Document Processing

Novo Nordisk needed to reduce the 12-week, multi-team effort required to produce compliant clinical study reports without sacrificing quality or regulatory rigor.

CSR creation reduced from 12 weeks to 10 minutes
“In terms of value, each day sooner a medicine gets to market can add around $15 million in revenue to the company.”
“We’ve reduced the time taken to create Clinical Study Reports from 12 weeks to 10 minutes, with higher quality outputs and a fraction of the team.”

Reported impact

Business outcome

NovoScribe reduced CSR creation from 12 weeks to 10 minutes, improved output quality, reduced staffing requirements, and accelerated time-to-market for new treatments.

  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

Novo Nordisk created the NovoScribe platform to automate Clinical Study Report production with a retrieval-augmented generation architecture built on MongoDB Atlas Vector Search, Amazon Bedrock, and LangChain. Statistical outputs from clinical trials, report templates, and supporting documentation are prepared as structured tables, figures, and vectorized content inside MongoDB Atlas. LangChain orchestrates multiple Bedrock-hosted foundation models, including Claude 3 and Titan, as well as the company's private ChatGPT instance, so teams can switch models without rewriting application code. Atlas Vector Search supplies the relevant template sections and report evidence back into the prompting flow, grounding generation in the right trial context. The system therefore replaces slow manual compilation, merging, and QA-heavy handoffs with a governed AI pipeline that drafts complete CSRs in minutes, while still allowing Novo Nordisk to compare model behavior and iterate quickly as requirements evolve.

Data flow

Clinical trial data is analyzed into tables and figures, templates and evidence are embedded in MongoDB Atlas, LangChain orchestrates Bedrock-hosted models such as Claude 3 and Titan, and MongoDB Atlas Vector Search feeds the right context back into the prompts so NovoScribe can assemble full clinical study reports in minutes.

Solution architecture

6 components · 4 layers
  1. Compute
    • Amazon Bedrock Hosts the foundation models NovoScribe uses to generate and refine report content.
    • Claude 3 Provides one of the foundation-model options Novo Nordisk uses for CSR generation.
    • Titan Provides an additional foundation-model option in the NovoScribe workflow.
  2. Storage
    • MongoDB Atlas Stores NovoScribe's trial outputs, report templates, and retrieval corpus for clinical study report generation.
  3. Serving
    • MongoDB Atlas Vector Search Retrieves relevant report templates and clinical evidence to ground CSR generation.
  4. Orchestration
    • LangChain Orchestrates model switching and the RAG workflow without requiring application-code changes.

Architecture clues

  • Novo Nordisk experiments with multiple embedding and generation models per report.
  • NovoScribe was initiated in mid-2023.
  • The platform also uses a private ChatGPT instance alongside Bedrock-hosted models.
  • The workflow uses retrieval-augmented generation over statistical outputs and report templates.

Evidence from the source

NovoScribe uses the Claude 3 and Titan foundation models hosted by Amazon Bedrock, alongside the company’s own private instance of ChatGPT.
“A CSR usually takes around 12 weeks to compile, involving a multidisciplinary team of statisticians, scientists, and technical authors.”
“We’ve reduced the time taken to create Clinical Study Reports from 12 weeks to 10 minutes, with higher quality outputs and a fraction of the team.”
“With NovoScribe, we are the first in the industry to generate a complete Clinical Study Report in minutes rather than weeks.”
Transparency Evidence & methodology 100/100 reference value · 89% 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 value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/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
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • 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. MongoDB

    Novo Nordisk customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/novo-nordisk
    Source type
    Vendor-published customer story
    Published
    Dec 21, 2025
    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

  • Published on source page Dec 21, 2025 · MongoDB · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.