What each system holds
No system holds the whole record. Each of these holds a different part of it — different encounters, different results, different notes — which is the reason moving data between them is worth doing at all. This screen asks that at both grains: the population by resource type, and, once you pick somebody, the same chart as each system holds it.
15 of 15 resource types published
Every figure is counted from that system's own store, not from the corpus — 323,607 records reachable across the 1 selected system. A type a vendor does not publish is not zero: it is unreachable through that connector, which is the thing to know before choosing a source.
Every resource type, in every selected system
One row per type, one column per system. A number is what that system holds and a connector can read; — means that vendor does not publish the type at all. derived marks a type this corpus computes from the records it stores rather than storing directly.
| Resource type | Northside Health (Epic) | widest | How this corpus has it |
|---|---|---|---|
| Observation | 108,566 | 108,566 | stored in this corpus |
| DiagnosticReport | 57,751 | 57,751 | derived one per lab panel — the results already on the chart, grouped as they were reported |
| Encounter | 36,985 | 36,985 | stored in this corpus |
| Condition | 19,520 | 19,520 | stored in this corpus |
| Immunization | 13,592 | 13,592 | stored in this corpus |
| Patient | 13,241 | 13,241 | derived the chart itself — one per patient this system holds |
| Consent | 13,241 | 13,241 | derived the sharing decision this demonstration already holds for every chart |
| ExplanationOfBenefit | 12,403 | 12,403 | derived one per adjudicated claim already in the corpus |
| MedicationRequest | 11,782 | 11,782 | stored in this corpus |
| MedicationAdministration | 11,036 | 11,036 | derived the giving of a medication already prescribed on the chart |
| DocumentReference | 9,485 | 9,485 | stored in this corpus |
| Procedure | 6,388 | 6,388 | stored in this corpus |
| ServiceRequest | 6,388 | 6,388 | derived the order behind each performed procedure |
| AllergyIntolerance | 1,687 | 1,687 | stored in this corpus |
| AdverseEvent | 1,542 | 1,542 | derived an allergy that already records a reaction |
Where each system's reach ends
The same systems, read as postures rather than counts — the auth model a connector must speak, whether a population can be read at all, and what the vendor will accept back.
Northside Health (Epic) 13,241 patients · 323,607 records · 15/15 types
Counts come from the corpus every other screen counts; the per-system type list comes from the same profile mirror the connectors read. Neither is stored here, so neither can drift. Heightened categories (psychotherapy notes, 42 CFR Part 2, sensitive conditions) are never included in a reachable count — they are decided per chart at run time, on the permission lattice.
A system's records are derived, not stored: CRC32("<system>|<table>|<record id>") decides each record on its own, so every visitor sees the same slices and nothing has to be kept in step. What a delivery adds lives in this session's sandbox — your run changes nobody else's, and the corpus is never written to.