Patient registries
Patient Registry Data Capture
ResearchGuru builds the eCRF for a patient registry from your questionnaire/form and protocol, tests it with your team, then hosts and supports the registry database for as long as it runs. One registry can cover one or more conditions, sites, treatment pathways or patient groups.
A registry outlives the people who set it up. Staff change, new questions are added, and the data still have to be comparable ten years on. ResearchGuru builds the registry database, hosts it and looks after it, with roles and permissions set according to each organisation's responsibilities.
One registry, seen by each site and by the coordinating centre. Illustrative example.
At a glance
Long-term registry data, collected the same way at every site
At any data cut, numbered tables, figures and listings and the statistical analyses are produced inside the registry.
Data collection, data analysis and study reports in one platform.
Registry types
One platform for the registries research teams run
What we build
From first registration to long-term follow-up
We turn your dataset definition into a registry with short, standard item codes, coded answer lists and the checks that keep entries consistent between sites and over the years.
Clinicians and site staff enter clinical data. Patients can complete their own follow-up questionnaires on a phone, tablet or computer, linked to the same record.
Registry functionality can include
| Role | View | Enter | Review | Export | Admin |
|---|---|---|---|---|---|
| Site user | – | – | – | ||
| Data manager | – | – | |||
| Monitoring user | – | – | – | ||
| Read-only reviewer | – | – | – | – | |
| System administrator | – | – | – | – |
Running the registry
Built to keep going, and to change safely
Registries grow. New forms and follow-up stages are added through a documented change-control process, so data collected before and after a change stay comparable, and every published version of the forms is on record.
Year after year
Two views of the same registry
A registry has to serve the people who enter the data and the people who answer for it. Access is set by site and by role, and every grant is recorded.
Data-processing roles, hosting location and retention are documented in the service agreement.
Getting started
Three ways a registry usually begins
Most registries do not start from nothing. We agree the route with you during the document review.
A new registry
You send the dataset definition and governance documents. We build the forms, test them with your users and activate.
A registry kept in spreadsheets
The existing records are imported in a controlled step, with the import and its reason recorded, after the new forms have been tested.
A registry outgrowing its current system
We map the current variables to the new forms and agree with you what is carried over and how it is checked.
Frequently asked questions
Patient registries: common questions
Something else? Get in touch and a senior researcher will answer.
You do. Data-processing roles, access arrangements, retention and final delivery are documented in the applicable agreement.
Yes. Access is set by site and by role, so site staff work with their own patients while the coordinating team has the overview.
Yes, through change control. The change is assessed, programmed, tested and approved, and the form version is recorded.
Tell us about your registry
Send us your dataset definition and study requirements. We'll review the proposed structure and come back to you with:
Or email admin@edcstat.com · call US/Canada: +1 252 283 8400; Europe: +44 20 8150 0084
