For Health plans
The signal before the claim.
Reproductive context arrives years ahead of utilisation data.
Assess governed population patterns without turning an individual's longitudinal record into a plan-level profile.
The problem
Claims describe utilisation, not the full context that preceded it.
Reproductive transitions, recurring symptoms and changes in function can develop long before they appear as a coded encounter. Claims remain essential for payment and utilisation analysis, but they do not reconstruct the member's lived sequence on their own.
Shiora is designed to support approved population questions using longitudinal context while separating aggregate analysis from access to individual health records.
What Shiora provides
Aggregate reproductive health context with controls at the query layer.
-
Cohort view
Approved aggregate analysis can examine recorded reproductive and life-stage patterns alongside relevant population context.
-
Suppression
Minimum-cohort and output controls are designed to reduce inappropriate disclosure from small or distinctive groups.
-
Governed access
Purpose, duration, data scope and review conditions are defined for each approved institutional use.
How it works
Every population question begins with a boundary.
Define the approved purpose
Specify the population question, decision it supports, permitted variables and accountable owners.
Assess legal and data fit
Review the applicable basis, coverage, provenance, identity risk, missingness and jurisdictional constraints.
Configure the cohort
Set inclusion logic, minimum-cohort conditions and output controls appropriate to the approved use.
Produce governed output
Return only the aggregate information permitted by the approved scope, with relevant limitations visible.
Retain accountability
Purpose, duration, access conditions and review history remain available for governance oversight.
Reporting boundary
What the plan can see. What remains personal.
Approved aggregate output
Population patterns for a defined question, above the configured disclosure threshold and with analytical limitations retained.
Protected from plan access
An individual's longitudinal record, person-level participation, unrelated information and any cohort too distinctive for the approved output controls.
Requirements and engagement
Start with one question and its governance basis.
A health plan engagement begins with a defined population question, accountable business and clinical owners, privacy and security review, minimum necessary data and a documented output policy. Integration is assessed against available systems and approved purpose.
The first engagement can be scoped around one cohort and reporting question. Timing, technical work and commercial terms depend on the jurisdiction, data environment and controls required. No savings or outcome claim is implied before evaluation.
The difference
Population analysis without turning records into plan-level profiles.
The governance model separates approved aggregate questions from access to an individual's longitudinal health record.
Health plan FAQ
Questions for clinical, actuarial and privacy teams.
The output is bounded before the analysis begins.
Can the plan see an individual's record?
No. The model separates approved aggregate analysis from access to an individual's longitudinal health record.
Does Shiora replace claims data?
No. Longitudinal reproductive context can complement utilisation data for an approved question. It does not replace claims or clinical records.
How are cohorts protected?
Controls can include minimum-cohort conditions, data minimisation, de-identification, access restrictions and output review selected for the use.
Can the plan see who participates?
The reporting model is designed for population output rather than person-level participation visibility.
Is the same legal basis used everywhere?
No. The legal basis, permitted use and deployment controls require jurisdiction-specific assessment.
Does Shiora produce individual risk scores for plans?
The audience model described here does not provide plan-level access to individual health profiles.
What integration is required?
Integration depends on the approved question, available systems, minimum necessary information and local security requirements.
How is analytical uncertainty shown?
Coverage, missingness, definitions and other relevant limitations should accompany the approved output.
Can this operate across jurisdictions?
Potential deployment must be assessed separately for each jurisdiction, including privacy, residency and governance requirements.
How does an evaluation begin?
Begin with one population question, the decision it will support, accountable owners and the output boundary.
Next step