Papers › MONAI: An open-source framework for deep learning in healthcare

MONAI: An open-source framework for deep learning in healthcare

4 Nov 2022arXiv:2211.02701archive 2025-07-28

M. Jorge Cardoso, Wenqi Li, Richard Brown, Nic Ma, Eric Kerfoot, Yiheng Wang, Benjamin Murrey, Can Zhao, Dong Yang, Vishwesh Nath, Yufan He, Ziyue Xu, Ali Hatamizadeh, Andriy Myronenko, Wentao Zhu, Yun Liu, Mingxin Zheng, Yucheng Tang, Isaac Yang, Michael Zephyr, Behrooz Hashemian, Sachidanand Alle, Mohammad Zalbagi Darestani, Charlie Budd, Marc Modat, Tom Vercauteren, Guotai Wang, Yiwen Li, Yipeng Hu, Yunguan Fu, Benjamin Gorman, Hans Johnson, Brad Genereaux, Barbaros S. Erdal, Vikash Gupta, Andres Diaz-Pinto, Andre Dourson, Lena Maier-Hein, Paul F. Jaeger, Michael Baumgartner, Jayashree Kalpathy-Cramer, Mona Flores, Justin Kirby, Lee A. D. Cooper, Holger R. Roth, Daguang Xu, David Bericat, Ralf Floca, S. Kevin Zhou, Haris Shuaib, Keyvan Farahani, Klaus H. Maier-Hein, Stephen Aylward, Prerna Dogra, Sebastien Ourselin, Andrew Feng

Artificial Intelligence (AI) is having a tremendous impact across most areas of science. Applications of AI in healthcare have the potential to improve our ability to detect, diagnose, prognose, and intervene on human disease. For AI models to be used clinically, they need to be made safe, reproducible and robust, and the underlying software framework must be aware of the particularities (e.g. geometry, physiology, physics) of medical data being processed. This work introduces MONAI, a freely available, community-supported, and consortium-led PyTorch-based framework for deep learning in healthcare. MONAI extends PyTorch to support medical data, with a particular focus on imaging, and provide purpose-specific AI model architectures, transformations and utilities that streamline the development and deployment of medical AI models. MONAI follows best practices for software-development, providing an easy-to-use, robust, well-documented, and well-tested software framework. MONAI preserves the simple, additive, and compositional approach of its underlying PyTorch libraries. MONAI is being used by and receiving contributions from research, clinical and industrial teams from around the world, who are pursuing applications spanning nearly every aspect of healthcare.

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

No sample from the archive's official repository (Project-MONAI/MONAI) is linked to this paper; the 10 samples below come from 1 community repository. Syntology harvested code from Project-MONAI/MONAI for another paper.

Project-MONAI/MONAI: Syntology's graph links these samples to SwiFT: Swin 4D fMRI Transformer (arXiv:2307.05916; that paper's own run record: 25 ran (of which 4 constructed an object rather than computing a result; 16 with no instrument failure: 0 honoured, 0 violated, 16 with no contract checked; 9 where Syntology's instrument failed) · 17 unverified); nothing checks that they implement this paper's method.

Syntology 10 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 10 samples from 1 repository, 9 ran (6 with no instrument failure; 3 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 9 samples that ran has no recorded date.

Project-MONAI/MONAI officialmentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to SwiFT: Swin 4D fMRI Transformer (arXiv:2307.05916; that paper's own run record: 25 ran (of which 4 constructed an object rather than computing a result; 16 with no instrument failure: 0 honoured, 0 violated, 16 with no contract checked; 9 where Syntology's instrument failed) · 17 unverified); nothing checks that they implement this paper's method. report
yaziciz/GLIMS mentioned on GitHubpytorchMITSyntology: 10 samples, 9 ran (3 instrument-failed) · 1 unverified 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

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

2ran · our draft was wrong
1ran; the contract check could not run
6ran
1unverified

Licence: 3 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from yaziciz/GLIMS. “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.

yaziciz/GLIMS community (archive-listed) 10 samples, 9 ran (3 instrument-failed) · 1 unverified
datafold_read utils/data_utils.py ran MIT (permissive) · ea8666acff12eb5e · report fixture: signature datalist:str/0/str, basedir:str/0/str, fold:int/0/int, key:str/0/str · returned tuple · level recorded 2026-09-25
distributed_all_gather utils/utils.py ran MIT (permissive) here; the stored copy is pointer only · 8b18111ad2f880f7 · report fixture: signature tensor_list:list/1/Tensor, valid_batch_size:int/0/int, out_numpy:bool/0/bool, world_size:int/0/int, no_barrier:bool/0/bool, is_valid:NoneType/0/? · returned list · level recorded 2026-09-24
get_conv_layer in 7 papers Modules/conv_generator.py ran MIT (permissive) · 4da4c81b5bbdc532 · report fixture: signature spatial_dims:int/0/int, in_channels:int/0/int, out_channels:int/0/int, kernel_size:int/0/int, stride:int/0/int, act:str/0/str, norm:str/0/str, dropout:NoneType/0/?, bias:bool/0/bool, conv_only:bool/0/bool, is_transposed:bool/0/bool, dilation:int/0/int, padding:int/0/int, output_padding:int/0/int · returned Convolution · level recorded 2026-09-25
get_output_padding Modules/conv_generator.py ran fingerprinted MIT (permissive) · 7e128ead08e94304 · report fixture: signature kernel_size:int/0/int, stride:int/0/int, padding:int/0/int · returned int · level recorded 2026-09-25
get_padding in 84 papers Modules/conv_generator.py ran MIT (permissive) · 3d2504e21805394d · report fixture: signature kernel_size:list/1/int, stride:list/1/int · returned tuple · level recorded 2026-09-25
get_window_size in 21 papers GLIMS.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed MIT (permissive) · 34484ba7deb03520 · report fixture: signature x_size:tuple/1/int, window_size:tuple/1/int, shift_size:tuple/1/int · returned tuple · level recorded, date not recorded
logsumexp_2d in 14 papers Modules/CSAB.py ran · our draft was wrong fingerprinted MIT (permissive) · 7abfa32a2f1d7424 · report fixture: signature tensor:Tensor/3/float · returned Tensor · level recorded 2026-09-22
window_partition in 377 papers
census: 13 implementations from 17 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
GLIMS.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 8cd5fa7e1d693a92 · report fixture: signature x:Tensor/4/float, window_size:tuple/1/int · returned Tensor · level recorded 2026-09-26
window_reverse in 296 papers GLIMS.py ran MIT (permissive) here; the stored copy is pointer only · 1545b891ff0bbdd7 · report fixture: signature windows:Tensor/5/float, window_size:tuple/1/int, dims:tuple/1/int · returned Tensor · level recorded 2026-09-26
get_loader in 62 papers utils/data_utils.py unverified MIT (permissive) · 4f0846ad1f425220 · report

Tasks

Deep LearningMedical Image ClassificationMedical Image RegistrationMedical Image Segmentationmedical image detection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AWARE

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