Skip to main content
DataCrafters synthetic data · demonstration

← Provenance

Offer OF-000026

Exactly what the side panel showed on Fri Nov 13, 2026 04:55 PM for patient P30 (visit KE-P30, note KN-P30-1), and every response to it. Synthetic demonstration data.

What was shown

Heart pumping fraction (type) · shown as Needs a look (stated, not supported by the record)

The note says “Heart failure with preserved ejection fraction”; the latest ejection fraction is 35% on 2026-08-14, which does not fit the type written (needs 50% or higher).

Evidence

  • Ejection fraction 35% · echocardiogram 2026-08-14 (transthoracic, biplane): Left ventricular ejection fraction 35% by biplane method. · ECHO-P30-2
  • Ejection fraction 55% · echocardiogram 2024-11-12 (transthoracic, visual estimate): Left ventricular ejection fraction estimated at 55%. · ECHO-P30-1
  • Acuity words in the note: chronic

Options (fixed order, nothing pre-selected)

  1. Heart failure with reduced ejection fraction (HFrEF) · met · latest 35% on 2026-08-14
  2. Heart failure with mildly reduced ejection fraction (HFmrEF) · not met · latest 35% on 2026-08-14
  3. Heart failure with preserved ejection fraction (HFpEF) · not met · latest 35% on 2026-08-14
  4. Heart failure with improved ejection fraction (HFimpEF) · not met · no earlier value of 40% or lower; latest 35% on 2026-08-14
  5. Other (I will write it)
  6. Clinically unable to determine
  7. Not clinically supported (I will revise the note myself)

How it was produced

  • Definition front_hf_ef_type@1.0; run FRUN-00030.
  • Note readers: Stand-in AI reader and rule reader agree; AI reader quoted Heart failure with preserved ejection fraction, HFpEF.
  • AI reader: offline stand-in (not a language model).
  • Replay hash 1dc331474d2f2ae2a299390afcd22bdc543b5c42a5fc7b8202c34eab24d577d6; results-side hash 821c37d97b9ecc237b41a1773c89328a8188e399da7c980ba7bf040fa974b91b.
Reference ids (for audit)
  • AI reader as stored on this offer: stand-in · clockworks-mock · version mock-1/exactdx.front_statements@1

Responses

Current answer: No response yet

  1. None yet.