Data Sources

Jiro uses several sources of data to provide Insights, Metrics, and other tools in the platform.



Our goal is to give clinicians a clear, trustworthy view of their patient panels, practice patterns, and opportunities to improve care without exposing raw, unwieldy datasets.

We intentionally focus on the clinical value and limitations of the data, rather than on technical infrastructure of third‑party vendors or data sources.


At A Glance


Types of Data that Jiro Utilizes

Medical Claims

  • Office visits and consultations
  • Hospitalizations and procedures
  • Emergency department visits and urgent care situations
  • Imaging and lab services

Pharmacy Claims

  • Prescriptions written and filled
  • Refills and discontinuations
  • Medication adherence patterns (proportion of days covered)

Reference Data

Provider & Facility

We link claims data to curated reference information that's useful for clinicians. This helps answer questions related to referrals, populations being managed, how care differs by site, and more.

  • Practice, clinic, and facility attributes
  • Clinician identifiers and specialty information
  • Groupings that help us attribute care to a practice or clinician

How Jiro’s Data is Clinically Relevant

Longitudinal View of Patients and Populations


Practice and Clinician-Level Insights


Context for Decision‑Making


How we clean and prepare the data

Before any data is used in Jiro, it undergoes a series of steps to ensure it is as accurate, consistent, and useful as possible.

Step 1: Ingestion and Validation

  • New records arrive and are validated for structure and completeness
  • Duplicate files or overlapping feeds are identified and reconciled

Step 2: Standardization and Normalization

  • Codes and categories are mapped to consistent internal representations
  • Dates and identifiers are normalized to a standard format
  • Services are grouped into clinically meaningful categories (office visit vs. inpatient stay vs. ED visit)

Step 3: De‑duplication and Record Linkage

  • Identify and merge duplicate claim lines and encounters
  • Link related codes, payments, and records from a single visit
  • Connect encounters, prescriptions, and providers to construct a coherent patient journey

Step 4: Aggregation into Metrics and Insights

  • Aggregates and summarizes data into metrics at the patient, clinician, and practice levels
  • Applies transparent, documented logic to define each metric
  • Encodes business rules and clinical logic that have been reviewed by clinicians and validated against real‑world scenarios

Step 5: Ongoing Quality Monitoring

  • Monitor new data loads for unexpected shifts (like sudden drops in volume from a specific facility)
  • Regularly re‑runs validation checks and sampling to look for anomalies
  • Updates metrics and logic as coding practices, guidelines, or local practice patterns evolve

How the Data is used in the Jiro App

Practice Dashboards and Panels

Practice Overview Dashboards

  • Panel composition and risks
  • Utilization patterns across care settings
  • Trends in ED visits, hospitalizations, and follow-up care

Referral and Network Views

  • Who your patients are being referred to
  • How much care remains in-network vs. out-of-network

Spotlights and Insights

Jiro surfaces focused insights from claims and metrics to surface information that may not be noticed through base level metrics. Below are a few examples.

  • Patients at risk of avoidable ED visits
  • Gaps in follow‑up after hospital discharge
  • Changes in referral patterns or medication adherence

Metrics Details

Drilling into a metric shows additional details into the data used to calculate it.

  • How it is defined
  • High-level information about the underlying data

FAQs

Where does the data in Jiro come from?

Jiro uses de‑identified healthcare utilization and medication data, combined with provider/facility reference data and information generated within the Jiro platform.

How current is the data?

There is an inherent lag between when care is delivered and when claims are fully processed and available. As a result, data may be several weeks to a few months behind real-time care. You can find the time period of a metric or insight using the drill down.

Does Jiro show every detail of a claim?

No. Jiro does not expose raw claim forms or line‑level billing detail in the clinician interface. In any provided Metric or Insight, Jiro defines the item at a high-level to explain how they have been constructed.

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