Pre-Submission Review for Health Services Research Papers

Health services reviewers often ask:

• what healthcare delivery problem is being solved?
• who can act on the finding?
• are setting, organization, payer, workforce, and patient-flow context clear?
• are EHR, claims, registry, survey, or administrative-data definitions auditable?
• are missingness, coding changes, clustering, and confounding handled?
• does the paper use the right reporting guideline?
• is implementation context integrated rather than decorative?
• are equity, access, and unintended consequences considered?
• does the target journal match the system, policy, quality, or implementation contribution?

The result has to be useful in a real healthcare system, not only statistically significant.

In our pre-submission review work, health services manuscripts most often fail when the analysis is technically competent but operationally underinterpreted.

System context gap: the paper reports utilization, quality, or access outcomes without enough detail about the system that generated them.

Administrative-data opacity: codes, attribution rules, eligibility, enrollment, visits, or episodes are hard to audit.

Decision-maker blur: the manuscript never clarifies whether the audience is a health system, payer, clinician, manager, public agency, or researcher.

Implementation thinness: an intervention or care-process change is described without fidelity, adaptation, workflow, or feasibility context.

Equity afterthought: subgroup or access effects appear late, without shaping interpretation.

A useful review should identify whether the paper's main risk is data trust, system context, implementation, or audience fit.

Journal of Health Services Research & Policy says it publishes scientific research on health services, health systems, and healthcare from a wide range of disciplines. Its guidance also mentions research data sharing policy and statistical reporting guidance. Implementation Science expects theories and frameworks to inform aims, data collection, analysis, findings, and contribution, and requires populated reporting checklists for submitted manuscripts.

BMJ reporting guidance points authors to design-specific reporting guidelines, including STROBE and RECORD for observational studies using routinely collected health data. Those expectations matter heavily for health services work using EHR or claims data.

Send the manuscript, target journal, protocol, reporting checklist, data dictionary, code lists, cohort definitions, inclusion and exclusion criteria, health-system context, intervention or workflow materials, statistical analysis plan, equity variables, data statement, and prior reviewer comments if available.

If the paper uses routinely collected health data, include the exact coding, time windows, attribution logic, and data-quality checks.

A useful health services research pre-submission review should include:

• healthcare-delivery contribution verdict
• data-definition and methods critique
• system and implementation-context review
• reporting-guideline check
• equity and access review
• policy or management-language review
• journal-lane recommendation
• submit, revise, retarget, or diagnose deeper call

The review should not only say "add context." It should identify the system or data context needed for the claim to be actionable.

Before submission, authors often need to:

• define the healthcare decision-maker more clearly
• move system context into the introduction or methods
• document code lists and cohort definitions
• add missingness, clustering, or sensitivity checks
• explain implementation fidelity or workflow adaptation
• use the correct reporting checklist
• narrow policy or management claims
• retarget from a clinical journal to health services, quality, implementation, or policy venues

These fixes make the manuscript easier for a health services editor to evaluate.

An EHR study needs phenotype definitions, missingness, data-quality checks, and coding transparency. A claims study needs enrollment, eligibility, coding, episode, and attribution clarity. A quality-improvement study needs SQUIRE-style reporting, intervention details, and context. An implementation study needs theory or framework use that is integrated, not tokenistic. A workforce study needs setting, labor-market, and organizational context. A patient-safety paper needs event definition, detection logic, and system consequence.

The AI manuscript review can flag whether the blocking risk is data definition, system context, implementation, equity, or journal fit.

Use this page when the manuscript's submission risk depends on healthcare delivery, utilization, access, quality, EHR or claims data, workforce, care pathways, implementation, or system management. Use public health review when the paper is mainly about population health, prevention, community health, or broad policy outside the care-delivery system.

That distinction keeps the page focused on the health services buyer's actual problem.

Do not submit a health services research paper if the data definitions are too thin for another group to understand. Reviewers will not trust utilization, access, quality, or outcome claims if cohort construction and coding choices are opaque.

Also pause if the discussion recommends a delivery change without explaining workflow, feasibility, equity, or system constraints. Health services research is judged partly by whether the result can survive contact with the care system.

For multi-site work, pause again if variation between sites is treated only as a nuisance. Differences in staffing, referral patterns, payer mix, EHR configuration, leadership, and local access can be the reason the finding matters. A good manuscript explains whether the intervention or association is robust across those conditions or depends on one favorable setting.

That site-level explanation is often what turns an analysis into usable health services evidence.