Contributors | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
Email Type | Trigger & Purpose | System Setting | User | Admin | ||
# | With Attachment? | # | With Attachment? | |||
Submit Request | Study team clicks “Submit Request” button on Step 5, the system sends notification to service providers that the study is ready to start and to Study team as a summary. *For a previously submitted protocol, only the requests chosen to be submitted will trigger an email. | Recipients: Study team; Administrators who do not have "hold email" setting in SPARCCatalog | 1 | Y | 2 | Y |
Authorized User Change | Study team or admin changes personnel and clicks “Save,” the system sends information regarding changes (additions or deletions). This only occurs when making a change through SPARCDashboard. | Recipients: Study team | N | |||
Notification | Alerts are sent when Study team/admin has received an internal message. | Recipients: Study team and Admins | 4 | N | ||
Survey Notification (to General Users) | 1). In SPARCDashboard, when a super user or service provider changes the sub-service-request status to “Complete,” the system sends out a link to any associated survey(s). 2). In SPARCDashboard, when a super user or service provider clicks "Resend Survey", the system sends out a link to any associated survey(s). | Recipients: PI and requester of completed service(s) with linked surveys. * Survey must be created and linked to the chosen organization in SPARCCatalog | N | |||
Survey Completion Notification (to Super Users) | For institutions who has management groups interested in receiving notification when user submits a service satisfaction survey, “Survey Alert“ can be turned on in SPARCCatalog. When the “Survey Alert“ is turned on in SPARCCatalog and the user submits a service satisfaction survey on a completed request, the super users who are not holding their emails from SPARCRequest will receive a system-generated email titled “Service Survey Completed in SPARCRequest“, with link showing the survey result. | Recipients: Super users who are not holding their emails from SPARCRequest and who are on the split/notify organization of the completed service/request. | N | |||
System Satisfaction Survey Completion | From the System Satisfaction survey link, “Submit” sends the response to system defined users. | Recipients: System defined users (database settings table option: system_satisfaction_survey_cc) * Email must be added in the development environment | N | |||
Deletion of All Services | Study team “deletes” all services in a sub-service-request, the system then notifies corresponding service providers their services are no longer needed. | Recipients: Service providers who do not have "hold email" setting in SPARCCatalog | N | |||
Epic Queue | Studies that have “sent to Epic” chosen are pushed from the Epic Queue daily. The designated personnel, defined by institution, then receive email notifications stating whether the study was sent successfully or not. | Recipients: System defined users (database settings table option: epic_queue_report_to) *Only applies to those institutions using Epic and have the function turned on | Y | |||
Request Amendment | When a user deletes or adds services from an already submitted sub-service- request and re-submits the protocol. *For a previously submitted protocol, only the requests chosen to be re-submitted will trigger an email. | Recipients: Study team; Service providers who do not have "hold email" setting in SPARCCatalog | ||||
Archive/ Unarchive Protocol | When a user archives or unarchives a study or project on SPARCDashboard. | Recipients: Study team; Service providers who have unfinished and non-draft requests on that study or project, who do not have "hold email" setting in SPARCCatalog. | N | |||
Contact Us | When a user clicks the “Contact Us” button under “My Services.” Used to contact SPARC Team. | Recipients: System defined users (database settings table: contact_us_mail_to & contact_us_cc) | N | |||
Listserv | When a user clicks “Listserv” in the SPARCRequest page footer. Used to sign up for SPARC communication(s). | Recipients: System defined users (database settings option: listserv_mail_to) | N | |||
Outside User Account Approval | When a user proceeds to the log in page and selects “Don’t have an account? Sign up.”Used to route email(s) to administrator(s) for approval. *Outside user accounts are configurable; not necessary if using Shibboleth | Recipients: System defined users (database settings option: admin_mail_to & new_user_cc) | N | |||
Reset Password | When a outsider user account holder forgets his/her password and click "Reset Password"; *Outside user accounts are configurable; not necessary if using Shibboleth | Recipients: Outside user account holder | N | |||
Request Access to Protocol | On SPARCDashboard, when a general user uses the "Search All" filter and chooses a protocol in which they require access. | Recipients: The selected study team user on the chosen protocol | N | |||
Protocol Merge | On SPARCDashboard, when an overlord user uses the "Merge Protocols" button and merge two protocols successfully. | Recipients: PI, Requester, and Service Provider Owners who have unfinished service requests on the protocol. | N | N |
...
*Email does not re-send if status has not changed on a request (no service revision).
1. “Submission” Email to User
Title: SPARCRequest Submission (Protocol 20331)
Dear Wenjun He,
A request has been submitted to start services in SPARCRequest. Visit SPARCDashboard to view the status or make any updates to your request.
...
(*Acknowledge language set up in SPARCCatalog is displayed here.)
Attachment: service_request_14826.xlsx
...
2. “Submission” Email to Administrator/Service Providers
Title: SPARCRequest Submission (Protocol 20331)
Dear Jihad Obeid,
A request has been submitted to start services in SPARCRequest and is awaiting your review in SPARCDashboard.
...
(*Acknowledge language set up in SPARCCatalog is displayed here.)
Attachment: service_request_2018222.xlsx
...
Anchor | ||||
---|---|---|---|---|
|
Title: SPARCRequest Authorized Users Update (Protocol 14826)
...
(*Acknowledge language set up in SPARCCatalog is displayed here.)
Anchor | ||||
---|---|---|---|---|
|
Title: New SPARCDashboard Notification (Protocol 14826)
Wenjun He sent you a new notification on your SPARCDashboard in regard to protocol (14826)
(*The title ‘SPARCDashboard’ takes the user directly to the notification message)
Anchor | ||||
---|---|---|---|---|
|
Title: SPARCRequest Survey Notification (Request 14826-0006)
Dear Prathik Harikrishnan,
Thank you for requesting services from MUSC - SCTR - REDCap. The service(s) you requested have now been completed.
Please click on the link(s) below to complete the following survey(s) regarding the service(s) you received. Your feedback is important and appreciated!
...
Anchor | ||||
---|---|---|---|---|
|
6. “Survey Alert” Email to Super User's who are not holding their emails from SPARCRequest and who are on the split/notify Org of the completed service/request
Title: Service Survey Completed in SPARCRequest
Anna Doyle (doylean@musc.edu) has completed a service survey. Results can be found here
Anchor | ||||
---|---|---|---|---|
|
7. “Survey Completion” Email to Administrator
Title: System Satisfaction Survey Completed in SPARCRequest
Wenjun He (hewwe@musc.edu) has completed a system satisfaction survey. Results can be found here
When clicking on the URL included in the email, the corresponding survey answers shows up in the browser for viewing:
...
Anchor | ||||
---|---|---|---|---|
|
8. “Deletion of All Services” Email to Administrator
Title: SPARCRequest Request Deletion (Request 13060-0005)
Dear musc-ocr@musc.edu,
All services have been deleted in SPARCRequest for the Study below to which you have been granted access.
Study Information | |
Study ID | 13060 |
---|---|
Short Title | Test |
Study Title | Testing Emails |
Sponsor Name | Emails Test |
Potential Funding Source | Federal |
...
Please contact SPARCRequest@musc.edu or call (843) 792-8300 for technical assistance or contact the service provider directly for questions related to your service request.
Anchor | ||||
---|---|---|---|---|
|
9. “Epic Queue” Emails to Designated Personnel
9.1 Title: Epic Queue Complete
...
3/9/2017 | ||||
(SPARC ID) | (Protocol Name) | (Funding Source) | ||
First Name | Last Name | Email Address | LDAP UID | Role |
Jordan | Smitley | jbs203@musc.edu | general-access-user | |
Ryan | Mulligan | mulligan@musc.edu | consultant | |
weii | Chen | iac200@musc.edu | primary-pi | |
Michele | Decandio | lmm4@musc.edu | research-nurse | |
Karen | Packard | kap59@musc.edu | other |
Anchor | ||||
---|---|---|---|---|
|
Title: SPARCRequest Amendment Submitted (Protocol 13060)
Dear Wenjun He,
Services have been added or deleted in SPARCRequest and is awaiting your review in SPARCDashboard.
...
Study Notes | ||
User | Date | Note |
---|---|---|
Sarah Brewer | 2/5/2020 | Is there a pharmacy manual available yet for this study? |
Wenjun He | 3/1/2020 | Budget agreement reached. |
A list of requested services is attached.
...
Attachment: service_request_13060.xlsx
...
Anchor | ||||
---|---|---|---|---|
|
Title: SPARCRequest Protocol Archive Notification (Protocol 13365)
Dear Abigail Kelly,
Protocol 13365 has been archived/unarchived in SPARCRequest by Kim Spencer. Your protocol can still be accessed through archived protocols or by this direct link to SPARCDashboard.
...
Please contact SPARCRequest@musc.edu or call (843) 792-8300 for technical assistance or contact the service provider directly for questions related to your service request.
Anchor | ||||
---|---|---|---|---|
|
12. “Contact Us” Email
Title: (User Entered in Email Subject Line)
...
We have received a message from Prathik Harikrishnan (harikrip@musc.edu).
(“free text typed in by user”)
Anchor | ||||
---|---|---|---|---|
|
13. “Listserv” Email
Title: SPARCRequest Listserv
Message: (free text entered by user)
Anchor | ||||
---|---|---|---|---|
|
Title: New SPARCRequest Account Registration
...
Reason for account/login request: (free text)
Approve Account
- OR -
Disapprove Account
Anchor | ||||
---|---|---|---|---|
|
15. "Reset Password" Email
Title: SPARCRequest Reset Password Instructions
Hello test1@musc.edu!
Someone has requested a link to change your password, and you can do this through the link below. This link is valid for one-time use only and will expire 6 hours from the time it was requested.
...
Anchor | ||||
---|---|---|---|---|
|
Title: SPARCRequest Protocols Merge Notification (Protocols 9697, 9702)
...