Engine

Model & Data Controls

loaded Oct 14 · Demo portfolio

Data mode

demo

Fictional portfolio scenario calibrated to a representative book of business.

Identity gates

73 high-conflict lives

Resolution debt

meds 2 · dx 0 · proc 2 · L3 1 — open rows from loaded summaries

Lab results

55,832

1,396 unit-blocked

Unresolved eligible rows

current-eligible members without a resolved life

Data factory path

What enters the product, where truth is shaped, and which evidence is live versus pinned.

loaded Oct 14

01Source intake3 cataloged families ^N
Hint membership/billing · Verve/Elation clinical · Marathon clinical/claims.
Ingest owner + watermark remain named debt.
02Canonical identity3 promotion gates
Source people resolve onto the durable life spine before product use.
73 high-conflict lives · 0 eligible unresolved.
03Semantic contracts2 loaded domains
Stable semantic/app-facing objects isolate product routes from source tables.
Domain durability, refresh posture, and next action continue below.
04Certification7/7 gate checks ^RQ
Pinned 2026-07-10; 37/39 reconcile gates passed.
Evidence snapshot, not a live control-plane signal.
05ServingDemo portfolio
Fictional portfolio scenario calibrated to a representative book of business.
Runtime posture is resolved on this request.

Truth certification (Wave 2.6)

Pinned certification snapshot (2026-07-10) — does Health OS conserve and fuse the clinical/encounter evidence Wave 3A needs? Executable gate data:certify-wave26 passes 7/7. Full manifest: docs/receipts/health-os-wave-2-6-certification-manifest-20260710.json.

Encounter truth (superseded by Wave 2.6.1)historical candidate math — not an official verified denominator

Wave 2.6 candidate math (historical)^P

9,138

5,744 appointment-status-proposed + 3,394 claim keys — candidates, not verified encounters

Atom overcount

387

current atom 9,525 carries un-collapsed claim duplicates — never present as a visit count

Cross-family collisions

Verve/Marathon disjoint at person-day

limitation SUPERSEDED BY WAVE 2.6.1: 9,138 is historical Wave 2.6 CANDIDATE math (5,744 appointment-status-proposed + 3,394 claim keys), not the published official verified encounter denominator. Appointment rows are preserved as candidate/supporting evidence and reporting facts; they do not, by themselves, certify a completed encounter.

Biomarker fusioncertified with limitation

Members, any lab

1,263

1,260 reach Lane 3

Lane 1+2+3 fused

227

1,033 Lane 1+3 · 3 Lane 1 only

Both source families

Verve + Marathon overlap (disjoint)

limitation Lane 1↔Lane 3 fuses at scale (1,260 members); Lane 1↔Lane 2 covers only 2 markers; 0 members span both Verve and Marathon source families.

Encounter evidence model v1 (Wave 2.6.1)

Pinned posture (2026-07-10, rule wave-2.6.1-v1-20260710) — visit-note evidence elevated from the charted-vitals carrier; appointments preserved as candidate/supporting evidence and reporting facts. Executable gate data:certify-wave261. No direct Appointment→Visit_Note FK exists; same resolved member + same service date is a rule-versioned match signal, and same-day fan-out stays ambiguous (never silently collapsed).

Encounter postureelevated to note-backed verification — 2,856 unambiguous person-resolved note pointers verify encounters; 397 note rows across 286 same-day fan-out member-days stay unresolved to avoid duplicate counts

Verified encounters^P

2,856

published note-backed unambiguous denominator — pending lifecycle exception check

Note-backed candidates

3,253

2,666 clean note+appointment same-day attachments (one candidate, both evidence objects)

Appointment-only candidates

3,078

possible/probable encounters — preserved candidate lane

Claim-visit candidates

3,394

external service-feed signals — no paid-claim requirement

Ambiguous member-days

286

same-day fan-out held ambiguous — no silent collapse

blocked on sanitized VERVE_HEALTH.VISIT_NOTE promotion (lifecycle/status, timestamps, provider/location keys, governed note text layer), DPC-safe external-service feed semantics, BILL→VISIT_NOTE bridge for CPT/dx attachment, vitals identity repair (11,300 unresolved note pointers). 1,569 excluded appointment rows stay conserved reporting facts; 11,300 unresolved note pointers await vitals identity repair. Historical Wave 2.6 candidate math (9,138) is reference only.

Encounter vitals + claims-equivalent lines (Wave 2.6.2)proposed · apply pending runner ddl approval (pinned 2026-07-10)

Charted vital rows attached^P

27,666

attach to all 2,856 verified note-backed encounters via the durable note pointer — avg ~9.7 rows/encounter

Vital measurement events

135,209

134,293 carry a note pointer — a vital row without one is a clinical measurement event, not an office visit

Claims-equivalent lines^P

18,346

conserved clinical service lines across two source adapters

Marathon procedure lines

3,596/3,625

attached to external service candidates by durable claim key — never same-day inference; candidates, not verified encounters

Verve bill lines

8,333

active lines blocked on the BILL→VISIT_NOTE promotion — billing dates 100% quality-flagged; 2,071 deleted/voided excluded

apply pending Views authored as health_os_dev_yolo.app_encounter_vital_observation_v1 + health_os_dev_yolo.app_claims_equivalent_line_v1, apply_pending_runner_ddl_approval; logic proven live by data:certify-wave262. Marathon diagnosis lines (4,317) are preserved with a disjoint claim-key family — not attachable yet.

Certification posturefreshness, worklists, and the reconcile gate

Reconcile gates

37/39

2 red = Hint membership identity drift; repair blocked_on_source_access from this principal (repair packet delivered).

Vintage^RQ

mixed

Lane 1 labs are a static 2026-07-07 build; live canonical Verve labs run to 2026-07-08 — any Lane-1-vs-live rollup is mixed-vintage.

Encounter worklist

417

387 dup + 30 unresolved-identity rows

Lane 3 exposure^R

internal only

lewis_reviewed_internal_use / reviewed_not_yet_evidence_validated / internal_only

Identity / MPI

Promotion gates after survivorship — what blocks identity promotion and what to do next.

Identity promotion gates3 gates

high conflict identity reviewreview blocked
Review candidate evidence before promotion.
source 73 · adjusted 73 · computed Oct 14
hint survivorship anchorresolved by hint survivorship
Keep Hint identifiers as source ids, not Health OS master ids.
source 3126 · adjusted 3126 · computed Oct 14
source only population visibilityneeds more signal
Attach EHR, claims, labs, or Marathon signal before clinical ranking.
source 284 · adjusted 284 · computed Oct 14

Source contracts

Semantic durability, refresh posture, and lab normalization evidence from the loaded product contracts.

Semantic spine domains2 domains

Domain	Concept family	Spine system	Durability	Refresh posture	Next action
labs	lab_observation	LOINC	live	refreshable now	npm run data:refresh-lane1
membership employer billing	operational_source_fact	source crosswalk	partially staged	needs refresh promotion	future_domain_refresh_command_required

Lab coverage by sourceLane 1 use layer

Source	Results	LOINC	Reference-matched	Unit normalized	Unit blocked
Sample lab source A	7	7	3	0	0
Sample clinical source B	12	11	5	11	2

Lab reference & unit posturepreviously loaded, now visible — caps what the biomarker catalog can claim

Reference status

mayo reference available: 8
mayo no reference values: 1
no mayo reference row: 9
no loinc mapping: 1

Unit status

unit normalized: 11
unit blocked: 2
unit missing: 4
non numeric result: 2

The lane still reads the dated reference table; switching the app to the stable app_lane1_lab_result_reference_v0 alias waits on runner-lane R4 confirming the alias exists in the DB.

Model governance

Lane 3 display policy and marker bindings. Changes to Lane 3 configuration are a GATED control — tracked, attributed, reversible — structure and labeling in v0, live controls later.

Lane 3 display policypreviously loaded, now visible

Policy area: lane3 risk display
Status: implemented
Scored lives: 310
Numeric scores suppressed: 310

show_reviewed_band_only_suppress_raw_numeric_score^R

Lane 3 marker bindingsLOINC binding posture

bound to loaded loinc · source loinc matches loaded loinc core: 5
needs resolution · missing source loinc: 1

Resolution reasons

missing source loinc: 1

Lane 3 marker resolution worklist1 open rows · showing top 1 by resolution rank

#	Marker	Domain	LOINC status	Reason	Required action
1	Sample Marker Gamma	sample domain	missing source loinc	missing source loinc	Sample action: confirm LOINC for this marker.

Resolution queues

Medication, diagnosis, and procedure crosswalk posture plus the loaded unmapped worklists. Row identifiers stay truncated; per-person context is reached through the workbench, not from here.

Medication mapping funnelcrosswalk + currency posture

Mapping status

source only: 2
ndc product mapped no target rxclass: 1
rxclass name mapped no ndc: 1
ndc and rxclass mapped: 1

Currency posture

current candidate: 3
historical or stale: 2

5 rows · 2 people · 3 current candidates

Diagnosis & procedure posturecode mapping + source policies

diagnosis: 4 mapped of 4 · 0 worklist
procedure: 1 mapped of 3 · 2 worklist

Source interpretation policies

lab crosswalk: implemented · 12
medication current: implemented current candidate · 3
risk display: implemented · 2

Medication resolution worklist2 open rows · showing top 1 by resolution rank

#	Medication	Type	Person	Posture	Reason	Required action
1	Sample Medication One	sample order	sample-l	current candidate	missing ndc and no safe rxclass name match	Sample action: resolve NDC or approved name mapping.

Diagnosis resolution worklist0 open rows · showing top 1 by resolution rank

#	Code	Person	Status	Required action
1	SAMPLE.0	sample-l	source code unmapped	Sample action: map or reject this source code.

Procedure resolution worklist2 open rows · showing top 1 by resolution rank · CPT descriptions license-gated

#	Code	Person	Status	Required action
1	S0000	sample-l	cpt source carried license blocked	Sample action: awaits CPT licensing decision.

This board is deliberately the last nav item. Data QC appears here — inside named support workflows — or where it gates a specific decision on a product surface; nowhere else.