SPARCRequest Wiki
SPARCFulfillment Visit Report Data Dictionary and Sample Report (v3.6.1)
Data Dictionary
Reports participant visits that started within selected date range parameters and have fulfilled procedures (services). Last columns - Core, Core Procedures Start Time, Core Procedures End Time - are optional to include when running the report.
No. | Column Name | Description | Database Name | Source | Type |
|---|---|---|---|---|---|
1 | Protocol ID (SRID) | System generated from SPARCRequest | protocols.sparc_id - sub_service_requests.ssr_id | Protocol page header SRID column | BIGINT(20) - VARCHAR(255) |
2 | RMID | A unique numeric identifier that links a research study across multiple MUSC electronic research systems | sparc_request.protocols.research_master_id | SPARCRequest Protocol Information page Research Master ID | INT(11) |
3 | Patient Last Name | Family name of the participant | participants.last_name | Patient registry page "Last Name" text field when creating a new participant. | VARCHAR(255) |
4 | Patient First Name | Given name of the participant that precedes the participant’s family name. | participants.first_name | Patient registry page "First Name" text field when creating a new participant. | VARCHAR(255) |
5 | Visit Name | The name of the visit template used for recording a visit | appointments.name | Protocol page, Study Schedule Tab | VARCHAR(255) |
6 | Custom Visit | A manually added visit which is not on the study calendar | appointments.type = ‘CustomAppointment’? | Participant Tracker, Calendar, manually added and have “(Custom Visit)” indication | VARCHAR(255) |
7 | Start Date | The date the visit was initiated | appointments.start_date | Participant Tracker, Calendar, chosen “Start Date” on a chosen visit | DATETIME |
8 | Completed Date | The date he visit was finished | appointments.completed_date | Participant Tracker, Calendar, “Completed Date” on a chosen visit | DATETIME |
9 | Visit Duration (minutes) | The amount of time between visit “Start Date” and visit “Completed Date” | appointments.completed_date - appointments.start_date | Calculated length (in minutes) of a chosen visit | N/A |
10 | Type of Visit | Categories of an encounter selected in SPARCFulfillment | appointments.contents | Participant Tracker, Calendar, “Type of Visit” on a chosen visit | VARCHAR(255) |
11 | Visit Indications | Reasons for incomplete visit or visit not occurring | appointment_statuses.status | Participant Tracker, Calendar, selected “Reason” when Incomplete a procedure on a chosen visit | VARCHAR(255) |
12 | Core | The organization’s Core under which services are grouped. Within the report, multiple rows display different Cores to account for individual Core Procedures Start & End Times per visit. | procedures.sparc_core_name | Participant Tracker “Procedures” table Organization grouping | VARCHAR(255) |
13 | Core Procedures Start Time | The time entered to indicate when the Visit’s group of Core/Program procedures ended for participant. Unique times apply to each Core/Program’s services, rather than to individual services and visits. | procedure_groups.end_time | Participant Tracker Appointments Core/Program End Time | DATETIME |
14 | Core Procedures End Time | The time entered to indicate when the Visit’s group of Core/Program procedures ended for participant. Unique times apply to each Core/Program’s services, rather than to individual services and visits. | procedure_groups.end_time | Participant Tracker Appointments Core/Program End Time | DATETIME |
Sample Report
Copyright © 2011-2026 MUSC Foundation for Research Development