ARO, Research Operations Platform Discuss a pilot

Patient Screening

Find eligible patients before the window closes.

ARO screens patient records against your protocol criteria and gives coordinators a ready-to-review worklist, for biobank specimen collection and cancer clinical trial pre-screening.

The problemTime / Missed patients / Scattered records

Screening is still done by hand.

Biobanks still screen patients for specimen collection almost entirely by hand, and trial pre-screening is often manual too. Coordinators read schedules, pathology reports and notes one patient at a time.

Time

Hours in charts

Skilled staff, searching

Coordinators spend much of their week looking for patients instead of consenting and collecting.

Missed patients

Windows that close

Found too late

When a potential candidate is identified after surgery, the opportunity for planned prospective collection may already have passed.

Scattered records

A fragmented trail

Decisions, hard to trace

Screening criteria, review notes, and decisions can sit across separate records, making the screening history difficult to reconcile.

The platformDefine / Screen / Review

One screening workflow, from protocol to patient list.

Your team sets the protocol criteria, ARO screens the records, and coordinators review each patient with the supporting evidence before recording a decision. The whole screening workflow lives in one place.

Screening modelApproved / Evidenced / Recorded

Your records

EHRSchedulesPathology

ARO screening

Protocol criteria · Matching · Evidence · Worklist

Coordinator review

Confirmed by people · Logged
What it is

One place for your screening workflow.
Criteria your team approves.
Worklists with the evidence attached.
A record of every screening decision.

Step 01

Define

Your criteria, approved

Your team sets up and approves each study's inclusion and exclusion criteria before screening begins.

Step 02

Screen

Records, checked

ARO checks patient records against those criteria and sorts them into potential matches, possible exclusions and cases that need a closer look, with the evidence attached.

Step 03

Review

People decide

Coordinators review each patient and the evidence, then confirm or rule them out. Every decision is recorded.

A screening runIllustrative / Synthetic data

What a coordinator sees.

Each patient arrives with the protocol they may fit, the criteria behind it, and where the evidence came from. One patient in this example matches none of the protocols.

  • 01Results across several protocols in one worklist.
  • 02Unclear cases flagged for a person, never guessed.
  • 03Final screening decisions stay with your team.
ARO / Screening run3 protocols
Screening across protocols1,284 records screened
Breast cancerLung cancerOvarian cancer
Patient 0142
BB-104 · Breast cancer tissue collectionPotential match
Meets 4 of 4 criteria · Surgery Nov 18 · Evidence: pathology report, surgical schedule
Patient 0157
BB-208 · Lung cancer tissue collectionPotential match
Meets 3 of 3 criteria · Resection Nov 20 · Evidence: imaging report, surgical schedule
Patient 0163
BB-312 · Ovarian cancer biobankFlagged for review
Prior treatment unclear in notes · Sent to a coordinator to confirm
Patient 0184
None of the screened protocolsNo protocol match
Closest: BB-104, excluded for neoadjuvant therapy · Reason recorded
Illustrative protocols and synthetic patients. Results reflect the available records. Coordinators make the final screening decisions.
Synthetic example · timing illustrative37 patients to review
Who we serveBiobanks / Trial teams / Also used for

ARO is built for biobanks and cancer research teams. The same screening workflow also supports industry collections, clinics and retrospective studies.

Reach the patient before the procedure.

Prospective collection depends on finding eligible patients ahead of surgery, while there is still time to consent and plan. ARO surfaces likely candidates from the schedule and the record, so coordinators can act in time.

Pilot objectiveFind more eligible patients in time for planned collection.
Yours by designSelf-hosted / Role-based / Accountable

Deployment under your control.

ARO can run in an environment your institution controls, limits access by role, and records who reviewed each patient and what they decided.

  1. 01
    Can be self-hostedRun ARO on your own servers or in your own cloud account.
  2. 02
    Built around your dataData sources and integration requirements are assessed with your institution during pilot planning.
  3. 03
    Access by roleDecide who sets up protocols, who reviews patients and who sees results.
  4. 04
    People stay in chargeA person makes every final screening decision, and it is logged.
Your environmentDeployment boundary
Patient recordsEHR and schedules
→
AROScreening
→
CoordinatorsReview and decide
Your serversYour cloud account
Patient data stays in your environment
QuestionsWhat teams ask first

FAQ

Does ARO decide who is eligible?

No. ARO identifies likely matches and shows its evidence. A coordinator confirms or rules out every patient.

Where does patient data go?

ARO can be self-hosted in your own environment and can run without sending patient data to outside services. Data flows are confirmed with your team during deployment planning.

Which EHRs does it work with?

ARO is not tied to one EHR vendor. Compatibility, available data, and integration requirements are assessed with your institution.

Is ARO available now?

ARO is ready for pilots. It has been tested on synthetic data, and a benchmark study against independent human review is in development.

Get in touch

Contact us.

Have a question about ARO? Want to learn more, explore a pilot, or discuss working together? Send us a message and we’ll be in touch.

Prefer email?
[email protected]

General inquiries only. Please do not include patient information. Messages are processed by Web3Forms and delivered to our email.