SPARCRequest Wiki
Epic Interface User Guide (SPARCRequest v3.13.0)
TABLE OF CONTENTS
SPARCRequest and Epic Interface Background
A fully integrated interface between SPARCRequest and Epic has been developed under the promotion of the Medical University of South Carolina. Roll-out with Epic enterprise went live in July 2014.
The purpose of SPARCRequest having an Electronic Health Record (EHR) Interface with Epic (as shown in Figure 1):
Easier creation of research protocol and billing calendar outside Epic
Uniform research pricing and improved billing compliance
Reduce manual and duplicative data entry
Improve data consistency across systems
Comprehensive reporting
Enhance communication across providers
User/research provider management
Figure 1 Functionality and Overlap between SPARCRequest and Epic
Jump to Section:
Data Exchange
Study information is pushed from SPARCRequest to Epic, commonly:
To create an Epic study record for later associating patients to the study in Epic
To create the Epic study calendar to manage study billing
To define Epic user rights to allow study staff access to Epic
Information pushed from SPARCRequest to Epic mainly comes from the Study Information and Authorized Users sections (see Figure 2) and the study calendar section (see Figure 3) of SPARCRequest, which helps build the following pieces in Epic:
Research study administrative (RSH) record
Study timeline
Study staff
Funding source identification
Participant Privacy Protections
Figure 2
Figure 3
The NCT# and IRB initial approval and expiration dates entered into SPARC in study details are also pushed into Epic (see Figure 4).
Specific terms in SPARCRequest that match with the ones in Epic are listed below.
SPARCRequest Terms | Epic Terms |
|---|---|
Protocol Information | General Information |
Protocol Title | Study Name (I RSH .2) |
PRO # (IRB #) | IRB Approval Number (I RSH 105) |
Initial IRB Approval Date | Approval Date (I RSH 106) |
IRB Expiration Date | Expiration Date (I RSH 107) |
NCT# | NCT # (I RSH 181) |
Protocol ID | Study Code (I RSH 100) |
Reporting Groupers | |
Funding Source | Report Grouper - Category List 1 (I RSH 3001) |
Study Type generated from SPARC Epic boxIDE, HUD, and HDE# (under Investigational Products)Research Master ID (RMID) | Report Grouper - Category List 3 (I RSH 3011)Report Grouper - Free-Text 2 (I RSH 3002)Report Grouper -Free-Text 3 (I RSH 3003) |
Role | Study Users (role_code) |
Primary PI | Principal Investigator (I RSH 130) (SER needed) |
PI/PD; Co-Investigator; Staff Scientist; Postdoctoral scholar, Fellow, or other Postdoctoral Position; Technician | Other providers (I RSH 140) (SER needed) |
Research Nurse | Nurses (I RSH 150) (SER needed) |
Graduate Research Assistant; Undergraduate Research Assistant; Research Assistant/Coordinator; Billing/Business Manager | Study Coordinators (I RSH 110) (no SER needed; EMP only) |
Faculty Collaborator; Consultant; Mentor; General Access User; Other | Research Contacts (I RSH 120) (no SER needed; EMP only) |
Visit Calendar (Billing Information) | Study Calendar |
ARM | Protocol (I PRL .2) |
Visit | Visit (CYCLE) (I PRL 200) |
Day | Day (CTTEVENT) (I PRL 400) |
Window | Research tolerance (I PRL 470 [minus], I PRL 480 [plus]) |
Service | Component (I PRL 41005) |
Research/Third Party Payer (R/T) | Modifier (I PRL 41007) |
Epic Questions | STUDYTYPE |
Answers to Epic Questions 1 to 5, Logic-driven | Study Type (I RSH115) |
Copyright © 2011-2025 MUSC Foundation for Research Development