Protocol in. Eligible patients out.
Three steps: extract the criteria, match against patient records, return a ranked list. Here is what each step actually does and why the order matters.
Protocol ingestion and criteria extraction
Upload a protocol PDF or paste criteria text directly. Enrollvue parses each inclusion and exclusion criterion, resolves negations, identifies temporal constraints such as prior therapy windows and washout periods, and structures the result as evaluable logic before a single patient record is touched.
Criteria written across multiple sentences, criteria with negated conditions ("must not have received"), and criteria that depend on prior treatment history are the ones that trip up manual review and keyword-based tools alike. Enrollvue resolves these into a structured form that can be evaluated consistently across every patient in your chart pool.
"Patients must not have received prior anti-HER2 therapy within 6 months of enrollment date, excluding trastuzumab given in the adjuvant setting more than 12 months prior."
type: exclusion
condition: prior_anti_HER2_therapy
window: 6 months
exception: trastuzumab_adjuvant > 12mo
negation: truePatient record matching
Connect via HL7 FHIR feed or upload de-identified chart exports. Enrollvue reads unstructured clinical notes alongside structured fields: lab values, diagnosis codes, procedure history, and medication records. Each criterion runs against the full record, not just coded fields.
Every flag traces to the specific note text that triggered it. When a coordinator sees a candidate marked "prior anti-HER2 therapy clear," they can read the exact evidence snippet that backs that determination, not just a confidence score from a black box.
"...staging CT 2026-04-12 confirms 2.1cm measurable hepatic lesion per RECIST 1.1 criteria. HER2 IHC 3+ confirmed pathology report 2026-03-08..."
Ranked eligibility list
Enrollvue returns a downloadable ranked list sorted by match completeness. Fully meeting candidates appear first. Each row shows which criteria were met, which were flagged for coordinator judgment, and which were disqualifying. Coordinators start at the top and work down a list they can trust, rather than starting from a raw chart pile.
The output format is a spreadsheet-style view your team already knows how to work with. No proprietary interface to learn, no new login for every coordinator. The ranked list is the deliverable.
Data stays at the site
Identifiable patient records never leave the site's infrastructure. Enrollvue's matching computation runs on de-identified or tokenized extracts. This architecture is designed to align with HIPAA controls. We do not store, transmit, or process PHI on our infrastructure.
Enrollvue is a decision support tool, not a diagnostic device. We surface candidates and evidence. All final eligibility determinations are made by your PI and study team. Enrollvue does not replace investigator judgment and is not intended to.
Works with your existing EHR setup
Epic, Cerner, Meditech, and most HL7 FHIR R4-capable systems are supported via standard API. Sites without API access use the CSV chart export workflow at no extra cost. A typical FHIR integration takes under two weeks. We handle the configuration; coordinators do not touch it.