Snowflake Healthcare Boston, Massachusetts

OM1

Application Refactoring

simplify a compute-heavy healthcare data ecosystem spread across AWS, Databricks, and custom software so OM1 could deploy ML code faster, reduce maintenance, and keep PHI redaction efficient.

100M+ clinical records redacted in less than 30 minutes to protect patient privacy
75% savings in processing costs using Snowpark Container Services to redact PII data

Reported impact

Business outcome

OM1 achieved 75% savings in processing costs using Snowpark Container Services to redact PII data and 100M+ clinical records redacted in less than 30 minutes to protect patient privacy.

  • Cost Reduction
  • Productivity Improvement
  • Risk Reduction

Solution

OM1 uses Snowflake, Snowpark, and Snowpark Container Services on Snowflake to simplify a compute-heavy healthcare data ecosystem spread across AWS, Databricks, and custom software so OM1 could deploy ML code faster, reduce maintenance, and keep PHI redaction efficient. Patient, claims, and clinician-note data are centralized in Snowflake so data engineers, clinical researchers, and ML teams can work from a faster, more reliable operating view. Snowpark keeps transformation and application logic close to the governed data instead of forcing the team to move workloads into separate compute environments. Keeping ingestion, storage, transformation, and governed access on one platform reduces handoffs, simplifies operations, and makes it easier to reuse trusted data across analytics, reporting, and AI. OM1 achieved 75% savings in processing costs using Snowpark Container Services to redact PII data and 100M+ clinical records redacted in less than 30 minutes to protect patient privacy.

Data flow

patient, claims, and clinician-note data flow into Snowflake, Snowpark, and Snowpark Container Services; curated data, reports, and model outputs are then served to data engineers, clinical researchers, and ML teams.

Solution architecture

3 components · 2 layers
  1. Compute
    • Snowpark Runs transformations, analytics, and application logic directly where Snowflake data already lives.
    • Snowpark Container Services Runs containerized ML, privacy, or application workloads directly against Snowflake-managed data.
  2. Storage
    • Snowflake Provides the centralized data platform that stores governed datasets and serves analytics or AI workloads.

Architecture clues

  • Integrates with AWS, dbt, Modelbit, Hex as part of the broader delivery workflow.
  • Operates at the scale described by metrics such as 75% savings in processing costs using Snowpark Container Services to redact PII data.
  • Snowpark Container Services handles specialized privacy or model workloads directly against the same managed data foundation.
  • Snowpark keeps transformation and application logic close to the governed data instead of forcing the team to move workloads into separate compute environments.

Evidence from the source

100M+ clinical records redacted in less than 30 minutes to protect patient privacy
75% savings in processing costs using Snowpark Container Services to redact PII data
OM1 achieved 75% savings in processing costs using Snowpark Container Services to redact PII data and 100M+ clinical records redacted in less than 30 minutes to protect patient privacy
The sheer size and complexity of OM1’s data sets require a reliable, scalable platform to meet the industry’s rigorous demands for privacy, accuracy and credibility
To deliver real-world insights from bench to bedside, OM1 moved its complex ecosystem spread across AWS, Databricks and custom software — and discovered newfound simplicity and efficiency in the process
Transparency Evidence & methodology 100/100 reference value · 79% 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
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • 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. Snowflake

    OM1 customer story

    First-party
    https://www.snowflake.com/en/customers/all-customers/case-study/om1/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived May 24, 2025 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jul 11, 2026 · Snowflake · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.