recruitby mahalo healthEpic

Trial recruitment from your Epic charts.

Recruit screens authorized Epic charts every night and shows the evidence for every match.

Scheduled screening

02:00

Approved criteria v3
Lakeview Internal MedicineSynced 02:04
Harbor Family PracticeSynced 02:11
Northwind ClinicSynced 02:19
Cedar Grove MedicalSynced 02:27
Ready for coordinator reviewHuman verification next
Illustrative product screens. Synthetic data, not patient information or reported results.

How Recruit connects to Epic.

Recruit connects to Epic through direct FHIR, including FHIR Bulk, and through our EHR connection network.

Epic publishes FHIR R4 APIs for chart data such as conditions, medications, results and encounters, plus a Bulk Data export for whole populations. Recruitment needs the population, so Recruit uses bulk export for the first sync and updates every night.

Source: Epic on FHIR

Recruit workspace · FHIR Bulk configuration
HORIZON-CV · Cardiovascular outcomes · Illustrative studyDr. Elena Ruiz · Study coordinator

Add new site

FHIR Bulk

Configure the connection for FHIR Bulk.

FHIR client registration guidance

To connect via FHIR Bulk Data (Flat FHIR), register Mahalo Recruit as a client application within the EHR developer portal.

App type
Backend Service / System-to-System
Auth method
Asymmetric (RS256)
JWKS URL
https://recruit.mahalo.health/.well-known/jwks.json

Once registered, provide the generated Client ID and Token Endpoint.

Base URL*

Enter base URL

Client ID

Enter client ID

Token URL

Enter token URL

Scope

Enter scope

Illustrative setup screen. The fields shown here are not active and do not collect connection details.

Illustrative product screen. Synthetic data, not patient information or reported results.

What a connection involves

  • An agreement first

    The practice signs a data-use agreement before any chart is read.

  • Registered by your admin

    The practice's EHR admin registers Recruit as an authorized system.

  • Checked, then synced

    Recruit checks what the EHR supports. A first sync brings in the patient population, and nightly updates keep it current.

  • Permission per study

    Each practice gives permission per study, with a named signer, and can withdraw it at any time.

From protocol to shortlist, inside Epic data.

Recruit reads the protocol, checks every authorized chart each night, and shows your coordinator why each person may fit.

Protocol rules your team approves.

Upload the protocol. Recruit's AI turns every inclusion and exclusion into a rule your team can read and edit. You approve the version before anything runs.

Each rule says how it gets answered: from the chart, from a doctor's note, or by asking the patient.

Recruit workspace · Protocol criteria
HORIZON-CV · Cardiovascular outcomes · Illustrative studyDr. Elena Ruiz · Study coordinator

Protocol criteria

Criteria

Version 3 · draft

HORIZON-CV protocol · 148 pages · 21 criteria. Reviewed and approved by your team before anything runs.

14 chart · 5 notes · 2 ask the patient2 changes since v2
Inclusion#02

Age 40–85 at screening

age between 40 and 85

Chart answers it
Inclusion#03

Type 2 diabetes ≥ 6 months

T2DM diagnosis · E11.x · onset ≥ 180 days

Chart answers it
Inclusion#04

HbA1c 7.0–10.5% within 90 days

hba1c between 7.0 and 10.5 · LOINC 4548-4 · 90 d

Chart answers it
Inclusion#05

Established ASCVD (MI, stroke, PAD or revascularisation)

I21–I25 · I63 · I70–I73 · Z95.1

Chart answers it
Inclusion#06

On stable statin therapy ≥ 8 weeks

statin class · continuous ≥ 56 d

Notes read by AI
Exclusion#11

Heart failure NYHA class IV

NYHA IV · documented in notes

Notes read by AI
Exclusion#14

eGFR < 30 mL/min/1.73m² in last 6 months

egfr < 30 · LOINC 62238-1 · 180 d

Chart answers it
Exclusion#19

Unable or unwilling to attend 12 study visits

willingness · ask at pre-screen

Ask the patient
Read by Mahalo Intelligence · reviewed by Dr. Elena RuizApproval required before screening
Illustrative product screen. Synthetic data, not patient information or reported results.

Evidence from the Epic chart.

A lab result and its date. The sentence a doctor wrote. A question only the patient can answer. Recruit puts the evidence next to each protocol rule, so your coordinator checks the source in Epic instead of trusting a score.

Unknown is never a guess.

If a chart can't answer a rule, Recruit says so and turns it into a question for the patient. A named person verifies every match.

Recruit workspace · Candidate evidence
HORIZON-CV · Cardiovascular outcomes · Illustrative studyDr. Elena Ruiz · Study coordinator
MR

Marcus Reed

65 · Lakeview Internal Medicine · next visit Nov 6, 9:30 AM

Coordinator verification

From the chart

Type 2 diabetes ≥ 6 months

Met

Type 2 diabetes mellitus · E11.9 · since 2017-03-14

Problem list

HbA1c 7.0–10.5% within 90 days

Met

Hemoglobin A1c 8.2% · 2026-09-11

Lab result

Established ASCVD

Met

Acute myocardial infarction · I21.4 · 2023-06-02

Problem list · procedure

Stable statin therapy ≥ 8 weeks

Met

Atorvastatin 40 mg · continuous since 2023-06-05

Medication history

From the notes

Heart failure NYHA class IV

“Dyspnoea on moderate exertion, NYHA II. No orthopnoea.”

Cardiology note · 2026-08-20
Read by AI · verify at source

Needs a human answer

Unable or unwilling to attend 12 study visits

Unknown. Ask the patient at pre-screen.

No inferred answer
Illustrative product screen. Synthetic data, not patient information or reported results.

The summary moves. The chart stays.

A coordinator can open the exact note excerpt behind a result inside Recruit, and that viewing is logged. What moves on to other systems is the summary.

What the site receives

  • Which criteria were met
  • How each was known: chart, note or patient answer
  • The next appointment
  • Who verified the candidate, and when

What stays in Epic

  • Clinician notes
  • Raw lab values beyond what the study needs
  • Anything unrelated to the study

After a person verifies a candidate, Noa can invite them by text, email or voice, and the referral goes to CRIO or your CTMS with the eligibility summary attached.

Questions, answered.

Does Recruit work with Epic?
Yes. Recruit connects to Epic through direct FHIR, including FHIR Bulk, and through our EHR connection network. Each practice gives permission per study.
What does an Epic connection involve?
The practice signs a data-use agreement and its Epic admin registers Recruit as an authorized system. Recruit checks what the Epic FHIR server supports, runs a first sync of the patient population, then updates every night.
Does Recruit replace Epic?
No. Epic stays the system of record for care. Recruit reads authorized data to find people who may fit a trial, and your team works the shortlist in Recruit.
Does the AI decide who is eligible?
No. Recruit's AI reads protocols, charts and profiles and shows what it found. A named person on your team verifies every match and makes the decision.
What leaves the practice?
A summary: which criteria were met, how each was known, the next appointment and who verified the candidate. Clinician notes and raw record content stay where they are.
Where do verified candidates go?
To CRIO or your CTMS, with the eligibility summary attached. Sites on other systems can export to CSV or Google Sheets.

See Recruit on your Epic data.

Bring a protocol and a site. We'll show you who matches and why, under the right agreements.