MongoDB Healthcare Denmark

Novo Nordisk

Document Processing

Novo Nordisk needed to shorten the slow and error-prone process for producing clinical study reports while keeping document generation deterministic and regulator-friendly in a tightly controlled pharmaceutical environment.

"MongoDB has helped us cut writing times by 90%"
"a document that can be up to 300 pages long"
"can take the company up to 19 weeks"
"just three full-time staff instead of 42"

Reported impact

Business outcome

MongoDB helped Novo Nordisk cut report-writing times by 90%, reduce staffing required for CSR creation, and produce regulator-friendly drafts far faster while keeping humans in control.

  • Compliance
  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

Novo Nordisk built NovoScribe on MongoDB Atlas to support structured authoring for clinical study reports. Atlas stores approved text snippets, vectors, and case-specific trial data such as tables, lists, statistical outputs, and analytical results. The application uses a prompt-search-retrieval loop built around large language models and retrieval-augmented generation: Atlas retrieves relevant approved passages, the system presents five candidate text options to a human reviewer, and the chosen language is written back to the database before the next document section is assembled. That pattern keeps a human in the loop while still automating repetitive authoring work in a regulated setting where deterministic output matters. By combining reusable content modules with study-specific data inside Atlas, NovoScribe can build long CSR drafts section by section in minutes instead of weeks while reducing manual rework and keeping scientific staff focused on higher-value review work.

Data flow

Approved text snippets and trial data are stored in MongoDB Atlas, the application retrieves relevant context for each prompt, a human reviewer selects from five candidate passages, and NovoScribe assembles report sections into a complete clinical study report.

Solution architecture

1 components · 1 layer
  1. Storage
    • MongoDB Atlas Stores approved text, vectors, and study data and supports the retrieval workflow that assembles clinical study reports.

Architecture clues

  • Human reviewers choose from five candidate passages before content is committed.
  • NovoScribe uses LLMs, vectors, and retrieval-augmented generation on top of MongoDB Atlas.
  • Structured authoring reuses approved text snippets across documents.

Evidence from the source

"LLMs are probabilistic models, but pharmaceuticals [are] very tightly regulated, so we can't just assume that the model does the right thing."
"MongoDB has helped us cut writing times by 90%."
"There are plenty of other parts of the process that still need human thought and scientific input, so it's great to be able to pass the repetitive tasks on to computers."
"We need deterministic and clear outcomes, so we introduced an intermediate step where a human reviews five possible pieces of text and chooses the best one."
Transparency Evidence & methodology 90/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 value90/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
    3 metrics describe measurable impact.
  • Deployment scale5/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-atlas
    Source type
    Vendor-published customer story
    Published
    May 23, 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 May 23, 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.