An electronic medical record search can produce a precise-looking number within a short time. That precision is easy to overinterpret. A record with a relevant diagnosis does not necessarily establish current disease activity, treatment history, interest in research or eligibility for a specific protocol.
For sponsors and CROs, the value of EMR-based clinical trial feasibility lies in the explanation behind the estimate. A useful response identifies the population searched, the evidence available, the uncertainties that remain and the operational steps needed before a potential candidate becomes an enrolled participant.
Define the population before running the search
Begin with a clear description of the source population. Which practices and records are included? How current are they? Does the search cover people recently seen, all historical records or a referral population that is not directly represented in the system?
Then define the unit being counted. Visits, diagnoses and individual people are different units. Multiple encounters can belong to one person, and the same person can appear in several therapeutic categories. A feasibility report should make those distinctions clear before its numbers are compared with another site's estimate.
WCR's patient-access page describes available patient records as a starting point for protocol-specific assessment. It also notes additional physician and referral relationships outside the displayed population. Those routes should be evaluated on their own evidence, without adding overlapping categories or assuming that every referral relationship provides a new, distinct pool.
Separate what is recorded from what is confirmed
Translate the protocol's important criteria into questions the available information can answer. A diagnosis code may support an initial search. A dated clinical note, a medication history or a recent result may be needed to evaluate a more specific requirement.
A practical review can distinguish criteria supported by current information, criteria contradicted by available information and criteria that remain unresolved. Missing information should remain visible as uncertainty. It should not silently become an assumption that the person meets the requirement.
Consider a protocol requiring a particular prior therapy and a recent assessment. The record might show the diagnosis but contain no reliable treatment dates or current result. The next step is a defined clinical review or records request through an appropriate pathway. It is not to classify that person as eligible based on the diagnosis alone.
Use clinical review to test the electronic search
An electronic filter can be too broad or too narrow. It may identify historical conditions that are no longer relevant, miss details recorded only in narrative notes or exclude a person because a field was not populated consistently.
Ask the investigator or qualified clinical team to review how the search translates the protocol. Identify the criteria that most influence the estimate and the source information needed to evaluate them. If a sample of records is reviewed, describe how it was selected and why its findings may or may not apply to the larger population.
The result should be a clearer understanding of the search, not an unsupported claim that the system has confirmed eligibility. Formal eligibility depends on the protocol and the appropriate clinical assessments. Documented review helps the team explain which assumptions can reasonably support an estimate and which still need to be resolved.
Treat permission to review and permission to contact separately
Technical access to information does not, by itself, determine how it may be used for recruitment. The site needs an appropriate process for reviewing records, approaching potential participants and sharing information with other parties.
HHS explains that HIPAA permits research uses and disclosures through individual authorization or specified circumstances, including particular preparatory-to-research activities. These pathways have conditions. A feasibility count should not be treated as general permission to export identifiable records or contact everyone identified by a search.
For the operational plan, establish who can perform each activity and which approvals or permissions apply. Sponsors can usually discuss aggregate feasibility information without receiving patient identities. Keep the distinction between population assessment and participant contact explicit so the recruitment plan reflects an available, appropriate pathway.
Build the estimate as a sequence of transitions
After the initial record review, several questions remain. Can the relevant information be obtained? Can the person be approached appropriately? Are they interested? Can they attend the required visits? Do formal screening results support enrollment?
Describe those stages separately rather than applying a single unexplained conversion percentage to the database. If historical experience informs an assumption, identify the population, protocol demands and period behind it. A rate from a different indication or a much shorter study may not be a useful guide.
It can be helpful to present a range with explicit assumptions instead of one apparently certain number. Explain what would support the more conservative scenario and what would need to be true for the higher scenario. The range should reflect evidence and uncertainty, not serve as a way to make an unsupported estimate look analytical.
Limit the forecast by the actual enrollment window
Even a well-characterized population cannot be processed instantly. Record retrieval, clinical review, participant conversations and screening appointments consume staff time. A required procedure or central assessment can further limit the pace.
Compare the proposed patient pathway with the site calendar. How many appointments can be supported while existing participants continue their visits? Which staff member or service is most constrained? How much of the enrollment window remains after the site is ready?
WCR's feasibility approach brings connected records together with competition, clinical review and operational capacity. The useful output is a plan that acknowledges these constraints, rather than allowing the largest database number to become the enrollment commitment.
Update assumptions with observed study activity
Once recruitment begins, compare the forecast with actual progression. A lower-than-expected response rate calls for a different discussion than repeated clinical screening failures or delayed appointments. Keep the reasons for stalled progression meaningful enough to guide action.
Review changes in protocol requirements, competing studies and available capacity as the study progresses. The original estimate may need revision even when the team is carrying out the agreed plan. A documented change is more useful than allowing an outdated forecast to remain the basis of every status discussion.
Protect the distinction between learning from results and relabeling the original prediction. Keep a record of the original assumptions, the new evidence and the revised estimate. This allows sponsors and sites to understand what changed and improve the next feasibility assessment.
What a defensible EMR feasibility response should include
A sponsor-ready response should make the following points understandable:
- Population: The practices, record period and distinct patient definition used.
- Criteria: The requirements supported by available information and those still unresolved.
- Review: The clinical checks applied to the electronic search.
- Pathway: The appropriate process for contact, records retrieval and screening.
- Capacity: The staff, appointments and procedures available during the enrollment window.
- Uncertainty: The assumptions behind the estimate and the evidence that would change it.
Make the number explainable
A credible estimate can be traced from the source population to the proposed study workflow. Its strength is not the size of the initial search result. It is the team's ability to explain how the available information supports a practical recruitment plan.
Share the protocol, target population and proposed enrollment period through WCR's study inquiry form to begin that assessment. The conversation should turn record access into clear questions, clinical review and realistic next steps.