How Research Works
- Process of Producing a Research Card
- Research Structure
- Data Sources & Timing
- Providing Feedback in Research
- Important to Remember
- Related Articles
Research turns your real-world data and peer comparisons into cards that point to patterns in your practice, usually one or two steps from a clinical decision. Knowing how a card is built, how to read each article, and how far the data reaches helps you judge what a finding means for your patients and your numbers.
New Research is posted weekly and reflects historical activity, because claims arrive with a lag of about 6 months.
Process of Producing a Research Card
- Data Collection: Your NPI-tied real-world data is attributed to you.
- Data Validation & Preparation: Data from you and thousands of peers goes through quality review before any calculations.
- Standardization: Raw data is mapped to a consistent structure so that codes, categories, and identifiers are interpreted correctly.
- Pattern Analysis: Data is analyzed within your peer group and clinical area to surface patterns and trends.
- Prioritization & Relevance Filtering: Research is designed to be actionable, typically 1–2 steps from a clinical decision.
- Output & Delivery: Cards appear in the Research tab. Deeper dives show the finding, background, supporting evidence, limitations, follow-up, and references.
Research Structure
Reading Guide
The top of each Research article contains a reading guide. Below the title, you see the date posted and a pill showing the Research topic.
A reference with a number, such as [1], cites published literature. A reference with a letter, such as [a], points you to data analysis. An asterisk (*) marks a defined term in the article.
Published literature, data analysis, and defined terms are listed in the References section of each article.
Study Design
Each study design in a Research article summarizes the type of analysis, the data and claims sources used, and the number of patients (shown as N = number of patients). It also lists the time period, with total months in parentheses.
Key Finding
This paragraph covers the key points of the article. It may include a brief data breakdown, comparisons and analyses, mechanisms or root causes, interpretation of the results, limitations, and clinical context.
Background
This paragraph gives the background relevant to the Research. It may include disease or condition data, clinical definitions and classifications, current guidelines and corresponding evidence, and real-world implementation gaps. It may also cover known limitations and policy or structural context. References support the background information.
Supporting Evidence
Supporting evidence is split into one paragraph per claim. Each paragraph may provide numerical specifics, trend analyses, comparisons, stratification and subgroup details, confounding checks, and potential exceptions.
Numerical evidence may carry a lettered reference. That reference leads you to the Data Evidence tab of References.
Limitations
Limitations appear in a table with two columns. One column shows where a limitation exists in the Research. The other explains why the finding still holds.
A limitation may be surfaced because of data source constraints, cohort definition limits, measurement or coding limits, analysis design choices, or incomplete data. It may also acknowledge the boundaries of the analysis.
Follow-Up
Follow-up items are bullet points of actions you can take based on the article. They may suggest how to apply the findings to your practice, additional variables to consider, or geographic constraints.
References
The References section has three dropdown tabs:
- Definitions: Explains key terms and how they were measured or coded in the analysis. It covers data specifications, coding details, timing and quantitative boundaries, and what is intentionally included or excluded. It also explains claim-level mechanics and how each definition applies to the cohort or analysis.
- Literature: Lists guidelines, peer-reviewed studies, policies, and healthcare organization reports, with a URL link for each citation. Citations are numbered in the order they appear in the article. Each source supports a specific claim in the Key Finding or Background section. Sources come from credible institutions such as medical societies, government agencies, and academic databases where applicable.
- Data Evidence: Gives a numerical breakdown of the data used in the article, including tables, percentages, and population or setting details. As with Literature, data presented in the article is tagged with a letter that links to the matching evidence.
Data Sources & Timing
Data: Research draws on medical claims (open, closed, QE, pharmacy) and de-identified peer data used for comparison.
Claims have an inherent lag, typically around 6 months. Research reflects historical activity, not current clinical practice. Recent activity may have gaps that affect the scope or direction of a Research article.
Timing: New Research is posted weekly.
Providing Feedback in Research
Your feedback on Research articles shows Jiro where Research is working as intended and where it can improve. Use these steps to give feedback on an article:
- Click a Research card to open the drill-down view. The thumbs-up and thumbs-down icons are below the title, to the right of the posted date and topic pill.
- Select the thumbs-up or thumbs-down icon to rate the Research content.
- In the "Tell us more" window that opens, add details in the optional text box. Any information you provide helps improve Jiro over time.
Submitting feedback does not change your Research or remove articles you flagged. Jiro reviews patterns across user submissions on a regular basis to make improvements.
Important to Remember
- Claims typically lag by around 6 months, so Research reflects historical activity, not current clinical practice.
- Recent activity may have gaps that affect the scope or direction of a Research article.
- New Research is posted weekly.
- Submitting thumbs-up or thumbs-down feedback does not change your Research or remove articles you flagged.