We run the application environment for you.
ManagedA dedicated, managed environment with your access controls and audit.
- Dedicated tenancy
- Your SSO and roles
- Full trace and audit
The same research, applied to each domain’s evidence, rules and owners.
A worked example for health plan quality teams: why a quality measure moved, whether it was performance or methodology, the gap to the next threshold and when an improvement can count. Operational analysis only, nothing clinical.
The questionWhy did this measure drop to three stars, and what would it take to reach four?
Match the measure, contract, publication and rating year.
Spot changes in performance, thresholds, definitions and methodology.
Reproduce the rating and measure the gap to the next threshold.
Connect the measurement period with the publication and rating year.
A quality leader checks the evidence, assumptions and likely impact.
Performance held at 71%. The four-star cut point moved from 70% to 75%, so the rating fell on methodology, not performance.
A quality leader confirms the interpretation before anyone acts on it.
Only approved versions go live. Every update reruns the same test set.
The reasoning path for one measure: the rate, the cut point that set the rating, the next threshold and the gap, with the timing that decides when it counts.
A measure value means little without the definition, cut point, contract and year behind it. Agent Hive keeps those pieces together.
Agent Hive
Agent HiveMeasure rates, scores and history from the quality warehouse.
Published releases, cut points and technical notes.
Rating year, applicable measures and dependencies.
Version comparison and the rating calculation run side by side. The explanation waits for a quality leader before it is used.
A measure can keep its name while its definition, weight or threshold changes. The quality evidence map keeps measures, contracts, thresholds, publications and years apart.
Provenance trail. Provenance of “on-time rate = 0.874”: on-time rate = 0.874 ← query run ← metric definition ← delivery policy §4 (read right to left: the fact was derived from each step in turn). Every step: entity “on-time rate = 0.874” (the fact in the answer); wasGeneratedBy query run. activity “query run” (2026-10-21 · 09:14); wasAssociatedWith analyst agent, used orders dataset, used metric definition. agent “analyst agent” (ran the query). entity “orders dataset” (snapshot 2026-10-20); wasDerivedFrom ERP export. entity “metric definition” (v3 of 3), versions v1 first draft; v2 excludes cancelled lines; v3 late = after promised date; wasDerivedFrom delivery policy §4, wasAttributedTo data steward. entity “ERP export” (nightly load). entity “delivery policy §4” (source document). agent “data steward” (approved v3).
Separate a real performance change from a calculation or data change.
Show what changed in the definition, threshold, weight or method.
Reproduce the rating and show the sources behind it.
Connect the measurement period with the publication and rating year.
Known cases and the questions reviewers use every day become the test set. Each reviewed answer becomes a repeatable test.
| Question | v1 | v2 | v3 |
|---|---|---|---|
| Why did measure M-12 drop from four to three stars?Movement | ~ | ✓ | ✓ |
| Did the cut point or the rate change?Rule | ✗ | ✓ | ✓ |
| Which methodology release applies to rating year 3?Rule | ✗ | ✗ | ✓ |
| Reproduce the rating from the published cut pointsGap | ✓ | ✓ | ✓ |
| How far is M-12 from the four-star threshold?Gap | ✓ | ~ | ✓ |
| Which measurement period feeds next year’s rating?Timing | ✗ | ~ | ✓ |
| Which measures share this data source?Dependencies | ~ | ✓ | ✓ |
Correct, partly right or wrong.
Reviewed answers join the set.
Prompts, tools and sources included.
A named owner signs off.
The same evidence trail, agent controls and expert review across four deployment patterns.
A dedicated, managed environment with your access controls and audit.
Agent Hive runs inside your private network, connected to your systems through approved paths.
The platform, the models and every trace stay on infrastructure you operate.
A policy gateway controls what is sent, which model receives it and what comes back into the workflow.
| Runs in | QpiAI managed environment | A dedicated network in your cloud | Your data centre (Docker / Compose) | An isolated network |
|---|---|---|---|---|
| Operated by | QpiAI | Agreed per engagement | Your team | Your team |
| Tenancy | Multi-tenant, isolated | Single-tenant | Single-tenant | Single-tenant |
| Data at rest | Managed environment | Your cloud and region | Your network | Inside the perimeter |
| Models | Managed models | Approved endpoints | Local, or via a policy gateway | Local models only |
| Outbound | Operated by QpiAI | Private connections | One controlled egress path (hybrid) | None |
| Identity | Your identity rules | Enterprise identity | SSO and RBAC | Local SSO and RBAC |
| Updates | Rolled out by QpiAI | Agreed per engagement | New image version, pulled | Signed offline packages |
| Audit | Audit history | Audit history | Local audit history | Local audit history |
Air-gapped Graph, agents and models run inside an isolated network; updates arrive as signed offline packages.