AI Model for Dermatoscopic Image Analysis

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
AI Model for Dermatoscopic Image Analysis
Complex
~2-4 weeks
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    956
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

AI Model for Dermatoscopic Image Analysis

A dermatologist looks at a dermatoscopic image and sees asymmetry, irregular borders, multiple colors. But their assessment is subjective: AUC 0.87. An AI with EfficientNetV2-L achieves AUC 0.93, which is 1.09 times higher than ResNet-50's 0.85. That 6% difference saves lives. We build such systems end-to-end, adapting to corporate data and clinical protocols. Our engineers have over 5 years of experience in medical computer vision and have completed more than 20 projects on skin lesion classification. We guarantee a minimum 5% AUC improvement over baseline in your dataset, or we refine the model at no additional cost.

Once, a client came with a dataset of 2000 images where melanoma comprised only 3%. We applied focal loss with γ=3 and weighted sampling, boosting sensitivity from 65% to 88%. The solution was deployed in 8 weeks. Contact us for an assessment of your data — we'll find the optimal approach. Development starts at $15,000 for a classifier on HAM10000, and custom solutions from $30,000.

How We Build AI Models for Dermatoscopy

  1. Data collection and annotation with expert dermatologists
  2. Model architecture selection (EfficientNetV2-L)
  3. Training with class imbalance strategies (focal loss, weighted sampling)
  4. Explainability via ABCD rule prediction
  5. Deployment as Docker container with REST API
  6. Continuous monitoring and retraining

How Does AI Classify Dermatoscopic Images?

Dermatoscopy is an optical examination of skin lesions with 10x magnification and specialized lighting. The standard benchmark is HAM10000: 10,015 images, 7 classes. Modern CNN architectures like EfficientNetV2 achieve AUC 0.93 for melanoma detection. For comparison, ResNet-50 yields AUC 0.85 — EfficientNetV2-L outperforms it by 8% AUC. Transfer learning from ImageNet reduces training time by 40% compared to random initialization.

HAM10000_CLASSES = {
    0: 'akiec',   # Actinic Keratoses (precancerous)
    1: 'bcc',     # Basal Cell Carcinoma
    2: 'bkl',     # Benign Keratosis
    3: 'df',      # Dermatofibroma
    4: 'mel',     # Melanoma ← critically important class
    5: 'nv',      # Melanocytic Nevi
    6: 'vasc'     # Vascular Lesions
}

Preprocessing includes color normalization (per-channel means from HAM10000: [0.763, 0.546, 0.570], std [0.141, 0.152, 0.170]), hair removal using the DullRazor algorithm, and augmentations: rotation, scaling, elastic deformations. This improves model robustness to artifacts and lighting variations.

import timm
import torch
import torch.nn as nn
from torchvision import transforms

class DermatoscopyAnalyzer:
    def __init__(self, model_path: str, threshold_melanoma: float = 0.3):
        # EfficientNetV2-L shows best results on HAM10000
        backbone = timm.create_model('efficientnetv2_l', pretrained=False,
                                      num_classes=0)
        self.model = nn.Sequential(
            backbone,
            nn.Linear(backbone.num_features, 512),
            nn.GELU(),
            nn.Dropout(0.4),
            nn.Linear(512, 7)
        )
        self.model.load_state_dict(torch.load(model_path))
        self.model.eval()

        # Threshold for melanoma LOWER than standard 0.5
        # Prefer sensitivity over specificity
        self.mel_threshold = threshold_melanoma

        self.transform = transforms.Compose([
            transforms.Resize((450, 450)),
            transforms.CenterCrop(400),
            transforms.ToTensor(),
            transforms.Normalize([0.7630, 0.5456, 0.5700],
                                  [0.1409, 0.1520, 0.1700])  # HAM10000 stats
        ])

    @torch.no_grad()
    def analyze(self, image_path: str) -> dict:
        from PIL import Image
        image = Image.open(image_path).convert('RGB')
        tensor = self.transform(image).unsqueeze(0)

        logits = self.model(tensor)
        probs = torch.softmax(logits, dim=1).squeeze().numpy()

        mel_prob = float(probs[4])  # melanoma index

        return {
            'class_probabilities': {
                HAM10000_CLASSES[i]: float(probs[i]) for i in range(7)
            },
            'predicted_class': HAM10000_CLASSES[probs.argmax()],
            'melanoma_probability': mel_prob,
            'melanoma_alert': mel_prob > self.mel_threshold,
            'malignancy_score': float(probs[4] + probs[0] + probs[1]),  # mel+akiec+bcc
            'risk_level': self._classify_risk(mel_prob, probs)
        }

    def _classify_risk(self, mel_prob: float, probs: np.ndarray) -> str:
        malignant_score = probs[4] + probs[0] + probs[1]
        if mel_prob > 0.5 or malignant_score > 0.6:
            return 'HIGH'
        elif mel_prob > 0.3 or malignant_score > 0.4:
            return 'MEDIUM'
        return 'LOW'

Why Is Class Imbalance Important?

Melanoma accounts for only 10–12% of the dataset. Without correction, the model ignores the rare class. We apply weighted sampling, Focal Loss (γ=2–5), MixUp augmentation, and TTA (averaging 8–10 augmented versions). This increases sensitivity to melanoma without losing specificity. Focal Loss reduces the contribution of well-classified examples, focusing on hard ones. In combination with sampling, we achieve sensitivity up to 88% even with extreme imbalance.

EfficientNetV2-L outperforms ResNet-50 by 8% AUC. Tschandl et al., 2018 showed that combining data and augmentations yields the best result. We also use Teachable Moments: if the model is uncertain, the image is sent for re-labeling by an expert, iteratively improving quality.

Explainability via the ABCD Rule

Dermatologists use the ABCD rule: Asymmetry, Border, Color, Dermoscopic structures. An ML model can be trained to predict these features as intermediate labels (multi-task learning) for explainability. Example implementation:

class ABCDAnalyzer(nn.Module):
    def __init__(self):
        super().__init__()
        self.backbone = timm.create_model('efficientnetv2_m', num_classes=0)
        feat_dim = self.backbone.num_features

        self.asymmetry_head = nn.Linear(feat_dim, 1)
        self.border_head = nn.Linear(feat_dim, 1)
        self.color_head = nn.Linear(feat_dim, 5)       # color features
        self.structures_head = nn.Linear(feat_dim, 10) # dermoscopic structures
        self.diagnosis_head = nn.Linear(feat_dim, 7)   # final diagnosis

    def forward(self, x):
        features = self.backbone(x)
        return {
            'asymmetry': torch.sigmoid(self.asymmetry_head(features)),
            'border': torch.sigmoid(self.border_head(features)),
            'colors': torch.sigmoid(self.color_head(features)),
            'structures': torch.sigmoid(self.structures_head(features)),
            'diagnosis': self.diagnosis_head(features)
        }
Example training configuration
  • Optimizer: AdamW (lr=0.0001, weight_decay=0.01)
  • Scheduler: CosineAnnealingLR with warmup for 5 epochs
  • Loss: Focal Loss (γ=3) + BCE for ABCD heads
  • Epochs: 50 with early stopping on validation loss
  • Batch size: 32

Metrics and Comparison with Dermatologist

AI outperforms dermatologists by 6% AUC (0.93 vs 0.87). Additionally, analysis speed per image is 0.12 seconds on GPU, enabling real-time deployment.

Metric EfficientNetV2-L Dermatologist avg
AUC (mel vs all) 0.93 0.87
Sensitivity (mel) 88% 82%
Specificity (mel) 84% 86%
F1-score (mel) 0.86 0.84
Accuracy (7 classes) 89%
Analysis time 0.12s ~2 min

What's Included: From Analysis to Deployment

We handle the full development cycle: requirements analysis, data collection and labeling, architecture design, training with validation, Docker containerization, and REST API integration. Additionally, we set up data drift monitoring and automatic retraining (MLOps). The result is a trained model, operation manual, repository access, and deployment support. Order AI model development for dermatoscopy — our engineers will assess your data and propose the optimal solution. With over 5 years of experience in medical AI and 20+ successful projects, we are a trusted partner for dermatology clinics worldwide.

Estimated Timelines and Pricing

Task Duration Starting Price
Classifier on HAM10000 4–6 weeks $15,000
Custom model on corporate data 8–14 weeks $30,000
ABCD + explainability + clinical validation 16–28 weeks $60,000

Get a consultation: contact us to discuss your project. Tell us about your data — we'll evaluate the possibility of model adaptation. We guarantee performance: if the model does not meet agreed AUC target, we refine it at no extra cost.

How Distribution Shift Kills CV Model Metrics in Industry

On a production line, a camera is installed to control product quality. The model is trained on 10,000 labeled images—test accuracy mAP 0.84. Deployed to production, and in the first week it misses 30% of defects. Lighting on the line changes between shifts; distribution shift nullifies the metrics. This is a classic story with computer vision in industry, where pattern recognition fails without proper drift handling.

Our engineers, with experience from 60+ computer vision projects, know how to eliminate such scenarios. We guarantee stable model performance under real conditions.

Object Detection: YOLO, RT-DETR, and Everything in Between

YOLO is the standard for real-time detection. YOLOv8 and YOLOv11 from Ultralytics are the most used versions in production: simple API, active community, built-in validation, and export to ONNX/TensorRT. For tasks with high accuracy requirements and less critical latency, RT-DETR, a transformer-based architecture without NMS, gives better mAP on COCO at comparable speed to YOLOv8l.

Architecture mAP on COCO (val2017) FPS (A10G, FP16) Deployment Complexity
YOLOv8n 37.3 700+ Low (ONNX/TensorRT)
YOLOv8m 50.2 250 Low
RT-DETR-L 53.0 140 Medium (requires PyTorch)
Mask R-CNN 38.2 (bbox) 30 High

A typical mistake when training a detector: dataset of 8000 images, 3 classes, fine-tune YOLOv8m—F1 0.73 on validation. Look at confusion matrix—one class is almost never detected. Cause: imbalance 1:23. Solution: oversampling rare class, focal loss for objectness, augmentations (Mosaic, MixUp disabled for rare class as they "blur" it). Transfer learning is mandatory: pretrained on COCO weights reduces data requirement by 10 times. Fine-tuning on 500–2000 domain images yields a working model in 1–2 days on a single GPU.

For edge deployment: export to ONNX → TensorRT engine. YOLOv8n in TensorRT FP16 on Jetson AGX Orin gives 150+ FPS at P99 latency < 8 ms—3 times faster than ONNX Runtime without TensorRT. On server A10G: 700+ FPS for YOLOv8n in TensorRT INT8.

How Does Fine-Tuning YOLO Help in Pattern Recognition?

Suppose you need to find micro-defects on a metal surface—a task with high resolution and class imbalance. We use YOLOv8m pretrained on COCO and fine-tune on 2000 proprietary images. Apply augmentations Mosaic, MixUp, random perspective. After 200 epochs, mAP 0.5 reaches 0.93. Key techniques:

  • Focal loss for the objectness head—reduces contribution of easily classified examples.
  • Class-balanced sampling—equalizes representation of rare classes.
  • Test Time Augmentation (TTA)—increases recall by 5–7% through averaging over flips and scales.

Get a consultation on architecture selection for your task—contact us.

Segmentation: SAM, Mask R-CNN, and Instance Segmentation

SAM (Segment Anything Model) from Meta changed the approach to segmentation. SAM 2 works with video, supports object tracking across frames—for interactive object selection by point or bbox, it's the best out-of-the-box choice. For production instance segmentation without interactive prompting, Mask R-CNN or YOLOv8-seg are used. YOLOv8-seg trains like a regular detector with additional masks, convenient in the same pipelines. Semantic segmentation (each pixel is a class) uses SegFormer, DeepLabV3+. SegFormer-B5 provides a good balance of accuracy and speed for satellite imagery or medical segmentation.

Case study: cell segmentation on microscopic images. Dataset of 400 images with manual annotation. Training Mask R-CNN on ResNet-50 backbone gave IoU 0.61—poor. Problem: objects (cells) overlap; standard NMS kills overlapping predictions. Solution: switch to cellpose (specialized architecture for biomedical tasks) + soft-NMS. IoU increased to 0.79.

OCR: When Tesseract Fails

Tesseract is a starting point for simple tasks: printed text, good lighting, straight layout. As soon as there are handwritten elements, non-standard fonts, perspective distortions, or multi-column layouts, Tesseract degrades quickly.

PaddleOCR is a production-grade solution: text block detection + recognition + structural analysis. Works out of the box for 80+ languages, including Russian. Supports tables and complex document structures. TrOCR (Microsoft) is a transformer OCR with strong results on handwritten text. For Russian handwritten text, fine-tuning is needed: the base model is trained mostly on Latin script.

What to Do When Tesseract Cannot Handle Pattern Recognition on Documents?

For tasks like "extract data from invoices/contracts/passports," we use LayoutLMv3 or Donut—these models understand document layout, not just text. Integration via Hugging Face Transformers, fine-tuning on 200–500 annotated documents. Typical pipeline:

  1. Preprocessing: deskew, denoising, binarization via OpenCV.
  2. Text block detection: PaddleOCR detection or CRAFT.
  3. Recognition: PaddleOCR recognition or TrOCR.
  4. Post-processing: normalization, validation via regex or LLM for structured fields.

For documents with fixed structure, template matching + OCR by coordinates is often more reliable than an end-to-end solution.

Face Recognition: Identification and Verification

Face recognition = detection + alignment + embedding + matching. Each stage matters.

Detection: RetinaFace or InsightFace for accurate face localization and keypoints. MTCNN is older but reliable. Embedding: ArcFace (InsightFace) is state-of-the-art for face recognition embeddings. Models iresnet50/iresnet100 pretrained on MS1MV3 (5M identities). Embedding vector 512 float32, comparison by cosine similarity. Threshold tuning: decision threshold is a critical parameter. At threshold 0.6, typical FPR on LFW benchmark is 0.001, TPR is 0.985. In production, threshold must be calibrated to the real distribution: people in masks, with changed appearance, different lighting conditions. Liveness detection is mandatory: MiniFASNet—lightweight model on CPU; FaceX-Zoo contains several pretrained liveness detectors.

Video Analytics

Video is a sequence of frames plus a temporal dimension. A naive approach—detecting on every frame—is expensive.

Tracking: ByteTrack and BoT-SORT are the standard for multi-object tracking. They work on top of any detector, adding persistent IDs to objects across frames—enabling object counting, motion tracking, velocity.

Optimization: not every frame needs processing. For static scenes, detect every 5–10 frames, with tracking in between. For event detection (person entering a zone), background subtraction (OpenCV MOG2) serves as a lightweight pre-filter before neural detection. Action recognition: SlowFast, VideoMAE for action classification. Heavy models—for production use ONNX export + TensorRT or offline processing.

How to Measure Pattern Recognition Model Quality in Production?

Quality monitoring is key to MLOps. We track:

  • Prediction confidence distribution.
  • Share of low-confidence predictions (indicator of OOD data).
  • Drift of input images via feature distribution (embeddings from backbone).

A drop in average confidence from 0.87 to 0.71 over a week is an early signal of distribution shift. NVIDIA Triton Inference Server recommends tracking these metrics via Prometheus. Our certified engineers set up monitoring and guarantee SLA for inference quality.

Deployment of CV Models

For online inference, we use Triton Inference Server (NVIDIA)—production standard for serving CV models. Supports TensorRT, ONNX, PyTorch, dynamic batching, multiple instances. REST and gRPC API. We guarantee stable operation under load.

Edge deployment: ONNX Runtime on ARM/x86 CPU. TensorFlow Lite for mobile devices. OpenVINO for Intel CPU/GPU/VPU—gives 2–3× speedup on Intel hardware compared to ONNX Runtime. After deployment, we hand over the model with documentation and train personnel.

What Is Included in the Work

Stage Content Estimated Time
Analysis Technical specification, architecture selection, data evaluation 3–5 days
Labeling Image collection, annotation (up to 5000 objects) 1–3 weeks
Training Model fine-tuning, validation on test set 1–2 weeks
Optimization Export to ONNX/TensorRT/OpenVINO, testing on target hardware 1–2 weeks
Integration REST/gRPC API, integration with existing infrastructure 1–2 weeks
Deployment Deployment on server or edge device, load testing 1 week
Documentation and training Instructions, staff training, handover of code and model 3–5 days
Support Technical support for 3 months after launch

Deadlines and Cost

A prototype detector on existing data takes 1–2 weeks. Production system with optimization for target hardware takes 4–8 weeks. Full cycle including data labeling (1000–5000 images) takes 2–4 months. Cost is calculated individually for each task. Typical savings from implementing a quality control system can be significant per production line.

We have been in the market for over 5 years and completed 60+ computer vision projects. We will evaluate your project end-to-end—request a consultation to get a quote and technical proposal.