Weekly meeting agenda and minutes
Everyone who touches the data meets every week, and the agenda comes from the registry itself. This page goes with Chapter 11. Follow-ups from the last meeting come first, every item gets a named owner and a date, and the minutes go into shared documentation the whole team can find.
|
Entry |
| Registry |
|
| Condition |
|
| Completed by (role) |
|
| Date |
|
| Version |
|
Registry identifiers only
Use registry identifiers on this page. Do not enter names, dates of birth, contact details, or anything else that could identify a person.
Meeting details
|
Entry |
| Date |
|
| Attended (roles) |
|
| Data extract used (date) |
|
| Minutes taken by (role) |
|
Agenda and minutes
| Item |
Notes |
Decision |
Owner |
Due |
| Follow-ups from the last meeting |
|
|
|
|
| New enrollments since the last meeting, each one reviewed |
|
|
|
|
| Overdue follow-up |
|
|
|
|
| Diagnoses still unconfirmed |
|
|
|
|
| Records to resolve: duplicates and open queries |
|
|
|
|
| Questions people are skipping or answering oddly |
|
|
|
|
| Counts on every data path |
|
|
|
|
| Changes: IRB, vendors, website, new forms or sub-studies |
|
|
|
|
| Unsolicited information from participant contacts |
|
|
|
|
| Anything else |
|
|
|
|
Counts on every data path
After any change to the study, confirm that new data reach every destination.
| Data path |
Count |
As of |
Matches the others? |
| Internal system the coordinators use |
|
|
|
| Database or warehouse |
|
|
|
| Export or environment for external collaborators |
|
|
|
|
|
|
|
Follow-ups assigned
| Action |
Owner (role) |
Due |
Done |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|