Journal of the American Medical Informatics Association Submission Guide

Source: the JIF, 5-year JIF and CiteScore rows are the 2025 values on the journal's About page (Clarivate and Scopus, read 2026-10-10); the About page and instructions publish no acceptance rate, desk-rejection rate or first-decision median.

Source: JAMIA author guidelines.

Use this page when deciding:

• whether the informatics contribution is substantive

• whether evaluation is rigorous

• whether the methodology is grounded in informatics-research frameworks

• a clear informatics contribution (method, system, evaluation framework)

• rigorous evaluation against baseline approaches

• methodology grounded in informatics-research frameworks

• reproducibility materials (code, data, evaluation protocol)

• a cover letter establishing the informatics contribution

• Descriptive system reports without rigorous evaluation.

• Missing comparison to baseline approaches.

• Weak informatics-research framing.

• Clinical research without informatics contribution.

JAMIA is the flagship medical-informatics journal.

Evaluation-first standard: the journal differentiates from clinical journals by demanding rigorous informatics evaluation.

Methodological-framework expectation: editors expect grounding in informatics-research methodology.

The initial editorial screen: decisive.

The strongest JAMIA cover letters establish:

• the informatics contribution

• the evaluation methodology and baseline comparison

• the methodological framing

• the reproducibility scope

Disclose related work and earlier editorial history

JAMIA's Instructions to Authors

also ask the cover letter to flag special considerations. State any related

papers by the same authors that are published or under consideration, and

identify any previous reviews of the submitted article. If earlier editor or

reviewer comments, author responses, or related papers would clarify the

submission history, upload them as an editor-only supplementary file. Do not

hide overlap or a prior decision behind a generic novelty claim.

Method note: the comparison reflects published author guidelines and Manusights internal analysis. We have not personally been JAMIA authors; the boundary is publicly documented editorial behavior. Pros and cons are based on documented editorial scope.

JAMIA's instructions call for these in the submission package:

• Cover letter informing the Editor of special considerations, including related papers by the same authors and details of previous reviews (our advice, not a journal requirement: also state the informatics contribution and the rigorous evaluation evidence)

• Declaration of competing interests for all authors

• Data availability statement (a requirement for articles published in JAMIA); authors can deposit data in Dryad at no charge

• CRediT contributor roles for each author (supplied at submission)

• Plagiarism screening: papers submitted to the journal are screened with Similarity Check / iThenticate

• Image integrity: manuscripts may also be screened, including with third-party services, for inappropriate image alteration and papermill activity

For JAMIA submissions, the most common artifact-related desk-reject is descriptive system reports without rigorous evaluation. JAMIA's instructions describe Research and Applications as original work in the formulation, implementation, or evaluation of informatics-based studies, so a clinical informatics system presented without quantified outcome evaluation or implementation-effectiveness data is a weak fit.

For JAMIA submissions, the editorial timeline runs through four phases. The journal publishes no acceptance rate or desk-rejection rate, and the stage ranges below are Manusights planning estimates, not JAMIA figures. The instructions say papers are screened for plagiarism with Similarity Check / iThenticate and may also be screened for image alteration and papermill activity.

Day 0 to 7: ScholarOne intake and integrity screening

ScholarOne intake handles format compliance, and submissions are also screened with iThenticate and may be checked for image-integrity and papermill issues. Biomedical informatics papers route to subject editors matching the domain (clinical decision support, public health informatics, consumer health, imaging informatics, NLP, EHR). The most common Day 0-7 hold-up: plagiarism flags from uncited reuse of prior conference work or methods text.

Day 7 to 28: Editor scope and evaluation-rigor screen

JAMIA's editor filter prioritizes substantive informatics contributions with rigorous quantified evaluation. The most common Day 7-28 desk reject in our review work: descriptive system reports (presenting a clinical informatics tool without outcome evaluation, implementation metrics, or usability evidence beyond qualitative claims).

Week 4 to 12: Peer review

JAMIA does not publish a reviewer count or a first-decision target. Reviewer mix typically includes one informatics-methodologist plus one clinical-domain or implementation-science specialist. Submissions missing comparator-system benchmarks, effect-size analysis, or implementation-context data extend reviewer dialogue by 3-5 weeks.

Week 12 to 24: Decision, revision, and production

JAMIA publishes no revision-round or submission-to-acceptance figures. The journal is hybrid: after acceptance you choose either an open access licence, for which you pay an open access charge, or standard subscription-based access, for which you are not charged.

• Is JAMIA a good journal?

Before upload, run your manuscript through a JAMIA evaluation rigor readiness check.

This guide tells you what Journal of the American Medical Informatics Association editors look for; the review tells you whether your paper clears the informatics-contribution and evaluation check before upload. Manusights checks are covered by a 60-day money-back guarantee, and we do not train models on submitted manuscripts.

The clinical system report without an informatics contribution

Across medical-informatics manuscripts targeting JAMIA, the most common failure pattern is a useful clinical or operational system report that never becomes a medical-informatics research contribution. The manuscript describes an EHR workflow, decision-support tool, NLP pipeline, dashboard, registry, patient portal, imaging workflow, or implementation project, but the abstract and introduction frame the result as "we built and deployed" rather than "we answer an informatics research question."

For JAMIA, the title, abstract, methods, and discussion need to make the informatics contribution explicit. That contribution might be a reusable evaluation framework, a validated algorithmic method, a learning-health-system implementation insight, a clinical decision-support design principle, a data-quality method, or an interoperability lesson that travels beyond the local site.

The cover letter should explain why the work belongs in JAMIA rather than Journal of Biomedical Informatics, Applied Clinical Informatics, International Journal of Medical Informatics, npj Digital Medicine, or a specialty clinical journal. If the manuscript components only show local deployment, the page-one pitch is too narrow.

Check whether your JAMIA manuscript has a real informatics contribution →

The evaluation section that reports performance without a baseline

For manuscripts targeting JAMIA, weak evaluation design is the pattern that most reliably turns a promising informatics paper into a fragile submission. Authors often provide model performance, user satisfaction, adoption counts, usability themes, or workflow metrics, but the methods section does not show a credible comparator, baseline, outcome definition, sample-size logic, statistical analysis plan, or implementation context.

JAMIA's author guidance emphasizes biomedical and health informatics research, and Oxford's data policy requires a Data Availability Statement for published JAMIA articles. That means evaluation and reproducibility are not optional polish. The manuscript should state what baseline approach the new system improves on, which metrics matter, how uncertainty is reported, what data were available for replication, and how the implementation setting limits interpretation.

A strong JAMIA package makes the evaluation legible in the abstract, the methods, the first results table, and the supplementary protocol. A weak package asks editors to infer that rigor from enthusiasm about the system.

Check whether your JAMIA evaluation design is strong enough for editorial screening →

The reproducibility package that cannot support the claim

Across JAMIA-targeted manuscripts, a third repeat problem is a reproducibility layer that is weaker than the claimed contribution. This shows up as missing code availability, unclear data-access restrictions, incomplete feature definitions, under-specified annotation protocols, absent model-card style details, sparse error analysis, thin fairness or subgroup checks, or supplementary files that do not let readers reconstruct the informatics workflow.

For JAMIA, these manuscript components matter because the journal's readers are not only asking whether a tool worked in one health system. They are asking whether the method, implementation lesson, data representation, or evaluation approach can be understood, trusted, and adapted by other informatics teams. The references should place the work in the JAMIA conversation, not just in clinical domain literature.

The discussion should separate what the system proves from what remains local, proprietary, retrospective, underpowered, or institution-specific. That separation is what makes a manuscript feel like research rather than product reporting.

Check whether your JAMIA reproducibility package supports the informatics claim →

Before the reviewer-invitation stage, read the Journal of the American Medical Informatics Association package against the same risks this guide flags in the Manusights section. If the components disagree about the target, the editor notices before the reviewer does.

• If the abstract still points toward clinical system report without an informatics contribution, revise the central claim before upload.

• If the evidence package leaves evaluation section that reports performance without a baseline, strengthen the methods, controls, figures, or supplementary material rather than expecting reviewers to infer it.

• If the cover letter cannot resolve reproducibility package that cannot support the claim, compare the target journal against the adjacent venues named above before submitting.

In pre-submission diagnostic work for top medical-informatics journals, we consistently see four signals that distinguish strong submissions from weak ones. First, the contribution must be substantive, not descriptive; submissions reporting system implementation without rigorous evaluation fail at desk screening. Second, evaluation should compare against baseline approaches with appropriate metrics. Third, methodology should be grounded in established informatics-research frameworks. Fourth, reproducibility materials (code, data, evaluation protocol) should be available.

For JAMIA-targeted manuscripts, the single most consistent feedback class we deliver in pre-submission diagnostics for JAMIA is the descriptive-versus-evaluative distinction. JAMIA editors expect rigorous evaluation, not just system descriptions. Submissions framed as "we developed system X and report user satisfaction" routinely receive "where is the rigorous evaluation?" feedback during desk screening.

We coach authors to lead with the evaluation question and frame the system in service of that question. Papers framed as "we evaluated whether system X improves clinical decision-making compared to baseline approach Y, using outcomes Z in setting W" receive better editorial traction.

The same logic applies across rigorous medical-informatics journals: editors are operating with limited slot inventory, and the submissions that get traction lead with the evaluation question.

For JAMIA-targeted manuscripts, beyond the rubric checks, three pre-submission diagnostic patterns recur most often in the manuscripts we review for JAMIA. First, manuscripts where the abstract emphasizes system features rather than evaluation are flagged at desk for descriptive framing. We recommend the abstract's central sentences state the evaluation question, the comparison approach, and the outcomes measured. Second, manuscripts where evaluation is reported without baseline comparison are flagged for evaluation gaps.

We recommend explicit comparison against at least one established baseline. Third, manuscripts that lack engagement with JAMIA's recent issues are at risk of being told the contribution does not fit the publication conversation.

For JAMIA-targeted manuscripts, the strongest manuscripts we coach distinguish themselves on three operational behaviors. First, they confine the cover letter to one page and use it to make the case for fit, contribution, and evaluation rigor. Second, they include a one-sentence elevator pitch in the cover letter's opening that the editor can use when discussing the manuscript internally. Third, they identify the specific recent JAMIA articles that this manuscript builds on and the specific informatics gap the work addresses.

Beyond the rubric checks, we observe that submissions framing the contribution as "we built and evaluated system X using established informatics-research framework Y, comparing against baseline Z" land more often than submissions framing the contribution as "we developed a new system to address clinical problem X." The framing distinction signals that the manuscript is operating inside the informatics-research conversation rather than treating informatics as a tool for clinical research.

The strongest JAMIA submissions also include explicit discussion of informatics-evaluation methodology, treating evaluation as a first-class research contribution rather than a technical step.