SPARCCatalog Defining New Service

Information Needed

Definition(s)

Field(s)

Location in SPARC Tree Structure (order):

Where you would like to see your program, core, or service displayed.

Institution:

Top level (i.e. MUSC)

Institution Description:

Information service providers want their users to know about their Institution.

Institution Acknowledgment Language:

Language that is added to emails displayed to user who request services. Language at the institutional level is added to all services.

Institution Super User(s):

Administrators who have access to all providers, programs, cores, and services under this level including draft requests and Admin. Reporting. No emails received at this level

Institution Service Provider(s):

Administrators who have access to all providers, programs, cores, and services under this level receive messages (unless chosen to hold) regarding service requests. Must choose a primary contact from this list to display to users.

Institution Catalog Manager(s):

Administrators who have the rights to change all providers, programs, cores, and services.

Provider:

Top level below Institution (i.e. SCTR)

Provider Description:

Information service providers want their users to know about their Provider

Provider Acknowledgment Language:

Language that is added to emails displayed to users who request services.

Provider Super User(s):

Administrators who have access to all programs, cores, and services under this level including draft requests and Admin. Reporting. No emails received at this level.

Provider Service Provider(s):

Administrators who have access to all programs, cores, and services under this level receive messages (unless chosen to hold) regarding service requests. Must choose a primary contact from this list to display to users.

Provider Catalog Manager(s):

Administrators who have the rights to change any programs, cores, and services belonging to this level.

Program:

Level under Provider (i.e. Research Nexus)

Program Description:

Information service providers want their users to know about their Program.

Program Acknowledgment Language:

Language that is added to emails displayed to users who request services.

Program Super User(s):

Administrators who will have access to all cores, and services under this level including draft requests and Admin. Reporting. No emails received at this level.

Program Service Provider(s):

Administrators who have access to all cores and services under this level receive messages (unless chosen to hold) regarding service requests. Must choose a primary contact from this list to display to users.

Program Catalog Manager(s):

Administrators who have the rights to change any cores and services belonging to this level.

Core:

Level under program (i.e. Nutrition Services)

Core Description:

Information service providers want their users to know about their Core.

Core Acknowledgment Language:

Core Super User(s):

Administrators who will have access to all services under this level including draft requests and Admin. Reporting. No emails received at this level.

Core Service Provider(s):

Administrators who have access to all services under this level receive messages (unless chosen to hold) regarding service requests. Must choose a primary contact from this list to display to users.

Core Catalog Manager(s):

Administrators who have the rights to change any services belonging to this level.

Service:

Level under Program or Core (i.e. Breakfast)

Service Description:

Information service providers want their users to know about their Service.

Related/Linked Service(s)?

Services that will pull into the shopping cart together. Required or suggested?

Abbreviation:

Name displayed in shopping cart when selected. User search terms.

Tags (Epic):

Special functionality that turn features on.

Fulfillment Components (if Fulfillment Tag selected at Split/Notify)

Dropdown descriptions in SPARCFulfillment.

Fulfillment Users (Names or NetID’s)

Users who have access to provide and complete services in SPARCFulfillment.

Rev Code, CDM Code, CPT Code , EAP Code (if Epic Tag selected)

Fields used for mapping services in scripts.

Non-Clincal (Non-Per Patient/Visit) Services (Y/N)

Part 1: Pricing Setup

Pricing Setup is required prior to adding service costs

Display Date:

Effective Date:

Percent of Fee for Federal:

Percent of Fee for Corporate:

Percent of Fee for Other:

Percent of Fee for Member:

Funding Source (Type all that apply below)

College:

Federal:

Foundation:

Industry:

Investigator:

Internal:

Unfunded Student Research:

Step 2: Pricing Map

Pricing map defines cost at a procedure level and looks to pricing schedule for discounts.

Display Date:

Effective Date:

Service Rate:

Cost of service before discounts applied.

Federal Rate:

Rate charged to a Federal study.

Corporate Rate:

Rate charged to Corporate study.

Other Rate:

Defined by Institution.

Member Rate:

Used for collaborative rates.