Rural health funds, opioid settlements and Medicaid quality programs must report outcomes, yet a small clinic or Critical Access Hospital sees too few patients to measure its own. A Circle runs one protocol across every site, each value traceable to the clinician or patient who entered it, and reports from live data.
Program evaluation is usually bought from intermediaries who take a share of value they did not create. A sponsored Circle deploys one protocol across every funded site, and the sponsoring agency or participating practices hold the 85% share of what the resulting datasets earn: an asset the program owns, not a recurring vendor license.
Public-sector data reuse is legally slow because provenance and consent degrade at every broker hand-off, and a hand-off that cannot be traced cannot be defended. A Circle has no hand-offs: data enters only from identified clinicians and their patients, with consent attached. Local nodes and verification without moving records are in pilot.
States report Rural Health Transformation progress to CMS; settlement funds must go to approved abatement uses, including evaluating what works; the Medicaid Quality Pledge calls for near-real-time data instead of claims and chart abstraction. Circles meets each inside routine capture, not a separate exercise.
Each runs on the same four pillars: the Observational Protocol, the Circle, the closed system and the technical stack. The governance and security detail sits in the linked white papers.
Pool comparable Cases across rural and urban sites on common protocols, so each site’s outcomes can be read against the state and national cohort.
Evaluations today are assembled from claims and vendor extracts, so the finding depends on data the agency cannot inspect. A Circle states the program's question as an Observational Protocol and captures the attributes that answer it at the point of care. The evidence supporting a funding or policy decision can be traced to the clinician who recorded it.
Chain of custody and consent are properties of the record, not promises in a contract.
In a brokered data path, provenance and consent degrade with every hand-off, which is what makes public-sector reuse legally slow. Here every entry carries its author and time, and the patient’s consent terms travel with it. Circle Health Coins and verification without moving records, now in development and pilot, extend this further.
One protocol, deployed across every practice an MSO or state program supports, with no hardware or local installation.
Management organizations carry the integration burden for practices running different systems. Because capture happens in inCytes™ during the ordinary visit rather than through an interface to each EMR, a Circle can be stood up across a managed group without a data-warehouse project, and completeness is visible per site from the first month.
Support ACCESS, ACO contracts, the Medicaid Quality Pledge and opioid-sparing prescribing with prospective outcome data.
Episode models judge the whole arc of care, which requires longitudinal outcomes the participating practices do not currently hold. A Circle defines those endpoints before enrollment, so an agency or MSO can monitor performance during a period rather than reconstructing it afterwards, and can defend a rate or attribution decision on source-verified records.
In a sponsored Circle, the agency holds 85% of net license value; in an MSO Circle, the practices that produced the data do.
Public programs and management organizations usually fund collection and then pay again to license the result back. On the Circles Platform the compilation belongs to the Circle Members who produced it, sponsors transact on the Circles Datasets Exchange, and RegenMed is committed to maximizing that value on the members' behalf. Participation becomes a return to the practices rather than an unfunded reporting mandate.
Sources: HHS (2025); Congressional Research Service (2025) and New York Attorney General (2025); CMS (2026); CDC National Center for Health Statistics (2026).
Today on AWS under HIPAA safeguards, and in-region where a jurisdiction requires it. An agency or institution can also run a licensed node inside its own firewall. Access follows the protocol’s sharing rules and the Ownership Agreement.
Program reporting uses aggregate measures; datasets licensed for other uses are de-identified under HIPAA, and each patient’s consent terms stay attached to the data. Verification without moving records, now in pilot, will let a reviewer confirm a value without receiving any record.
Yes. Different programs can define different episodes over the same Cases; a primary care protocol can serve a rural health program, an opioid settlement evaluation and a Medicaid quality measure at once.
Agreement on the protocols, clinicians willing to enroll every eligible patient, and an onboarding schedule across sites. No hardware, local installation or added staff.