Working memory outsourced to the edge of your screen

miraeproof tracks the readiness of every upcoming visit across your studies, so you can allocate your attention to what needs you first.

next
What needs you first, by time left to act
nowP077 · V1Due 08:00 today, not arrived; consent is on ICF v5 and v6 is now required.
14hP014 · V8Infusion lead time already breached.
1dP031 · V5Protocol window closes tomorrow.
2dP052 · V3Consent review needed; no infusion booking and the lead time has passed.
5dP099 · V4Infusion feed silent since Friday; readiness unknown.
8dP108 · V2Moderate risk; flexibility remains ample.
12dP042 · V6High no-show risk, but ample flexibility and all ready.
Synthetic data. 7 visits need no current action.

Synthetic data. Ebin Systems is a made-up clinic system standing in for the ones your site already uses. Select any part of the strip to open it.

A visit's loose ends live in different systems

Take one infusion visit. The protocol sets the dates it's allowed to happen. eConsent knows which consent version the participant signed. The chair scheduler knows whether a chair is booked, and the sponsor portal carries the latest amendment.

Each system is right about its own piece. The whole visit is held together by a coordinator, in a spreadsheet and in their working memory. That holds up until the week gets busy, or until that coordinator moves on.

The visit most likely to be missed can wait

review
P042 · V6
79%
no-show risk
Why it can waitTwelve days remain in its window, and everything it needs is ready.
critical
P052 · V3
27%
no-show risk
Why nowIts window closes in two days, with no infusion chair booked in time. Consent is also on an old version and needs review.

Sorted by no-show risk, P042 would come first. miraeproof ranks P052 ahead of it because its problems stop being fixable in two days, and the row says so.

Protocol window
The range of dates the study allows for a visit.
Recovery deadline
The last moment a problem can still be fixed without losing the visit. The queue groups items by severity, then orders them by this deadline.
No-show risk
How likely the participant is to miss the visit as scheduled. It refreshes whenever its attendance sources update.
Unknown
What miraeproof shows when a source goes quiet. An unknown is never counted as ready.

Every line in the queue traces back to its source

Open any item and follow it back to the records behind it. Here is P052.

  1. The site-approved protocol becomes a set of obligations. P052 has four, each checked as often as its source updates.
  2. Each obligation reads a few permitted fields from one system, in that system's own format. Everything else stays where it is. Records are matched by a local key, and its link to the person never leaves the site.
  3. A fixed rule turns what was read into a state. Anything short of satisfied stays open, and a source that stops answering becomes unknown.
  4. Only changes of state leave the source, as small packages with no patient record inside. Each one cites the poll it came from.
what the protocol asks
what each source holds
evidence state
what leaves
Consent versioneConsent, every 6 haccepts ICF-v6
eConsentREDCap-style export
subject_ref
S-7f3a
documented_icf_version
ICF-v5
consent_recorded_at
2026-07-10 09:00
consent_status
DOCUMENTED
5 more fields stay in eConsent
pendingv6 required since Aug 12
consent.versionsatisfied › pending, as of Aug 12, 09:00
Infusion bookingchair scheduler, every 15 minaccepts a confirmed booking
Infusion chairsscheduler feed
subject_ref
S-7f3a
infusion_required
yes
booking_status
NOT FOUND
4 more fields stay in Infusion chairs
pendingno booking found, and the booking lead time has passed
infusion.bookingpending, as of Aug 19, 07:00
Attendance historyEbin Systems, every 5 minaccepts recorded outcomes
Ebin SystemsFHIR Appointment
resourceType
Appointment
subject
S-7f3a
status
fulfilled
start
2026-07-04
4 more fields stay in Ebin Systems
satisfied3 prior visits attended; rescheduled Aug 14
attendance.historysatisfied, as of Aug 14, 00:00
Reminder repliestext reminders, every 5 minaccepts a reply
Reminder textsgateway log
replied_at
08-14 12:30
subject_ref
S-7f3a
reply
CONFIRMED
3 more fields stay in Reminder texts
satisfiedreply Aug 14, 12:30
attendance.remindersatisfied, as of Aug 14, 12:30
P052 · V3 in the queue: criticalNo infusion booking in time, and consent needs review. Window closes Aug 21.

When the protocol changes

An amendment recompiles the protocol, and every obligation is re-proved from what its source holds now. Nothing carries over from the old version. P077's consent passed under version 1.0 and needs review under 2.0.

Trace P077 in the demo

What a site can show its sponsors

The protocol decides what may be read, and interpretation follows fixed rules. Before anything runs, a site can show exactly which fields miraeproof reads and what leaves.

It works beside the systems you already run

miraeproof docks to the edge of your screen, next to your records and scheduling systems from any vendor. It holds back everything splitting your attention and unfolds for what needs you now.

It's built for the teams who run visits at research sites. The site decides what it may read and approves anything it learns, and your team still does the work in its own systems.

It keeps what your site learns

miraeproof keeps the evidence and adds the outcome while patient records stay in the site's own systems. As miraeproof sees more visits it learns how a site operates and relies less on reference data.

When miraeproof notices a pattern, such as a sponsor portal that always runs a day late, it proposes a change. Nothing changes until someone at the site approves it.

Clinical research professionals stay in a role for about 1.5 to 2 years. In a 2022 open letter, SCRS reported annual turnover of 35% to 61% among patient-facing site staff. Someone new to the team starts with the history their predecessors built.

Sources: SCRS, Fixing the Foundations (2025); SCRS, open letter on workforce retention (2022).

412visits matched to what actually happened, kept since Mar 3
MarAprMayJunJulAug
fit to this site
reference set1 in 5 missedthis site1 in 7 missed
noticed here
Sponsor portal records land about a day late.

Waits a day before treating sponsor data as missing.

Approved by the site's lead coordinator, Aug 2
The satellite infusion schedule goes quiet from Friday evening.

Asks for infusion confirmation by Friday noon.

Waiting for review

Where things stand

miraeproof is in the early stages of rollout. The core is built and tested, and every number on this site and in the demo comes from one synthetic dataset.

Built and tested

  • Readiness checks for visit windows, consent versions, infusion bookings and source freshness.
  • The protocol-driven evidence exchange, with FHIR and REDCap-style test connections.
  • A no-show forecast fed by the same exchange, refreshed as its sources update.
  • Every item shows why it's there, and when it's stale.

Rollout

  1. Retrospective validation with research sites, using records they already have, with no effect on care.
  2. Connections to each site's own systems.
  3. Learning from each site's own record, as the demo shows.
  4. Clinical validation.

Work with us

Research sites

Retrospective validation is open to research sites now. Email us and we'll walk your team through the demo, then ask how you track visits today.

Collaborators

If you build protocol tooling, or turn free-text records into structured facts, we'll show you how the evidence exchange works and where your work could plug in.