Papers › DeepLesion: Automated Deep Mining, Categorization and Detection of Significant...

DeepLesion: Automated Deep Mining, Categorization and Detection of Significant Radiology Image Findings using Large-Scale Clinical Lesion Annotations

4 Oct 2017arXiv:1710.01766archive 2025-07-28

Ke Yan, Xiaosong Wang, Le Lu, Ronald M. Summers

Extracting, harvesting and building large-scale annotated radiological image datasets is a greatly important yet challenging problem. It is also the bottleneck to designing more effective data-hungry computing paradigms (e.g., deep learning) for medical image analysis. Yet, vast amounts of clinical annotations (usually associated with disease image findings and marked using arrows, lines, lesion diameters, segmentation, etc.) have been collected over several decades and stored in hospitals' Picture Archiving and Communication Systems. In this paper, we mine and harvest one major type of clinical annotation data - lesion diameters annotated on bookmarked images - to learn an effective multi-class lesion detector via unsupervised and supervised deep Convolutional Neural Networks (CNN). Our dataset is composed of 33,688 bookmarked radiology images from 10,825 studies of 4,477 unique patients. For every bookmarked image, a bounding box is created to cover the target lesion based on its measured diameters. We categorize the collection of lesions using an unsupervised deep mining scheme to generate clustered pseudo lesion labels. Next, we adopt a regional-CNN method to detect lesions of multiple categories, regardless of missing annotations (normally only one lesion is annotated, despite the presence of multiple co-existing findings). Our integrated mining, categorization and detection framework is validated with promising empirical results, as a scalable, universal or multi-purpose CAD paradigm built upon abundant retrospective medical data. Furthermore, we demonstrate that detection accuracy can be significantly improved by incorporating pseudo lesion labels (e.g., Liver lesion/tumor, Lung nodule/tumor, Abdomen lesions, Chest lymph node and others). This dataset will be made publicly available (under the open science initiative).

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 11 samples from 1 repository, 11 ran (11 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-25 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Masaaki-75/proct mentioned on GitHubpytorchMITSyntology: 11 samples, 11 ran (0 instrument-failed) · 0 unverified report
mtcazzolato/featset mentioned on GitHubGPL-3.0Syntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

11ran

Licence: 0 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from Masaaki-75/proct. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

Masaaki-75/proct community (archive-listed) 11 samples, 11 ran (0 instrument-failed) · 0 unverified
build_sincos2d_pos_embed modules/rope.py ran MIT (permissive) · bb04d14701260c0f · report fixture: signature feat_shape:list/1/int, dim:int/0/int, temperature:float/0/float, reverse_coord:bool/0/bool, interleave_sin_cos:bool/0/bool, dtype:dtype/0/?, device:NoneType/0/? · returned Tensor · level recorded 2026-09-26
forward_channel_last modules/basic_layers.py ran MIT (permissive) · 0e211f4654d783be · report fixture: signature module:callable/0/?, x:Tensor/4/float, keep_shape:bool/0/bool · returned Tensor · level recorded 2026-09-26
forward_channel_second modules/basic_layers.py ran MIT (permissive) · 799fe50f1f9e224c · report fixture: signature module:callable/0/?, x:Tensor/3/float, x_size:tuple/1/int · returned Tensor · level recorded 2026-09-26
freq_bands modules/rope.py ran MIT (permissive) · 968a74d4e1310a55 · report fixture: signature num_bands:int/0/int, temperature:float/0/float, step:int/0/int, device:NoneType/0/? · returned Tensor · level recorded 2026-09-26
gaussian in 218 papers
census: 8 implementations from 9 papers, 8 distinct outputs across 4 buckets, one shared input per bucket
utilities/rec_loss.py ran fingerprinted MIT (permissive) · 0d209028c2dee969 · report fixture: signature window_size:int/0/int, sigma:float/0/float · returned Tensor · level recorded 2026-09-25
get_conv_block modules/basic_layers.py ran MIT (permissive) · c6e8792591fbec4c · report fixture: signature in_channels:int/0/int, out_channels:int/0/int, kernel_size:int/0/int, stride:int/0/int, padding:int/0/int, dilation:int/0/int, groups:int/0/int, bias:bool/0/bool, is_transposed:bool/0/bool, output_padding:int/0/int, padding_mode:str/0/str, spatial_dims:int/0/int, conv_type:NoneType/0/? · returned Sequential · level recorded 2026-09-26
get_metrics in 46 papers utilities/rec_loss.py ran MIT (permissive) · 8bf3319a7b1db318 · report fixture: signature preds:Tensor/4/float, labels:Tensor/4/float, val_range:int/0/int, eps:float/0/float, window_size:int/0/int · returned tuple · level recorded 2026-09-26
get_mse in 5 papers utilities/rec_loss.py ran fingerprinted MIT (permissive) · 363dfe1b7fa7f2ba · report fixture: signature img1:Tensor/2/float, img2:Tensor/2/float · returned Tensor · level recorded 2026-09-26
pixel_freq_bands modules/rope.py ran MIT (permissive) · 025f4d123711b4e5 · report fixture: signature num_bands:int/0/int, max_freq:float/0/float, linear_bands:bool/0/bool, device:NoneType/0/? · returned Tensor · level recorded 2026-09-26
poly_lr trainers/basic_trainer.py ran fingerprinted MIT (permissive) · 6de2f712f7f3e0a1 · report fixture: signature epoch:int/0/int, max_epochs:int/0/int, initial_lr:float/0/float, exponent:float/0/float · returned float · level recorded 2026-09-26
vmap sources/proct.py ran MIT (permissive) · 413b87f93f023198 · report fixture: signature module:callable/0/?, x:Tensor/3/float, args:tuple/1/empty, kwargs:dict/0/? · returned Tensor · level recorded 2026-09-26

Tasks

Lesion SegmentationMedical Image Analysis

Datasets

Introduced by this paper, per the archive.

DeepLesion

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections