How To Cite Jiro In Research


Purpose

This guide enables researchers to properly attribute Jiro as a data source when citing platform-generated Research cards, metrics, and analytics in published work. Clear attribution supports transparency, reproducibility, and appropriate credit for the platform's infrastructure and methodology.


Citations by Feature

Different Jiro features require different citation approaches:

Feature What to Cite
Practice Jiro
Metrics Jiro
Spotlights Jiro
Research Jiro
Consult The listed sources in a response
Discover The summarized journal or article

What to Include in a Citation

When citing Jiro, include the following elements:


  • Platform name: Jiro
  • Version or data period referenced, if known
  • Specific Metric card, Research card, or feature cited
  • Access date
  • Your organization or practice context, if relevant

Citation Format Examples

General Platform Reference

Jiro [Software]. Accessed [Month Year]. Available from: https://app.jirohealth.com

Specific Metric or Research Card

[Metric Name]. Jiro platform Research card. Data period: [Month Year – Month Year]. Accessed [Month Year]. Available from: https://app.jirohealth.com

In-Text Citation Example

"According to practice-level data from Jiro (accessed March 2026), ED utilization among attributed patients decreased 12% over 12 months."


Citing The Underlying Data

Jiro surfaces Research cards derived from de-identified medical and pharmacy claims data. When your research requires you to cite the underlying dataset, use:

"Data were sourced from de-identified healthcare utilization and medication claims, accessed via Jiro."

Do not characterize Jiro as a claims database or payer platform. Jiro is a clinical intelligence platform that uses claims data as its source.


Important to Note

Include the following in your methods or limitations section when referencing Jiro Research cards:


  • Claims data reflects billed encounters, not all care delivered.
  • Data lag varies by source. Pharmacy claims arrive within approximately 2 weeks of service. Open claims (clearinghouses and third-party sources) arrive within 6 weeks. Commercial closed claims arrive within 6 months. Government payer claims (Medicaid, Medicare, Qualified Entity programs) arrive within 9 months. See Time & Refresh Cadence for details.
  • The claims database covers approximately 60–70% of U.S. medical encounters and 50–60% of pharmaceutical encounters. Findings may not generalize to care outside the connected claims network.
  • Metrics are attributed to providers via NPI and may not capture all encounters.
  • Data is de-identified and does not represent individual patient records.
  • Research and Metric cards update over time as new data arrives.

This guide applies to citing Jiro platform features in peer-reviewed publications, dissertations, institutional reports, and formal research contexts. Researchers should understand the data limitations and lag characteristics outlined above to accurately contextualize findings.


Frequently Asked Questions

Do I need permission to cite Jiro in research? No. To cite Jiro in research, no special permission is required. If sharing or publishing practice-level data derived from Jiro, ensure you have appropriate institutional approvals.

Can I cite Consult? Consult draws on peer-reviewed medical literature and clinical guidelines. Cite the specific sources provided in a Consult response (click or hover on desktop, tap on mobile). Note that Consult surfaced these sources.

What if I want to use Jiro data in a formal study? Contact the Jiro Health team to discuss your research needs.

How do I describe Jiro in a methods section? Describe Jiro as a clinical intelligence platform that surfaces practice-level Research derived from de-identified claims data. Include the specific Metric or feature used, the data period, and the access date.

Can I cite a specific Research card from Jiro? Yes. When citing a specific Research card, describe the content, topic, time period, and cohort. Note the access date, as Research cards refresh over time.


Related Articles

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us