Databricks Healthcare Mexico

Mendel

Customer Service Automation · Enterprise Knowledge Search

Mendel, an AI leader in healthcare and life sciences, tackles the challenges of fragmented clinical data with their HyperCube platform, which enables precision in tasks like clinical trial matching. However, the complexity of building disease-specific ontologies and managing data across multiple systems slowed progress.

3x faster
3x faster Model training to provide patient insights

Reported impact

Business outcome

Reported outcomes include 3x faster Model training to provide patient insights; 3x faster.

  • Compliance
  • Productivity Improvement

Solution

Mendel built its Databricks implementation around Agent Bricks, Databricks Data + AI Platform, Unity Catalog, Lakehouse Federation. Mendel, an AI leader in healthcare and life sciences, tackles the challenges of fragmented clinical data with their HyperCube platform, which enables precision in tasks like clinical trial matching. However, the complexity of building disease-specific ontologies and managing data across multiple systems slowed progress. Agent Bricks provides the agentic and generative AI runtime used to build domain-specific applications. Databricks Data + AI Platform provides the shared lakehouse environment for ingestion, engineering, analytics, and AI workflows in this deployment. Unity Catalog applies centralized governance, lineage, auditing, and access control across shared data assets. Lakehouse Federation lets teams query remote systems alongside lakehouse data without copying all source data first.

Data flow

Source data is ingested into databricks, curated in shared lakehouse tables, processed with Databricks compute and orchestration services, and exposed to downstream analytics and users.

Solution architecture

5 components · 4 layers
  1. Ingest
    • Lakehouse Federation Lets teams query remote systems alongside lakehouse data without copying all source data first.
  2. Compute
    • Agent Bricks Provides the agentic and generative AI runtime used to build domain-specific applications.
    • Llama 3.1 Supplies the base large language model used for domain-specific training or inference.
  3. Governance
    • Unity Catalog Applies centralized governance, lineage, auditing, and access control across shared data assets.
  4. Uncategorized
    • Databricks Data + AI Platform Provides the shared lakehouse environment for ingestion, engineering, analytics, and AI workflows in this deployment.

Architecture clues

  • Agent Bricks
  • Databricks Data + AI Platform
  • Lakehouse Federation
  • Model training to provide patient insights
  • Unity Catalog
  • lakehouse federation

Evidence from the source

3x faster
3x faster Model training to provide patient insights
Adding to the challenge, Mendel faced the daunting task of building disease-specific ontologies, essential for enabling semantic querying within clinical data. Developing these ontologies required extensive resources, including teams of dat
Looking ahead, Mendel plans to leverage Lakehouse Federation capabilities within Unity Catalog . This will enable Mendel to manage and audit data access seamlessly across multiple sources, ensuring that their federated queries are both secu
Mendel started with a partially trained model, continuing its training on public datasets before integrating their proprietary data — around 200 billion raw tokens — into the process. With help from Databricks, Mendel was able to unify thei
Transparency Evidence & methodology 91/100 reference value · 94% confidence · 2 sources

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 value91/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 specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    2 source references 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. Databricks

    Mendel customer story

    First-party
    https://www.databricks.com/customers/mendel
    Source type
    Vendor-published customer story
    Published
    Sep 26, 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
  2. Prospeo

    Mendel Overview, Address & Contact

    Independent secondary
    https://prospeo.io/c/mendel

    The page shows Headquarters "Mexico City, Mexico City, Mexico" and the embedded Organization data lists addressCountry "MX" with numberOfEmployees value 201.

    Source type
    Structured profile
    Supports
    • Region
    • Company size

Date evidence

  • Published on source page Sep 26, 2024 · Databricks · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.