DEV Community

Scott Shoemaker
Scott Shoemaker

Posted on

MedReachAI: Bringing Data Intelligence to Healthcare Provider Management

The Messy Reality of Healthcare Data (The Problem)
When people hear the phrase "healthcare data," they immediately think of patient records—blood pressure, clinical notes, and heart rates. But there is an entirely different side to the industry that is just as critical, and often just as messy: Provider Data.

Healthcare organizations, compliance officers, and medical sales teams rely on massive datasets of physician credentials, practice locations, and financial relationships. However, this data is notoriously unstructured. It suffers from a few major problems:

Corruption & Duplication: Provider databases are often cobbled together through web-scraping or manual entry. This leads to duplicate profiles, mismatched specialties, and corrupted National Provider Identifiers (NPIs).

Hidden Security Risks: Free-text fields (like notes or contact arrays) frequently harbor Protected Health Information (PHI) or Personally Identifiable Information (PII), creating massive compliance liabilities.

Financial Blind Spots: Without a clean, verified NPI, it is impossible to track a physician's financial relationships under the federal Sunshine Act.

The industry needs a way to automatically ingest, sanitize, and secure this provider data before it ever hits a production database.

(Caption: Raw healthcare provider datasets are often riddled with structural errors and hidden compliance risks.)

Enter MedReachAI (The Solution)
Over the past few months, my capstone partner, Collin, and I have been building MedReachAI: an automated, full-stack data intelligence platform designed specifically to sanitize and enrich healthcare provider profiles.

Rather than relying on humans to manually comb through spreadsheets, we engineered a backend pipeline using Python, FastAPI, and machine learning to do the heavy lifting.

Here is a look at the core features driving the MedReachAI backend:

  1. Unsupervised Anomaly Detection
    To catch corrupted data, I engineered a machine learning model using Scikit-Learn’s IsolationForest. Because provider data changes dynamically, we don't rely on a static training set. Instead, the algorithm evaluates each new upload batch in real-time, calculates the mathematical distance between provider profiles, and automatically isolates the top 5% most irregular records (such as geographic mismatches or structural scraping errors).

  2. Automated PII & PHI Redaction
    To handle security, I integrated the Microsoft Presidio AnalyzerEngine. I built custom pattern recognizers that scan unstructured text to detect Medical Record Numbers (MRNs) alongside standard identifiers like SSNs and emails. Once detected, our downstream Anonymizer service actively scrubs the data, replacing the sensitive text with explicit tags like .

(Caption: The MedReachAI backend utilizes custom Python services to flag statistical anomalies and redact sensitive information in real-time.)

  1. Non-Destructive Data Deduplication
    To ensure our analytics remain accurate, I built a custom Pandas algorithm to identify exact and partial duplicate provider profiles. Instead of deleting these records and risking data loss, the system performs a "soft delete" by appending a boolean flag to the database row, allowing the data to be recovered if needed.

  2. The Human-in-the-Loop Dashboard
    While the backend handles the automation, Collin built a brilliant React-based UI that gives the user final oversight. The MedReachAI dashboard features a suite of review tabs that allow end-users to manually accept or reject the anomaly, duplication, and PII flags generated by the backend.

(Caption: The MedReachAI dashboard provides end-users with real-time visibility into the health and cleanliness of their provider datasets.)

What’s Next?
With the core data-cleaning pipeline fully operational, Phase C of our development will focus on external enrichment. I will be building asynchronous clients to connect our clean local records directly to the official CMS NPI Registry and the CMS Open Payments database, turning sparse, sanitized records into rich, compliant provider profiles.

Building MedReachAI has been an incredible exercise in bridging the gap between raw data engineering and user-facing application design. Stay tuned as we wrap up our final features!

Top comments (0)