EPSi™ Data Studio User Guide> Space > Other July31,2017 ... ProductLine T_ENCOUNTER_CPT Analysis...

EPSi™ 16.2

Data StudioUser Guide

Item number: EP10068A

Copyright © 2017 Allscripts Healthcare, LLCand/or its affiliates. All Rights Reserved.

www.allscripts.com

Published Date: July 31, 2017 for release 16.2 of EPSi™For further information about this manual or other Allscripts Healthcare, LLC products, contact Global Product Support Services,as follows:

Global Product Support ServicesAllscripts Central Website: https://clientconnect.allscripts.com/welcome (Allscripts Central login is required. Contact informationvaries by product.)

Telephone: http://www.allscripts.com/support-learning/phone-numbers

EPSiTelephone: (Domestic) 877.623.5702; (International) 1+ 636.532.8907 Email: [email protected]

The Documentation Center of Excellence welcomes your opinion regarding this document. Please e-mail your comments andsuggestions to [email protected] or send them to the EPSi Support email address shown above.

Proprietary Notice© 2017 Allscripts Healthcare, LLC and/or its affiliates. All Rights Reserved.

This document contains confidential and proprietary information protected by trade secret and copyright law. This document, theinformation in this document, and all rights thereto are the sole and exclusive property of Allscripts Healthcare, LLC and/or itsaffiliates, are intended for use by customers and employees of Allscripts Healthcare, LLC and/or its affiliates and others authorizedin writing by Allscripts Healthcare, LLC and/or its affiliates, and are not to be copied, used, or disclosed to anyone else, in wholeor in part, without the express written permission of Allscripts Healthcare, LLC and/or its affiliates. For authorization from AllscriptsHealthcare, LLC to copy this information, please call Allscripts Global Product Support Services at 888 GET-HELP or 888438-4357. Notice to U.S. Government Users: This is “Commercial Computer Software Documentation” within the meaning ofFAR Part 12.212 (October 1995), DFARS Part 227.7202 (June 1995) and DFARS 252.227-7014 (a) (June 1995). All use,modification, reproduction, release, performance, display, and disclosure shall be in strict accordance with the license terms ofAllscripts Healthcare, LLC and/or its affiliates. Manufacturer is Allscripts Healthcare, LLC, and/or its affiliates, 222 MerchandiseMart Plaza, Suite #2024, Chicago, IL 60654.

IMPORTANT NOTICE REGARDING GOVERNMENT USEThe software and other materials provided to you by Allscripts Healthcare, LLC include "commercial computer software" andrelated documentation within the meaning of Federal Acquisition Regulation 2.101, 12.212, and 27.405-3 and Defense FederalAcquisition Regulation Supplement 227.7202 and 52.227-7014(a). These materials are highly proprietary to Allscripts Healthcare,LLC and its vendors. Users, including those that are representatives of the U.S. Government or any other government body, arepermitted to use these materials only as expressly authorized in the applicable written agreement between Allscripts Healthcare,LLC and your organization. Neither your organization nor any government body shall receive any ownership, license, or otherrights other than those expressly set forth in that agreement, irrespective of (a) whether your organization is an agency, agent,or other instrumentality of the U.S. Government or any other government body, (b) whether your organization is entering into orperforming under the agreement in support of a U.S. Government or any other government agreement or utilizing any U.S.Government or any other government funding of any nature, or (c) anything else.

EPSi™ is a trademark of Allscripts Software, LLC and/or its affiliates.

All trademarks, service marks, trade names, trade dress, product names, and logos are property of their respective owners. Anyrights not expressly granted herein are reserved.

The names and associated patient data used in this documentation are fictional and do not represent any real person living orotherwise. Any similarities to actual people are coincidental.

Images and option names used in this documentation might differ from how they are displayed in your environment. Certainoptions and labels vary according to your specific configuration. Images are for illustration purposes only.

Fee schedules, relative value units, conversion factors and/or related components are not assigned by the AMA, are not part ofCPT, and the AMA is not recommending their use. The AMA does not directly or indirectly practice medicine or dispense medicalservices. The AMA assumes no liability for data contained or not contained herein.

Excel and Microsoft are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or othercountries.

Adobe, the Adobe logo, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated inthe United States and/or other countries.

iPhone® and iPad® are trademarks of Apple Inc., registered in the U.S. and other countries.

Perceptive Content, Lexmark, and the Lexmark logo are trademarks of Lexmark International, Inc., registered in the United Statesand/or other countries.

Allscripts Patient Administration Solution (PAS) contains barcode components licensed from IDAutomation.com, Inc. Theseproducts may only be used as part of and in connection with the Allscripts Patient Administration Solution software.

Table of Contents

Chapter 1: EPSi solutions overview.............................................................................5

Chapter 2: Data Studio.......................................................................................................6Access Data Studio..................................................................................................................6Data Studio control panel.........................................................................................................6Breadcrumbs............................................................................................................................7Task Engine..............................................................................................................................7Data Studio toolbar options......................................................................................................8

Chapter 3: Setting up Data Studio schedules.........................................................11Add a new schedule...............................................................................................................11

Edit a schedule.................................................................................................................12Delete a schedule............................................................................................................14

Add jobs to a schedule...........................................................................................................14

Chapter 4: Tasks.................................................................................................................16Add tasks to a job...................................................................................................................17Standard Data Load...............................................................................................................18

Set up the destination data..............................................................................................19Edit the destination data definition.............................................................................20

Set up the source data.....................................................................................................21Edit the source data definition....................................................................................22

Edit location - File Details.................................................................................................24Edit location - Database Details.......................................................................................25Map a source to a destination..........................................................................................26

Edit mapping..............................................................................................................26Add a conversion table...............................................................................................27

Subtasks..........................................................................................................................29Pre-processing subtasks............................................................................................29Pre-merge subtasks...................................................................................................30Post-merge subtasks.................................................................................................36

Summarization task...............................................................................................................37Summarize patient data...................................................................................................37Transfer activity codes and statistics...............................................................................41

July 31, 2017 | EPSi™ 16.2 3Data Studio User GuideCopyright © 2017 | Allscripts Healthcare, LLCThis page contains Allscripts proprietary information and is not to be duplicated or disclosed to unauthorized persons.

Merge patient accounts....................................................................................................42Merging patient data examples..................................................................................45

Product line assignment...................................................................................................48Calculating contract models.............................................................................................49Variance years.................................................................................................................50Rule sets..........................................................................................................................50Calculating estimated net revenue...................................................................................50Clinical Analysis refresh...................................................................................................51Activity cost assignment...................................................................................................51

Run the Report Schedule Groups task..................................................................................52

Chapter 5: Executing Data Studio Schedules and viewing logs......................54Configuration status...............................................................................................................54Running a schedule...............................................................................................................54

Task engine and task execution logs...............................................................................55Error logs..........................................................................................................................56

View the Batch Record Report...............................................................................................56Delete a batch..................................................................................................................57

View schedule history............................................................................................................58View reprocessing data..........................................................................................................59

Appendix A: General Ledger data schedules...........................................................61

Appendix B: Recommended Payroll data schedules............................................64

Appendix C: Recommended Product Line Analysis data schedules..............67

Appendix D: Recommended Activity Costing data schedules...........................76

Appendix E: Setting up Data Extender loads............................................................78

Appendix F: Allscripts Clinical Performance Management schedule load....79

Index..........................................................................................................................................83


Table of Contents

Chapter 1

EPSi solutions overview

The following image outlines the modules associated with the EPSi™ suite of applications.

Data is obtained from source applications and then loaded into the EPSi applications using theData Loader and Data Studio applications. The Security application controls user access to eachmodule.

Figure 1: Overview of EPSi applications


Chapter 2

Data Studio

The EPSi Data Studio module enables you to load data from any third-party application into theEPSi SQL database using English language (ASCII) text files in either fixed width or delimitedformat.

Your organization can perform data loads manually or you can schedule the data loads to occurautomatically on a daily, weekly, or monthly basis. Error reporting and audit histories are performedautomatically with each data load.

Access Data StudioAccess the Data Studio application through the portal.

1. In the portal, click the Application Launcher .A list of applications is displayed.

2. Select Admin Tools > Data Studio.Data Studio opens and Data Studio Schedules is displayed.

Data Studio control panelThe Data Studio control panel enables you to access each Data Studio function directly.

Click to launch the control panel.

Data

View or edit data that is available in Data Studio. You can view, add, and delete data storesand data definitions.

Maps

View available maps of source to destination.

Task Engines

View or add task engines available for Data Studio.


Access Data Studio

Logs

View Task Engine and Task Execution logs.

Schedules

View or add schedules.

Jobs

View jobs for data loads, data extracts, and data migrations.

Tasks

View tasks for data loads, data extracts, and data migrations.

Network Shares

View the network shares, or cloud based storage, that have been configured.

Related informationTask Engine on page 7Setting up Data Studio schedules on page 11Tasks on page 16

BreadcrumbsBreadcrumbs refers to the trail of windows that you have accessed, displayed under the Homeribbon in Data Studio.

Breadcrumbs display the navigation path, which is the windows or functions that you haveprogressed through. You can click a breadcrumb to return to that function.

Figure 2: Breadcrumbs

Task EngineThe Task Engine performs the scheduled jobs or tasks configured in Data Studio.

You can have multiple task engines, but it is best practice to use only 1.


Breadcrumbs

Task engines are configured during implementation. Use Task Engines in the Data Studio controlpanel to add or edit task engines.

Data Studio toolbar optionsThe options in the Home toolbar change depending on the task you are accessing.

Table 1: Home toolbar options

FunctionIcon

Application

Settings enables you to minimize the toolbar. To display the toolbarwhen it is minimized, click the Home tab.

Schedule History enables you to view the history and results ofexecuted schedules at the individual task level.

Click Save to save any changes you make.

Click Cancel to return to the previous window, which is displayed in thebreadcrumbs. Any changes you have made are not saved.

Click Tools to view or delete batch and reprocessing table information.Batch Record Report enables you to filter a search for batch recordreports by batch number and date range, or by only date range. Youcan also search for only records that have errors. Delete Batch enablesyou to delete a batch. View Reprocessing Table Data enables you toview and delete charge or payment records that were loaded with nocorresponding encounter record.

Use Product to select the product by module. The product structure isset up as a hierarchy. When you select a product, you will see thatproduct and any products under it in the hierarchy.

Schedules

Click Add Schedule to add a new schedule.

Click Delete Schedule to delete an existing schedule.


Data Studio toolbar options

FunctionIcon

Click Copy Schedule to copy and then modify an existing schedule.When you create a copy of a schedule, all of the associated tasks andjobs are also copied.

Schedule Type

Click On-Demand to run a schedule at any time.

Click Once to run the schedule once.

Click Daily to run the schedule on a daily schedule.

Click Weekly to run the schedule on a weekly schedule.

Click Monthly to run the schedule on a weekly schedule.

Schedule

Use Hide Details to hide or show additional information in the Detailsarea.

Click Add Job to add a new job to the selected schedule.

Click Delete Job to delete an existing job from the selected schedule.

Click Reassign Job to move a job from an existing schedule to theselected schedule.

Click Execute Schedule to run a schedule.



FunctionIcon

Click Cancel Schedule to cancel a schedule.

Click Add Task to add a task to a job and select the type of task.

Click Delete Task to delete a task from a job.

ClickReassign Task to move a task from an existing job to the selectedjob.

Standard Data Load Task

Click Download Error File to view the file with the records that wererejected in a task and the rejection reasons. The error file containsspecific record error messages instead of task-level errors. Task-levelerrors are available in the Data Studio Log Viewer.

Click View Log Messages to view a list of all the events that occurredduring the scheduling process, including records loaded, number oferrors, process completion, and any errors.

Click Add Data Store to add a source data store that will contain thesource data to load.

Click Copy To Server to copy a file to the data store when the locationis selected.

Click Add Data Definition to add a data definition.

Click Add Location to add a data location.

Click Add Mapping to add a mapping when a source and destinationdata definition are selected.

ClickAutoMap Fields to automatically populateSource ColumnNamebased on the matching User-Defined Column Name, or the actualnames in the source with the Target Column Name in the destination.

Click Clear Mappings to clear all the values in Source Column Name.



Chapter 3

Setting up Data Studio schedules

Schedules define a set of jobs and tasks and the frequency that the assigned jobs and tasks arerun. Schedules are defined based on a product or collection of products.

You must complete several steps to fully configure a schedule in Data Studio.

1. Add the schedule.2. Edit the schedule.3. Assign jobs to the schedule.4. Assign tasks to the job.5. Edit the tasks.

As you proceed through the steps of configuring a schedule, the breadcrumbs display each of thefunctions you have set up. Use the breadcrumbs to go to a previous task, or to refresh the currentwindow.

Add a new scheduleSet up data load jobs and tasks to run at specific times.

1. In Data Studio, you can create a new schedule by doing 1 of the following:

> Click to launch the control panel and click Add Schedule under Schedules.

> In Schedules, click .

> In Schedules, select an existing schedule in the grid and click to copy and then modify anexisting schedule.When you create a copy of a schedule, all of the associated tasks and jobs are also copied.

New Schedule opens.


2. For Name, enter a schedule name.3. For Description, enter a description of the schedule.4. For Task Engine, select the applicable task engine.5. Click OK.

Edit Schedule opens.

Related informationEdit a schedule on page 12Delete a schedule on page 14Setting up Data Studio schedules on page 11Add jobs to a schedule on page 14

Edit a scheduleDefine schedules in Edit Schedule. You can define the frequency and timing of the schedule andassign jobs to the schedule.

Use Product in the Home toolbar to filter schedules by product. You can also use Filter to filterthe schedules by name, description, and product.


Add a new schedule

1. In Data Studio, click to launch the control panel.2. Click View Schedules.3. To edit an existing schedule, double-click a schedule in the Schedules grid.

When adding a new schedule, Edit Schedule is displayed when you click OK in NewSchedule.Edit Schedule is displayed.

4. In the Schedule Type toolbar, select the frequency that the schedule runs: On Demand,Once, Daily, Weekly, or Monthly.

5. Specify the schedule settings for the selected schedule type.> If you select Once, select a Start at time and a Begin Date for the schedule to run. After the data

load, the schedule is not removed from the scheduled list, but it will not be run again until it isrescheduled.

> If you select Daily, select the day, the Start at time, the Begin Date, and an End By date, EndAfter Occurrences, or No End Date.

> If you select Weekly, select 1 or more days of the week, the Start at time, the Begin Date, and anEnd By date, End After Occurrences, or No End Date.

> If you select Monthly, select 1 or more days of the month, the Start at time, the Begin Date, andan End By date, End After Occurrences, or No End Date.

6. Select Active to activate the schedule.You must select Active for Once, Daily, Weekly, or Monthly schedule types.

7. (Optional) Select On job failure, abort schedule execution to indicate that if 1 job fails, theother jobs associated with the schedule will not run.

8. Click Save.

Related informationAdd a new schedule on page 11Delete a schedule on page 14Setting up Data Studio schedules on page 11Add jobs to a schedule on page 14


Add a new schedule

Delete a scheduleIf you no longer need a schedule to run, you can delete the schedule.

1. In Data Studio, click to launch the control panel.2. Click View Schedules.3. In the Schedules grid, select the schedule to delete.

4. Click .A message is displayed confirming that you want to delete the selected schedule.

5. Click Yes.

Add jobs to a scheduleJobs represent a series of tasks that run sequentially.

1. In Data Studio, click to launch the control panel.2. Click View Schedules.3. To add jobs to an existing schedule, double-click a schedule in the Schedules grid.

When adding a new schedule, Edit Schedule is displayed when you click OK in NewSchedule.Edit Schedule is displayed.


Add jobs to a schedule

4. Click in the Home toolbar.Job Details opens.

5. For Job Name, enter the name of the job.6. For Description, enter a short description of the job.7. For Select Product, select the module.

The only available products are products that exist in the hierarchy of the product selectedfor the schedule.

8. Click OK.The job is added to the schedule and is displayed under Jobs in Edit Schedule.

What to do nextJobs are processed in the order that they are displayed. Use the up and down arrows to changethe job order. You can edit a job by double-clicking it in Edit Schedule.

Related informationAdd a new schedule on page 11Delete a schedule on page 14Setting up Data Studio schedules on page 11Edit a schedule on page 12Tasks on page 16


Add jobs to a schedule

Chapter 4

Tasks

Tasks represent the actions that occur in a job. The options for tasks includeData Studio Cleanup,Execute Report Schedule Groups, Execute SSIS Package, Standard Data Load, StoredProcedure, and Summarization.

Table 2: Data Studio tasks

FunctionTask

Data Studio Clean Up cleans up Data Studio data byremoving temporary tables or orphaned data.

Execute Report Schedule Groups runs specificreporting schedule groups as part of the job. Schedulegroups are created in Reporting Manager.

Execute SSIS Package enables you to execute SQLServer® Integration Services packages as a part of theEPSi™ load process and to build custom processingpackages.

Standard Data Load loads data from a file or databaseto another file or database.

Stored Procedure runs stored procedures as part ofthe job.

Summarization Task runs specific tasks on the loadeddata such as summarizing patient data, product lineassignments, merging patient accounts, activity codeand statistic transfers.


Add tasks to a jobTasks are the actions that occur in a job.

1. Under Jobs in Edit Schedule, double-click a job.Edit Job opens.

2. In the toolbar, click Add Task and select the task to add.> Data Studio Clean Up> Execute Report Schedule Groups> Execute SSIS Package> Standard Data Load> Stored Procedure> Summarization Task

3. Click Save.

What to do nextTasks are processed in the order that they are displayed. Use the up and down arrows to changethe task order.After adding tasks to a job, edit the task by double-clicking it.

Related informationStandard Data Load on page 18Tasks on page 16


Add tasks to a job

Standard Data LoadThe Standard Data Load task enables you to copy data from a source file or database into adestination database. In Standard Data Load Edit, identify the source and the destination andhow the source maps to the destination table.

There are 3 parts to source and destination selection.

> Data store: File or database> Location: Physical location or instance of the data store> Data definition: The selected file or table in the selected database

To set up Standard Data Load Edit, click the numbered icons in Work Flow. Steps 1 through 3are associated with selecting the destination, steps 4 through 6 are associated with selecting thesource, and step 7 identifies how the source data maps to the destination data. When you click astep number in the Data Studio application it identifies the associated item.

1. Select a destination database to load the data into.2. Select a destination database location to load data into.3. Select a destination table to load data into.4. Select or add a source data store that will contain the source data to load.5. Select a source location to load data from.6. Select or add a source data definition that defines the format to load data from.7. Select or add a map that is associated with the source and destination data definitions.

You can use the filter box in Toolbox throughout the work flow to limit the list of items.

Note: Data Studio supports loading data from 1 database table to another.However, loads specifically to EPSi destinations do not currently supporttable-to-table loads.

Related informationSet up the destination data on page 19Edit the destination data definition on page 20Set up the source data on page 21Map a source to a destination on page 26Edit mapping on page 26


Standard Data Load

Set up the destination dataSelect the destination database, location, and table to load the source data into.

Before you beginAdd a Standard Data Load task to a job.

Note: The destination data store for EPSi™ standard tables is EPSIDatabase. The destination data store for loading conversion table valuesis DataStudio Database.

1. Navigate to Schedules > Edit Schedule > Edit Job and double-click the standard data loadtask.Standard Data Load Edit opens.

2. Under Work Flow, click .Information for Step: 1 - Target Database is displayed.


Standard Data Load

3. In Toolbox, select the destination database to load data into by double-clicking the database,or by dragging the database from Toolbox to 1 - Database.

4. Under Work Flow, click .Information for Step: 2 - Target Location is displayed.

5. In Toolbox, select the location to load data into by double-clicking the location, or by draggingthe location from Toolbox to 2 - Location.If there is only 1 location set up for the destination database, the location is automaticallypopulated.

6. Under Work Flow, click .Information for Step: 3 - Target Table is displayed.

7. In Toolbox, select the definition, or table, to load data into by double-clicking the table, or bydragging the location from Toolbox to 3 - Data Definition.

8. Click Save.The Configurations pane populates with subtasks.

Results of this taskThe Destination data information is setup.

What to do nextSet up the Source information.

Related informationSubtasks on page 29

Edit the destination data definitionAfter setting up the destination data to load the source data into, you can edit the data definition.

For system defined data definitions, you can only edit the user-defined column name.

1. Navigate to Schedules > Edit Schedule > Edit Job and double-click the standard data loadtask.

2. In Standard Data Load Edit select the destination data information (Work Flow steps 1through 3).

3. In 3 - Data Definition, click .Edit Data Definition opens.

4. Select a data definition item in the grid.5. For User Defined Column Name, enter a column display name to use in Auto Map Fields.6. Click Save.


Standard Data Load

What to do nextClick Standard Data Load Edit in the breadcrumbs to continue setting up the task.

Set up the source dataSet up the source data information that contains the source data to load into the destination.

Before you beginAdd a Standard Data Load task to a job and select the destination database.


2. In Standard Data Load Edit select the destination data information (Work Flow steps 1through 3).

3. Under Work Flow, click .Information for Step: 4 - Source Data Store is displayed.

4. Select the source data store.> In Toolbox, select the source data store that will contain the source data to load by double-clicking

the data store, or by dragging the data store from Toolbox to 4 - File/Database Data Store.> Click Add Data Store to add a new database or file to use in the source.

5. (Optional) You can edit the source data store or file by clicking in 4 - File/Database DataStore.Databases that have a lock icon, such as the EPSI Database, cannot be edited.

6. Under Work Flow, click .Information for Step: 5 - Source Location is displayed.

7. Select a source location.> In Toolbox, select the source location that will contain the source data to load by double-clicking

the data store, or by dragging the data store from Toolbox to 5 - Location.> Click Add Location to add a new source location.Source files must be on network servers that can be accessed by the task engine. Click CopyTo Server to copy a file from your computer. The source file must be flagged to use thestandard upload path to enable file uploading.

8. (Optional) Edit the source database or file by clicking in 5 - Location.

9. Under Work Flow, click .Information for Step: 6 - Source Data Definition is displayed.


Standard Data Load

10. In Toolbox, select the source data definition to load by double-clicking the data definition, orby dragging the data definition from Toolbox to 6 - Data Definition.

11. (Optional) Edit the source data definition by clicking in 6 - Data Definition.12. Click Save.

Related informationEdit location - File Details on page 24Edit location - Database Details on page 25

Edit the source data definition


2. In Standard Data Load Edit, select the destination definition (Work Flow steps 1 through3).

3. In 6 - Data Definition, click .Edit Data Definition opens.


Standard Data Load

4. If a new column was added to the source extract, click Add Data Definition Column to addthe new column to the data definition.

5. (Optional) Select a column and click Delete Data Definition Column to remove a columnfrom the data definition.

6. (Optional) In Column Name, edit the column headers.7. Select a column and use the up and down arrows to adjust which columns display which

values.8. For Delimiter, select the item that will separate the data.

> Comma> Tab> Semicolon> Space> Other


Standard Data Load

9. For Rows to Display, enter the number of rows you want to view.10. Click Save.

What to do nextClick Standard Data Load Edit in the breadcrumbs to continue setting up the task.

Edit location - File DetailsThe file details identify the network source of the file that you want to load.

Before you beginThis task only applies to setting up a network source.


2. In Standard Data Load Edit, for 2 - Location or 5 - Location, click .File Details opens.

3. For Location Name, enter a name.4. SelectUse standard upload path to move a file from your workspace to a predefined location

on the network share.

Note: This option is not available if you are using a Microsoft Azure™

environment.

5. For Network Share, select the network share that contains the file.If there is only 1 network share configured, the box is automatically populated.

6. For File Name, click the browse button (...) to locate the source file.File Path and Full File Path fill based on the file name.


Standard Data Load

7. Click Save.

Edit location - Database DetailsSet up the database details to identify the Microsoft SQL Server® database to connect to yournetwork to load data into the EPSi™ database.

Before you beginThis task only applies to setting up databases.


2. In Standard Data Load Edit, for 2 - Location or 5 - Location, click .Database Details opens.

3. For Location Name, enter a name for the location.4. For Server Name, enter the name of the source server.5. For Database Name, enter the name of the source database.6. If the database has an instance, enter the name in Instance Name.7. For User ID and Password, enter the name and password of the SQL administrative user.8. Click Save.


Standard Data Load

Map a source to a destinationSelect an existing mapping that is associated with the source and destination data definitions.


2. In Standard Data Load Edit, under Work Flow, click .Information for Step: 7 - Map is displayed.

3. In Toolbox, select the mapping by double-clicking the data store, or by dragging the mappingfrom Toolbox to 7 - Mapping.

4. (Optional) Edit the data mapping by clicking in 7 - Map.5. Click Save.

Edit mappingYou can edit an existing mapping that associates the source with the destination data definitions.

Before you beginAdd data mapping to a Standard Data Load task.


2. (Optional) Edit the mapping by clicking in 7 - Map.Edit Map opens. Target Column Name is filled with the destination data definition fields.Required fields are grouped at the top of the list.


Standard Data Load

3. (Optional) Click Auto Map Fields to automatically populate Source Column Name basedon the matching User-Defined Column Name, or the actual names in the source with theTarget Column Name in the destination.

4. Click Source Column Name next to the Target Column Name you want to map.The available fields contained in the source data definition are displayed.

5. Select the source data definition field to map to the Target Column Name.6. (Optional) For Default Value, enter a default value to populate the field with.

If a source field is mapped to a destination field and a value is provided from the input source,the default value does not override it. The default value is only used if the input does notcontain a value. You can enter ##CURRENTDATE in Default Value to populate the currentdate as the default value.Enter a default value for Default Value for any row with Allow Null and Is Enabled selected.Fields that must contain a value are marked as enabled. Reference Database Default todetermine the database default. To enter a Default Value for a field that is a primary key, youmust clear Required for that row.

7. To update all fields when loading data, select Is Enabled. To only update specific fields, selectonly the box next to those specific fields.Key fields are always updated and are identified in Is Primary Key.

8. Use Conversion to convert values in the source field to the values necessary for thedestination.a) Click Conversion.

The available conversion tables are displayed.

b) Select an existing conversion table or click Add New to add a new conversion table.Using a conversion table, you can change a value in the input file to a value specified inthe conversion table.

9. Click Clear Mappings to clear all the values in Source Column Name.10. Click Save.

Add a conversion tableUse Conversion to convert values in the source field to the values necessary for the destination.Using a conversion table, you can change a value in the input file to a value specified in theconversion table.

Note:For work flow items 4 through 7, Toolbox is empty unless you create theapplicable item for each step.


Standard Data Load

You can double-click items to add them from Toolbox, or drag and dropthem to the applicable Data Flow step.


2. Under Destination, for 1 - Database, select DataStudio Database from Toolbox.

The information for 2 - Location is configured by the EPSi™ implementation team.

3. For 3 - Data Definition, select Conversions from Toolbox.

a) Click in 3 - Conversions to edit the destination data definition.b) Enter the conversion information.c) Click Save.d) Click Standard Data Load Edit.

4. Under Source, for 4 - File/Database Data Store, select the file to be loaded from Toolbox.You might need to define a data store by clicking Add Data Store if it is not already defined.

5. For 5 - Location, select the location of the file from Toolbox.You might need to add a location by clicking Add Location if it is not already defined.


Standard Data Load

6. For 6 - Data Definition, select the format of the data from the Toolbox.7. For 7 - Map, select the user-defined mapping from Toolbox.

You might need to define the mapping by clicking Add Mapping in the toolbar if it is notalready defined.

8. Click Save.

SubtasksSubtasks represent additional processes that are run at various stages of the task process andare dependent on the destination data definition.

Pre-processing, pre-merge, and post-merge subtasks are displayed in the Configurations paneof Standard Data Load Edit after you select the destination data definition and save the task.

Related informationPre-merge subtasks on page 30Pre-merge subtask descriptions on page 34Post-merge subtasks on page 36

Pre-processing subtasksPre-processing subtasks are tasks that are performed before processing the source data. Theseactivities are based on the destination data definition that you select.

Table 3: Pre-processing subtasks

DescriptionNameData DefinitionModule

Log new entriesLog new entriesT_ACTIVITYVarious EPSi ModulesT_COST_CENTERST_GL_ACCOUNTST_JOB_CLASSEST_PAY_TYPEST_STATISTIC_ACCOUNTST_SUB_ACCOUNTS

Selecting Log new entries logs new data, such as cost centers, subaccounts, or job classes, thatare loaded into the application. You can run reports in Reporting Manager that identify new entrieslogged.


Standard Data Load

Pre-merge subtasksPre-merge subtasks are performed prior to merging the source data into the destination data.These activities are based on the destination data definition selected.

Table 4: Pre-merge subtasks

FunctionsSubtasksData DefinitionModule

Load GL DataT_GL_ACCOUNT_INPUTG/LBudgeting

> Log Updates> Data Set> Account Ranges> Reverse Signs

Account RangesLoad SubAccount Data

T_SUB_ACCOUNTSG/LBudgeting

Load LaborDistribution

T_EMPLOYEE_RESULTSPayroll > Log Updates> Summarize Data

Delete All Existing PatientAccount Tables(Secondary Tables)

Load PatientEncounters

T_IP_ENCOUNTERT_OP_ENCOUNTERT_LOAD_ENCOUNTER_FIELDS

Product LineAnalysis

Charge DetailT_IP_CHARGESProduct LineAnalysis

> Delete Existing PatientAccount InformationT_OP_CHARGES

> Summarize Values InInput File

> Summarize InputValues With ExistingValues

> Compute TotalCharges

> Compute Unit ChargeAmount

> Look up RevenueCenter

Log Updates SummarizeData

Monthly LaborT_LOAD_EMPLOYEE_RESULTS_MONTHLYPayroll


Standard Data Load


Daily LaborMaster

T_EMPLOYEE_RESULTS_DAILY_DETAILPayroll > Summarize Values InInput File


> Delete Existing EntriesFor Days In Input File

Statistics DailyInput

T_STATISTIC_DAILY_INPUTG/LBudgeting



> Delete Existing EntriesFor Days In Input File


Load EncounterSupport Tables

T_ENCOUNTER_APCProduct LineAnalysis



T_ENCOUNTER_APGProduct LineAnalysis



T_ENCOUNTER_CPTProduct LineAnalysis



T_ENCOUNTER_ICD9DXProduct LineAnalysis



T_ENCOUNTER_ICD9PXProduct LineAnalysis



T_ENCOUNTER_PHYSICIANProduct LineAnalysis



T_ENCOUNTER_DAY_TYPEProduct LineAnalysis


Standard Data Load




T_IP_ENCOUNTER_EXTProduct LineAnalysis



T_OP_ENCOUNTER_EXTProduct LineAnalysis

Charge DetailT_LOAD_CHARGES_FIELDSProduct LineAnalysis

> Delete Existing PatientAccount Information



> Compute Total Charge> Compute Unit Charge

Amount> Look up Revenue

Center

Charge DetailT_ACTUAL_PAYMENTS_001Product LineAnalysis




> Reverse PaymentsSign

> Reverse AdjustmentsSign

> Reverse Refunds Sign> Reverse Write Offs

Sign

Charge DetailT_ENCOUNTER_REMIT_001Product LineAnalysis




Standard Data Load

FunctionsSubtasksData DefinitionModule> Summarize Input

Values With ExistingValues


Load FlattenedTables

T_LOAD_ENCOUNTER_APC_FIELDSProduct LineAnalysis



T_LOAD_ENCOUNTER_APG_FIELDSProduct LineAnalysis



T_LOAD_ENCOUNTER_CPT_FIELDSProduct LineAnalysis



T_LOAD_ENCOUNTER_ICD9DX_FIELDSProduct LineAnalysis



T_LOAD_ENCOUNTER_ICD9PX_FIELDSProduct LineAnalysis



T_LOAD_ENCOUNTER_PHYSICIAN_FIELDSProduct LineAnalysis

Load a physician tableand records to allfacilities.

Load PhysiciansT_PHYSICIANSProduct LineAnalysis

Delete Existing AssetsAsset TrackingT_CAP_ASSET_TRACKINGCapital

Summarize Values InInput File

CA IndicatorT_LOAD_CA_INDICATORProduct LineAnalysis

Apply ContingencyCapital InvoiceData

T_LOAD_CAP_INVOICECapital

Apply ContingencyCapital PO DataT_LOAD_CAP_PURCHASE_ORDERCapital

Related informationPre-merge subtask descriptions on page 34


Standard Data Load

Pre-merge subtask descriptionsThe following are descriptions of subtasks that are performed prior to merging the source datainto the destination data

Account ranges

Account Type is required for general ledger files. If you have not supplied the account typesfor revenues, expenses, and deductions in the source file, you can assign the account typebased on the account ranges. Click Add Account Range and select the account type —revenue, expense or deduction. Enter the subaccount From and To codes and the cost centerFrom and To code, if applicable. Click OK to add the information to Account Ranges.

Data set

Select the data set to load general ledger subaccount values into. The data set you select isused to validate that the general ledger data is loaded into the applicable data set and mustmatch the values in the source file or default value in the mapping.

Reverse signs

Select Revenues, Expenses, or Deductions to reverse the signs during the load process.

Summarize data

Select Summarize Data to add values in the input file where all key fields match prior to mergingthe data. Key fields associated with a labor distribution file are data set, facility, cost center, jobclass, employee ID, pay type, and pay period. Summarizing the data prevents duplicate recorderrors during the data load process, if multiple entries that match all key fields exist in the sourcedata definition.

Delete All Existing Patient Account Tables (Secondary Tables)

SelectDelete All Existing Patient Account Tables to search for the facility and patient accountfrom the input data file in all of the encounter tables (encounter, encounter charge detail,encounter ICD9 Dx, encounter ICD9 Px, encounter CPT-4, actual payments, encounter APC,and encounter physician) and delete every occurrence of it. Only select Delete All ExistingPatient Account Tables if you are reloading all of the facility and patient account informationfor patient accounts that were deleted.


Standard Data Load

Delete Existing Patient Information

Select Delete Existing Patient Information to search for the facility and patient account in thedatabase and compare them with the input file. If a match is found, all of the records for thepatient in the table are removed from the database and replaced with the records from the inputfile.For example, if the encounter CPT data definition is selected, the deletion would only apply tothe CPT table. If the encounter ICD-10 diagnosis or encounter ICD-10 surgical procedure loadsare selected, only that table is deleted.This option assumes all of the information for those patient accounts will be reloaded correctly.

Summarize Values in Input File

Summarizes the input data based on the key fields before data loading. If you alreadysummarized the data based on the key fields, selecting Summarize Values in Input File doesnot affect anything. If you do not select this option and have not summarized, it rejects everyrecord that matches on the key fields.

Summarize Input Values with Existing Values

Appends the input data with the data previously data loaded based on the key fields. If you donot select Summarize Input Values with Existing Values and you match on the key fields,the non-key fields are be overwritten.

Note: Do not select both Delete Existing Patient Information andSummarize Input Values with Existing Values.

Compute Total Charges

If you can only supply the number of units and average charge amount in the input data file,selecting Compute Total Charges multiplies number of units and average charge amount andpopulates Detail Total Charge.

Compute Unit Charge Amount

If you can only supply the number of units and detail total charge amount in the input data file,selecting Compute Unit Charge Amount divides the number of units and detail total chargeamount and populates Unit Charge Amount.


Standard Data Load

Lookup Revenue Center

If you cannot supply the revenue center in the input data file, selecting Lookup Revenue Centersearches for the revenue center based on the facility and the activity code before data loading.The activity codes must be unique by facility and not by revenue center. The selected activitydata set is the year used for the search.

Load Physicians

Select Load Physician Subtask for the T_PHYSICIANS data definition to load all physicianrecords from the input file into all of the facilities in the facility table. One valid facility ID isrequired in the input file, or as a default value in the mapping function.

Post-merge subtasksPost-merge subtasks are performed after merging the data into the destination. These activitiesare based on the destination data definition selected.

Table 5: Post-merge subtasks

FunctionsSubtaskData DefinitionModule

Assign Account CategoriesAssign AccountCategories

T_GL_ACCOUNT_INPUTT_STATISTIC_INPUT

G/L Budgeting

Synchronize Encounter withDSM

SynchronizeEncounter

T_PAT_DSM_INVENTORYProduct LineAnalysis

Update Cost Summary FromDSM

Update CostSummary

T_DSM_COSTSProduct LineAnalysis

If you set up Assign Account Categories, any new subaccounts are assigned to their respectiveaccount categories based on the Account Category Mapping Definitions setup in Enterprise

Analyst. To set up Assign Account Categories, select the data set and click to move theaccount categories from Unassigned to Assigned.


Standard Data Load

Summarization taskThe Summarization task enables you to run various data assignments and summarization ondata entered in the schedule that the job or task is assigned to.

The Summarization task is only processed on the data that is loaded in jobs or tasks that areperformed before the Summarization task in the same schedule.Navigate to Schedules > Edit Schedule > Edit Job and double-click the summarization task.

Figure 3: Summarization Task

Under General Details, Process Order identifies the order of the summarization steps. You canchange the process order using the arrows.

Summarize patient dataUse theSummarize Patient Data task to populate fields in the patient encounter table. Summarizingpatient data expedites reports and adds new fields for analysis purposes.

You can select 1 or multiple options to summarize. Data Studio summarization only summarizesthe data from the input file.You can also access patient summarization functionality from the Product Line Analysis PatientControl Panel. From Patient Control Panel, you can summarize the historical data that waspreviously loaded.There are many patient summarization options.

Default Costs

If you select Default Costs, the activity costing results from the Cost Date Ranges tab updatesthe encounter charge detail fields (Fixed Indirect Costs, Fixed Direct Costs, Variable DirectCosts, Variable Indirect Costs) based on the activity code service date. The data is thensummarized to a patient cost summary table that contains the facility, patient account, cost


Summarization task

category, cost type, and values. Then, the application will update Fixed Indirect Costs, FixedDirect Costs, Variable Direct Costs, and Variable Indirect Cost in the encounter table. Ifresults exist for the facility, revenue center, and activity code in the costing result set, it will setthese fields to zero at the encounter and charge detail levels.

Charges

If you select Charges, Total Charges in the encounter table is updated from the encountercharge detail table.

Allowable Charge

If you selectAllowable Charges, Total Allowable Charges and Total Non-Allowable Chargesare updated based on the table specifications by payor plan code for the encounter chargedetail.

Assign Professional/Technical to Charge

If you select Assign Professional/Technical to Charge, the Professional / Technical Flagon the charge record is updated based on Professional / Technical Flag on the activity codefor the default professional or technical data set in the Patient Control Panel.

Note: If the activity code is not in the activity code table, the chargeswill be set to Professional.

Professional/Technical Charges

If you select Professional/Technical Charges, the professional or technical charges in thedetail charge record are summarized to the encounter record.

Build APC Table from CPT Table

If you select Build APC Table from CPT Table, the APC table is built from the CPT table forthe encounter record APC tab.

Use Actual as Estimated Payment for Zero Balance Accounts

If you select Use Actual as Estimated Payment for Zero Balance Accounts, the expectedpayments on the encounter record on the Expected Payments tab populate with first payorplan payments. The patient account must be a zero balance (0.00) and not null (blank), in orderfor this summarization process to update. Any default contract modeling calculations areoverwritten.


Summarization task

APC Codes

If you selectAPCCodes, Primary APC is updated in the encounter table. Data Studio searchesfor the default APC table from the Defaults tab in the Patient Control Panel. Data Studio thenuses the encounter CPT-4 with sequence equal to 1 and the APC group assignment table incontract modeling to determine which APC group the CPT-4 code is related to.

CPT Codes

If you selectCPTCodes,Primary CPT-4 is updated in the encounter table. Data Studio searchesfor the encounter CPT-4 with sequence equal to 1 and populate Primary CPT-4.

Diagnosis Codes

If you select Diagnosis Codes, Primary ICD9 Diagnosis is updated in the encounter table.Data Studio looks up the encounter ICD-9 diagnosis with a sequence equal to 1 and populatePrimary ICD9 Diagnosis.

Procedure Codes

If you select Procedure Codes, Primary ICD9 Surgical Procedure is updated in the encountertable. Data Studio searches for the encounter ICD-9 surgical procedure code with a sequenceequal to 1 and populate Primary ICD9 Surgical Procedure.

Actual Payments

If you select Actual Payments, the following fields are updated in the encounter level table:

> Total Actual Payments> Payments Minus Refunds> First Payor Plan Payments> First Payor Plan Refunds> First Payor Plan Adjustments> Second Payor Plan Payments> Second Payor Plan Refunds> Second Payor Plan Adjustments> Third Payor Plan Payments> Third Payor Plan Refunds> Third Payor Plan Adjustments> Fourth Payor Plan Payments> Fourth Payor Plan Refunds


Summarization task

> Fourth Payor Plan Adjustments

Data Studio uses at the payor plan code, second payor plan code, third payor plan code, andfourth payor plan codes at the encounter table and based upon the payment type in the actualpayment table, populates this information.

Patient Portion

If you select Patient Portion, the Patient Portion Payments, Patient Portion Adjustments,Patient Portion Refunds, and Patient Portion Write Offs are updated in the encounter leveltable. Data Studio searches for the default patient payor transaction code from the Defaultstab in the Patient Control Panel and populates the applicable Patient Portion if this defaulttransaction code is on the encounter record. This function can only be used if the facility onlyhas 1 patient payor transaction code.

Detail Payments on Charges

If you selectDetail Payments on Charges, the detail expected payment, detail actual payment,and detail net payments are updated. The summarization takes the values at the encounter-leveland spreads the values to each charge record based on a percent to total of the charge recordsdetail total charge and the total charge for the encounter.

Demographic Data

If Demographic Data is selected, the first name, last name, middle initial, address 1, address2, address 3, city, state, ZIP Code, phone, marital status, date of birth, sex, race, age, andcounty are updated in the encounter-level table. Data Studio looks at the MPI table and populatesall of the information at the encounter level.

UB/HCPCS

If UB/HCPCS is selected, the default HCPCS and UB revenue codes loaded in to the activitycode table are populated by activity code into the details section of the Financial tab.

Related informationMerge patient accounts on page 42Merging patient data examples on page 45


Summarization task

Transfer activity codes and statisticsIf you are using the encounter charge detail information to populate daily, pay period, or monthlystatistic accounts for productivity or variance reporting purposes, you can set up a transfer to runautomatically when the load is run.

1. Navigate toSchedules > Edit Schedule > Edit Job and double-click the summarization task.2. In Summarization Task, click the Activity Code/Statistic Transfers tab.3. Select Enable Activity Code/Statistic Transfers.

The transfer is added to the Process Order list.

4. Click Add Transfer to create a new transfer.

Figure 4: Add a transfer

5. For Transfer Name, enter a name for the transfer.6. Select Active.


Summarization task

7. Select Enable Audit Log to create an audit log.You can only use the audit log when monthly statistics are affected.

8. For Month Range, select the month range to transfer each month.You can enter the entire year with 1 as the first entry and 12 as the to entry. Current Monthand Current Month - # reference the current month in the Reporting Manager control panel.

9. For Pay Period Range, select the pay period range to transfer in each load.You can enter the entire year by entering 1 as the first entry and 27 as the to entry.

10. (Optional) Select Use Full Pay Period 1 Value when transferring Product Line Analysis topay period values to transfer the whole pay period 1 and ignore the accrual table for payperiod 1.

11. (Optional) If you are transferring daily statistics, it is best practice to select a range of datesfor Relative Date Range.

12. Under Available Profiles, select the profiles to run and click to move them to SelectedProfiles.The profiles are processed in the order they are listed and can be sorted using the arrows.Profiles must first be created using chart maintenance in Enterprise Analyst.

13. Click OK.14. In the Activity Code Statistic Transfer tab, select Active for the transfer to run automatically.

Merge patient accountsUse the Merge Patient Accounts tab in Summarization Task to merge inpatient and outpatientencounter and charge detail data into 1 resulting encounter record.

Merging patient accounts merges all matching facility and patient accounts between the 2 tablesinto 1 record for the entire database, not just for a specific time frame or data load. This functionalityis available for Product Line Analysis loads in Data Studio and in the Enterprise Analyst PatientControl Panel.

Figure 5: Merge Patient Accounts


Summarization task

Qualify Patients Based On

For Qualify Patients Based On, select the field the merge routine uses to determine whichtable contains the resulting facility and patient account. The 4 options are: Batch Number,Billed Date, Last Record Update Date, and Record Create Date. The merge utility comparesthe facility and patient accounts in both tables and deletes the older patient account based uponthis field.

Move Charges from Old to New

Select Move Charges from Old to New to move the charge detail record from the old recordand add it to the new patient type charge detail table. If you do not select Move Charges fromOld to New, the charge detail from the old patient type table is deleted. This assumes that theencounter charge detail has been data loaded to the correct patient type table.

Append to Existing Charges if Key Fields Match

If you select Move Charges from Old to New, you can select Append to Existing Chargesif Key Fields Match to append the number of units and total charges if key fields match (facility,patient account, revenue center, activity code, service date, and posting date). If you selectMove Charges from Old to New and you do not select Append to Existing Charges if KeyFields Match and the key fields match, the number of units, unit charge amount, and totalcharge amounts are overwritten by the old record.

History

The history grid is located in the Patient Control Panel in Enterprise Analyst and displays a 1line record about the merge date and time, merge type (inpatient to outpatient or outpatient toinpatient), qualifying field (batch number, billed date, last record update date, and record createdate), number of encounters, Move Charges from Old to New, and Append to ExistingCharges if Key Fields Match.


Summarization task

Figure 6: Summary Patient Merge input listing report

Figure 7: Detail Patient Merge input listing report

Related informationMerging patient data examples on page 45


Summarization task

Merging patient data examplesThe following are patient data merge examples.


> Qualify Patients Based On: Last Record Update Date> Merge Patient Accounts: Selected> Move Charges from Old to New: Not selected> Append to Existing Charges if Key Fields Match: Not selected

Outpatient encounter table

Facility: 1Patient account: 9999Last record update: 1/1/2004 10:00 AM

Inpatient encounter table

Facility: 1Patient account: 9999Revenue center: 600Activity code: 600100Service date: 1/1/2004Posting date 1/1/2004Number of units: 1Average charges: 10.00Total charges: 10.00


Summarization task

Inpatient charge detail table

Facility: 1Patient account: 9999Revenue center: 615Activity code: 615100Service date: 1/2/2004Posting date: 1/2/2004Number of units: 1Average charges: 10.00Total charges: 10.00Facility: 1Patient account: 9999Revenue center: 620Activity code: 620100Service date: 1/2/2004Posting date: 1/2/2004Number of units: 2Average charges: 10.00Total charges: 20.00

Result

Because the inpatient encounter record has the most recent update date, it is the result encounterrecord. The outpatient encounter record is deleted. Because Move Charges from Old to Newwas not selected, the outpatient charge detail is deleted.


Summarization task


> Qualify Patients Based On: Last Record Update Date> Merge Patient Accounts: Selected> Move Charges from Old to New: Selected> Append to Existing Charges if Key Fields Match: Not selected

Outpatient Encounter Table

Facility: 1Patient account: 9999Last record update date: 1/1/2004 10:00 AM

Inpatient Encounter Table

Facility: 1Patient account: 9999Last record update date: 1/2/2004 9:00 AM

Outpatient Charge Detail Table

Facility: 1Patient account: 9999Revenue center: 600Activity code: 600100Service date: 1/1/2004Posting date: 1/1/2004Number of units: 1Average charges: 10.00


Summarization task

Total charges: 10.00

Inpatient Charge Detail Table

Facility: 1Patient account: 9999Revenue center: 615Activity code: 615100Service date: 1/1/2004Posting date: 1/1/2004Number of units: 1Average charges: 10.00Total Charges: 10.00Facility: 1Patient account: 9999Revenue center: 620Activity code: 620100Service date: 1/2/2004Posting date: 1/2/2004Number of Units: 2Average charges: 10.00Total Charges: 20.00

Result

Because the inpatient encounter record has the most recent update date, it is the result encounterrecord. The outpatient encounter record it is deleted. Because Move Charges from Old toNew was selected, the outpatient charge detail record is moved to the inpatient charge detail.

Product line assignmentAfter defining product lines in Product Line Analysis using the Product Line Designer, you canassign them to the encounter records as they are loaded into the EPSi application.

On the Product Line Assignment tab in Summarization Task, select Assign Product Lines.Select the product lines to assign. Only encounters being loaded in the EPSi™ application are


Summarization task

updated. If historical data needs to be updated, you must updateAssign Product Lines in ProductLine Analysis.

Calculating contract modelsAfter you define contracts using Contract Modeling in Product Line Analysis, the contract modelsselected in Data Studio are calculated as the encounter records are loading into the EPSi™

application.

SelectCalculate Contract Models and the contract models to calculate on theContract Modelingtab in Summarization Task. Only the encounter records being loaded into the application arecalculated in the Data Studio. To calculate historical data, you must run contract model calculationsin Product Line Analysis.

Figure 10: Contract Modeling tab

> SelectUpdate Detail Estimated Payment in Charge Record for the Default Model to spreadthe expected payment among all of the charge codes on the patient record on a percent to totalbasis.

> Select Store EOB Information to store the contracting calculation for the explanation of benefits(EOB) report in Product Line Analysis reports under the Payments reports section.

> Select Continue On Error to continue calculating when an error is encountered in the DataStudio and Contract Modeling calculations. When selected, the calculation continues and reports


Summarization task

the errors. If you do not select Continue On Error, the calculations will stop when there is anerror.

Note: If you select Continue On Error and errors occur, encountersthat qualify for term that generates an error might now qualify for adifferent term and receive the incorrect reimbursement. You mustrecalculate those patients after correcting the error.

> Select Clear the Estimated Payment for all Patient Records in the Batch to delete thepayment value for all encounters in the batch that had an expected payment before the newcontract model calculation is run. If you do not select the check box, the expected paymentvalues will not be cleared for any encounter that had an expected payment value that currentlydoes not qualify.

Note: This option should only be used when calculating all selectedinpatient/outpatient, professional/technical, facilities, payor groups,payor plan codes, and effective date ranges, or when all encounters inthat date range will have their expected payments cleared and somewill not have the value repopulated.

Variance yearsUse the Variance Years tab in Summarization Task to summarize the Product Line Analysisencounter data into a selected data set. This function is used in the Product Line Variance module.

Rule setsAfter you define rule sets in Data Manager, they can be assigned to the encounter records as theyare loaded into the EPSi™ application.

Assign rule sets in the Rule Sets tab in Summarization Task. Select Execute Rule Sets andthen select the rule sets to assign. Only encounters entering the EPSi application are updated. Toupdate historical data, rule set assignments must be updated in Data Manager.

Calculating estimated net revenueIn Data Studio, you can calculate estimated net revenue for the encounters being loaded into theEPSi™ application.

Select the date range to calculate on the Estimated Net Revenue tab in Summarization Task.Based on the patient start date and end date, the percentages of actual payments to total charges


Summarization task

are calculated by taking each facility and payor plan code, total actual payments – refunds dividedby total charges. This percentage is then applied to each encounter record.

Historical date range = 10/1/2002-9/30/2003Total charges = $10,000,000.00Total actual payments – refunds = $7,500,000.00Percent to total = 75%Total encounter charges = $10,000.00Estimated net revenue = $7,500.00

Clinical Analysis refreshAfter code assignments are defined in Clinical Analysis, they can be assigned to the encounterrecords as they are loaded for the batch being loaded into the EPSi™ application.

On the Clinical Analysis Refresh tab in Summarization Task, select Clinical Analysis Refreshto activate the task. Under Do Not Perform Code Assignment, select the codes to assign and

click to move them to Perform Code Assignment.Select Always run all code Assignments to override any selections and run all of the codeassignments. Select Delete Assignments for Patients Within Batch Before Performing CodeAssignment to delete any previous code assignments that were run for the patients who are inthe batch being loaded.Only encounters entering the EPSi application are updated. To update historical data, update thescheduling assignment in Clinical Analysis.

Activity cost assignmentYou can run cost calculations using Data Studio to calculate costs during the data load process.Use theActivity Cost Assignment tab in the summarization task to assign variable charge costing,activity-based costing (ABC), and product line costing.

1. Navigate toSchedules > Edit Schedule > Edit Job and double-click the summarization task.Summarization Task opens.

2. Click the Activity Cost Assignment tab to configure the activity cost settings.3. On the Variable Charge Costing tab, select Assign Variable Charge Cost to add the

assignment to the process order and include it in the calculations.a) For Data Sets, select the data set to assign.

Only data sets mapped in the Patient Control Panel are available.


Summarization task

The default cost scenario populates Cost Scenario.

b) If there is no default, select a cost scenario.c) For From and To, select the months containing the activity codes to calculate.d) UnderActivity Codes to Calculate, use the arrows to select the activity codes to calculate.e) Click Save.

4. Click the ABC Costing tab to assign activity based costing.a) Select Assign Activity Based Cost to add the assignment to the process order.b) For Data Sets, select the data set to assign.

Only data sets mapped in the patient control panel are available.The default cost scenario populates Cost Scenario.

c) If there is no default, select a cost scenario.d) For From and To, select the months containing the activity codes to calculate.e) Click Save.

5. Click the Product Line Costing tab to assign product line costing.a) Select Assign Product Line Cost to add the assignment to the process order.b) For Data Sets, select the data set to assign.

Only data sets mapped in the patient control panel are available.The default cost scenario populates Cost Scenario.

c) If there is no default, select a cost scenario.d) For From and To, select the months containing the activity codes to calculate.e) Under Available Cost Categories, use the arrows to select the activity codes to calculate.f) Click Save.

6. (Optional) Under General Details in Process Order, adjust the order that the costs arecalculated.

7. Click Save.

Run the Report Schedule Groups taskThe Execute Report Schedule Groups Task enables you to run scheduled reports from theschedule groups created in Reporting Manager.

1. Navigate to Schedules > Edit Schedule > Edit Job and double-click the Execute ReportSchedule Groups task.Execute Report Schedule Groups Task opens.

2. Under Unselected Schedule Groups, select the schedule groups and click to movethem to Selected Schedule Groups.


Run the Report Schedule Groups task

3. Click Save.


Run the Report Schedule Groups task

Chapter 5

Executing Data Studio Schedules andviewing logs

Configuration statusIn each step of the data load process — Standard Data Load Edit, Summarization Task, EditJobs, and Edit Schedule — the completion status is indicated under Details.

The execution status of all schedules is updated automatically.

Figure 11: Configuration status

indicates that all the necessary steps for an item have been completed.

indicates configuration is not complete. Review the setup at the lowestlevel displayed in the message, beginning with tasks. If configuration is incomplete in StandardData Load Edit, it is also incomplete in Job Edit and Schedule Edit.

Related informationRunning a schedule on page 54

Running a scheduleA schedule must be fully configured before you can run it.

In Schedule, click next to the schedule to run. You can also click in Edit Schedule.A message opens confirming that you want to run the schedule. Click Yes.


Configuration status

After running the schedule, the status is updated. Status indicators are displayed at the bottom ofSchedule.

Figure 12: Schedule status indicators

Task engine and task execution logsTask engine and execution logs enable you to review the logs of the task engine and task executionprocesses.

You can access the logs by clicking View LogMessages in the Standard Data Load Task toolbaror under Logs in the control panel.Charges that are loaded that do not have an encounter ID and cannot be matched to an existingencounter record are contained in a temporary table. The Task Execution Log displays theholding, or temporary, table information.

Figure 13: Task Engine Log Messages

You can select to view the Task Engine or Task Execution log.Click View Filters to view the filter options for Task Engine and Task Execution.The following filter options are available for the task engine log:

> Task Engine> Minimum Severity> Start Date> End Date


Running a schedule

> Search Text

The following filter options are available for the task execution log:

> Task Engine> Minimum Severity> Start Date> End Date> Search Text> Schedule> Task Type> Task

Error logsIf any record errors are generated during the running of a task, a file is created that contains onlythe records rejected by Data Studio.

To view the file with the records that were rejected in a task and the rejection reasons, go to

Standard Data Load Edit for the task. Click to view every record that was rejected and acomment that identifies why it was rejected.To view an error file, click the row for the file in the download error file and click Open. A messageopens asking you to open the file or save the file. Select the applicable option. If you select toopen the file, the file is displayed. The file displays the data for each error record and the reasonfor the error.

Note: If the error percentage is greater than 90% after processing thefirst 2000 records, the load ends, which reduces the overall processingtime for a bad source file that would keep producing errors for every record.

View the Batch Record ReportBatch Record Report enables you to filter a search for batch record reports by batch number anddate range, or by only date range and view information about the batch load.

1. In the Data Studio toolbar, select Tools > Batch Records Report.Batch Records Search opens.


View the Batch Record Report

2. For Batch Number, enter the batch number to view.3. For Start Date and End Date, select the date range containing the batch.4. (Optional) Select Only Records with Errors to only view batch loads that contain errors.5. Click Search.

The grid fills with the applicable results and the most recent batch is displayed first.

6. Click View Log for any batch to see more information.7. Click Close.

Delete a batchYou can delete a batch, or a source file that was loaded, using Delete Batch.

Note: Deleting a table from a batch deletes all data in that table for eachencounter record. For example, in the following image, all inpatient chargesfrom batch 100022344 are selected to be deleted. The application deletesthe inpatient charges that were in this batch.

1. In the Data Studio toolbar, select Tools > Delete Batch.Delete Batch opens.


View the Batch Record Report

2. For Batch Number, enter or select the batch number to delete.3. Under Select Tables to Delete, select the tables you want to delete.

If you select Inpatient Encounters orOutpatient Encounters, all of the child tables associatedwith the parent table are automatically selected.

4. Click Delete.Confirm Delete opens.

5. Click Yes.The data is deleted.

View schedule historyIn Schedule History Search you can view the results of executed schedules such as the durationand any errors or rejected records.

1. In the Data Studio toolbar, click Schedule History.Schedule History Search is displayed. The history for the last 48 hours is displayed bydefault.

2. In the Filters pane, enter search criteria to specify the schedules that are displayed.a) (Optional) For Schedule, select the name of the schedule to view.b) (Optional) For Batch Number, enter the batch number.c) (Optional) For Start Date and End Date, enter the date range.

3. Click SearchThe schedule information is displayed in the grid. You can click any of the column titles tosort the data.


View schedule history

4. Click View History in any of the rows to view the schedule results.Schedule History is displayed. Information about the individual jobs and tasks in the scheduleis available to view.

5. Click any of the items to expand more information about the job or task.

View reprocessing dataCharge and payment records are moved to the reprocessing table if there is no correspondingencounter record in the database when they are loaded. You can view or delete records from thereprocessing table in View Reprocessing Table Data.

1. In the Data Studio toolbar, select Tools > View Reprocessing Table Data.View Reprocessing Table Data opens.


View reprocessing data

2. Select the type of records to view: Charges or Payments.By default, charge records are displayed.

3. For Start Date and End Date, select the date range that contains the records.4. Click Search.

The grid fills with the applicable results. Use the scroll bar at the bottom of the window to viewall of the record information.

5. (Optional) Select 1 or more records to delete and click Delete.6. Click Close.


View reprocessing data

Appendix A

General Ledger data schedules

It is best practice when setting new schedules for general ledger to create a separate schedulefor general ledger tables and monthly general ledger and statistics loads.

This section contains examples of recommended schedule names and tables, or tasks, to becreated. If security data is going to be loaded, a schedule for user security schedule should becreated in the G/L Budgeting product in Data Studio.Other schedules for general ledger might also be set up for additional reasons, such as loadingbudget values.

General Ledger TablesThe General Ledger Tables schedules are generally set up during the implementation process.This schedule typically includes all the set up tables for the general ledger data. The activity andstatistic transfer process is not established in this schedule. The schedule type is on-demand

Table 6: General Ledger Tables schedule

DescriptionData DefinitionTasks

Load the facilitiesT_FACILITYStandard Data Load

Load cost centers and descriptions by facilityT_COST_CENTERSStandard Data Load

Load the revenue centers by facility andassignment to cost centers

T_REVENUE_CENTERSStandard Data Load

Load General Ledger Account Categories(including statistics)

T_ACCOUNT_CATEGORYStandard Data Load

Load the General Ledger Chart of Accounts byfacility including statistics

T_SUB_ACCOUNTSStandard Data Load

Load the Balance Sheet Chart of Accounts byfacility

T_CF_SUB_ACCOUNTSStandard Data Load

Monthly General Ledger and Statistic LoadsThe Monthly General Ledger and Statistic Loads schedule typically includes all the monthlygeneral ledger and statistic data such as general ledger file, statistic file, cash flow account input,journal entries, materials management, revenue and usage, and accounts payable. The activityand statistic transfer process can be established in this schedule if monthly statistics or revenue


and usage tables are generated based on Product Line Analysis charge detail data. The scheduletype is monthly.

Table 7: Monthly General Ledger and Statistic Loads schedule

DescriptionEPSI Database DataDefinition

Task

Load monthly general ledger valuesT_GL_ACCOUNT_INPUTStandard Data Load

Load monthly statistic valuesT_GL_STATISTIC_INPUTStandard Data Load

Load monthly balance sheet balancesT_CF_ACCOUNT_INPUTStandard Data Load(optional)

Load monthly accounts payable subledger detailT_SUB_LEDGER_DETAILSStandard Data Load(optional)

Load monthly journal entry subledger detailT_SUBLEDGER_JOURNAL_ENTRIES

Standard Data Load(optional)

Load monthly materials management subledgerdetail

T_SUBLEDGER_MATERIALS_MANAGEMENT

Standard Data Load(optional)

Transfer activity code volumes to statisticsActivity Code/StatisticTransfer

Summarization(optional)

User SecurityUser Security schedules are generally set up during the implementation process and typicallyinclude the tables for loading user security. These tables are available in the EPSi or G/L Budgetingproducts in Data Studio. The schedule type is on-demand.

Table 8: User Security schedule


Load user security setupT_USERSStandard Data Load

Load user access by facility and cost center bymodule

T_USER_SECURITYStandard Data Load

Runs the stored procedure EPSI_SEC_MoveUsersToRoles to set up SQL Server

EPSI_SEC_MoveUsersToRoles(Stored Procedure)

Stored Procedure

Security. This only needs to be run if new usersare added


Note: The following fields in T_USERS require values of TRUE or FALSE:Allow Report Sharing, Allow Report Scheduling, and Allow DataStudio. The values of TRUE and FALSE can be included in the sourcedata or a conversion table (convert 0 to False and 1 to True) can be setup and applied to these fields.


Appendix B

Recommended Payroll data schedules

It is best practice when setting new schedules for payroll to create a separate schedule for payrolltables and daily or bi-weekly payroll loads. This section includes examples of schedule namesand tables, or tasks, to be created. Other schedules for payroll can also be set up.

Payroll Setup TablesPayroll Setup Table schedules are generally set up during the implementation process and typicallyinclude all set up tables for payroll data. The activity and statistic transfer process is not establishedin this schedule. The schedule type is on-demand.

Table 9: Payroll Setup Tables schedule


Load job classesT_JOB_CLASSESStandard DataLoad

Load job categoriesT_JOB_CATEGORYStandard DataLoad

Load pay typesT_PAY_TYPESStandard DataLoad

Load position codesT_POSITION_CODESStandard DataLoad (optional)

Load shift codesT_SHIFTSStandard DataLoad (optional)

Load grade codesT_GRADE_LOOKUPStandard DataLoad (optional)

Load step codesT_STEP_LOOKUPStandard DataLoad (optional)

Load union codesT_UNION_CODESStandard DataLoad (optional)

Load cost center level standard,benchmark and/or targets

T_PRD_COST_CENTER_STANDARDStandard DataLoad (optional)



Load job class level standard,benchmark and/or targets

T_PRD_PRODUCTIVITY_STANDARDStandard DataLoad (optional)

Biweekly Payroll LoadThe Biweekly Payroll Load schedule typically includes all the biweekly loads: Biweekly labordistribution file, labor master (for employee names), and biweekly statistics (for biweeklyproductivity). The activity and statistic transfer process can be established in this schedule ifbiweekly statistics are generated based on Product Line Analysis charge detail data. The scheduletype is weekly.

Table 10: Biweekly Payroll Load schedule


Load biweekly labor dataT_EMPLOYEE_RESULTSStandard DataLoad

Load biweekly statistic data (forbiweekly productivity)

T_STATISTIC_PAY_PERIOD_INPUTStandard DataLoad (optional)

Transfer activity code volumes tostatistics (for biweekly productivity)

Activity Code/Statistic TransfersSummarization(optional)

Daily Productivity LoadThe Daily Productivity Load schedule typically includes all the biweekly loads: Daily labor distributionfile, labor master (for employee names), and daily statistics (for manual statistics). The activity andstatistic transfer process can be established in this schedule if daily statistics are generated basedon Product Line Analysis charge detail data. The schedule type is daily. This schedule can alsobe used in Productivity Manager.

Table 11: Daily Productivity Load schedule


Load daily labor dataT_EMPLOYEE_RESULTS_DAILY_DETAILStandard DataLoad

Load labor master for employeenames

T_EMPLOYEE_DETAILStandard Data

Transfer activity code volumes tostatistics

Activity Code/Statistic TransferSummarization


Budget Labor Master LoadThe Budget Labor Master Load schedule typically contains only the labor master for budgetingpurposes. The schedule type is on-demand.

Table 12: Budget Labor Master Load schedule


Load labor master for budgetingT_EMPLOYEE_DETAILStandard DataLoad


Appendix C

RecommendedProduct LineAnalysis dataschedules

It is best practice when setting up new schedules for Product Line Analysis to create a schedulefor encounter records and a schedule for tables. This section contains examples of schedulenames and tables, or tasks to be created.

Product Line Analysis TablesProduct Line Analysis Tables schedules are generally set up during the implementation processand typically includes all descriptive tables used for the detail encounter records. Tables can beupdated yearly, monthly, weekly, or daily. The summarization process is not included in thisschedule. The schedule type is on-demand.

Table 13: Product Line Analysis Tables schedule

DescriptionEPSi Database Data DefinitionTasks

Load the facilitiesT_FACILITYStandard DataLoad

Load the list of activity codes anddescriptions

T_ACTIVITY_CODEStandard DataLoad

Load list of admission source codes anddescriptions

T_ADMISSION_SOURCEStandard DataLoad

Load list of admission type codes anddescriptions

T_ADMISSION_TYPEStandard DataLoad

Load list of admit service codes anddescriptions

T_ADMIT_SERVICEStandard DataLoad

Load APDRG table numbers anddescriptions

T_APDRG_TABLE_NUMSStandard DataLoad

Load APDRG codes and descriptions byAPDRG table

T_APDRG_TABLEStandard DataLoad

Load APG table numbers and descriptionsT_APG_TABLE_DEFINITIONStandard DataLoad



Load APG codes and descriptions by APGtable

T_APG_CODEStandard DataLoad

Load APRDRG table numbers anddescriptions

T_APRDRG_TABLE_NUMSStandard DataLoad

Load APRDRG codes and descriptions byAPDRG table

T_APRDRG_TABLEStandard DataLoad

Load cost centers and descriptions byfacility

T_COST_CENTERSStandard DataLoad

Load CPT codes and informationT_CPT_CODESStandard DataLoad

Load CPT status indicators anddescriptions

T_CPT_STATUS_INDICATORStandard DataLoad

Load custom patient typesT_PATIENT_CUSTOM_TYPESStandard DataLoad

Load discharge disposition codes anddescriptions

T_DISCHARGE_DISPOSITIONStandard DataLoad

Load discharge flags and descriptionsT_DISCHARGE_FLAGStandard DataLoad

Load the discharge service codes anddescriptions

T_DISCHARGE_SERVICEStandard DataLoad

Load the discharge status codes anddescriptions

T_DISCHARGE_STATUSStandard DataLoad

Load DRG table and descriptionT_DRG_TABLE_NUMSStandard DataLoad

Load DRG code data by DRG tableT_DRG_TABLEStandard DataLoad

Load employers tableT_EMPLOYERSStandard DataLoad

Load financial classesT_FINANCIAL_CLASSStandard DataLoad

Load financial class groupsT_FINANCIAL_CLASS_GROUPStandard DataLoad



Load relationships of financial classes tofinancial class groups

T_FINANCIAL_CLASS_GROUP_ASSIGNMENT

Standard DataLoad

Load sex code table and descriptionsT_SEXStandard DataLoad

Load HCPCS codes and descriptionsT_HCPCS_CODESStandard DataLoad

Load HRG table numbers and descriptionsT_HRG_TABLE_NUMSStandard DataLoad

Load HRGs and descriptions by HRG tablenumber

T_HRG_TABLEStandard DataLoad

Load ICD9DX codes and descriptionsT_ICD9DX_CODESStandard DataLoad

Load ICD10DX codes and descriptionsT_ICD10DX_CODESStandard DataLoad

Load ICD9PX codes and descriptionsT_ICD9PX_CODESStandard DataLoad

Load ICD10PX codes and descriptionsT_ICD10PX_CODESStandard DataLoad

Load insured group numbers anddescriptions

T_INSUREDS_GROUPStandard DataLoad

Load marital status codes and descriptionsT_MARITAL_STATUSStandard DataLoad

Load MDC codes and descriptionsT_MDCStandard DataLoad

Load MSDRG table numbers anddescriptions

T_MSDRG_TABLE_NUMSStandard DataLoad

Load MSDRG code data by MSDRG tableT_MSDRG_TABLEStandard DataLoad

Load payor plan code informationT_PAYOR_PLAN_CODESStandard DataLoad

Load payor codes and descriptionsT_PAYOR_CODESStandard DataLoad



Load relationship of payor plan codes topayor groups

T_PAYOR_CODE_GROUPSStandard DataLoad

Load the payor groups and descriptionsT_PAYOR_GROUPSStandard DataLoad

Load physician informationT_PHYSICIANStandard DataLoad

Load physician groups and descriptionsT_PHYSICIAN_GROUPStandard DataLoad

Load assignment of physicians tophysician groups

T_PHYSICIAN_GROUP_ASSIGNMENTStandard DataLoad

Load the physician types, description andassigned summary physician type

T_PHYSICIAN_TYPEStandard DataLoad

Load the summary physician typesT_SUMMARY_PHYSICIAN_TYPEStandard DataLoad

Load physician service codes anddescriptions

T_PHYSICIAN_SERVICEStandard DataLoad

Load physician admit division codes anddescriptions

T_PHYSICIAN_ADMIT_DIVISIONStandard DataLoad

Load present on admission diagnosiscodes and descriptions (ICD9)

T_ICD9DX_POAStandard DataLoad

Load present on admission diagnosiscodes and descriptions (ICD10)

T_ICD10DX_POAStandard DataLoad

Load race codes and descriptionsT_RACEStandard DataLoad

Load readmission codes and descriptionsT_READMISSION_CODESStandard DataLoad

Load the avoidable days reason codesand descriptions

T_REASON_CODESStandard DataLoad

Load the referral sources and descriptionsT_REFERRAL_SOURCEStandard DataLoad

Load the remit code table numbersT_PAT_REMIT_CODE_TABLE_NUMSStandard DataLoad



Load remit codes and descriptions by remitcode table

T_PAT_REMIT_CODESStandard DataLoad

Load standard remit codes anddescriptions

T_PAT_REMIT_STANDARD_CODEStandard DataLoad

Load remit type codes and descriptionsT_PAT_REMIT_TYPE_CODEStandard DataLoad

Load remit source codes and descriptionsT_PAT_REMIT_SOURCE_CODEStandard DataLoad

Load remit category codes anddescriptions

T_PAT_REMIT_CATEGORY_CODEStandard DataLoad

Load remit rejection tier codes anddescriptions

T_PAT_REMIT_REJECTION_TIER_CODEStandard DataLoad

Load the resubmission codes anddescriptions

T_RESUBMISSION_CODESStandard DataLoad


T_REVENUE_CENTERSStandard DataLoad

Load service group and descriptionsT_SERVICE_GROUPS_TABLESStandard DataLoad

Load service groups and the assignedrevenue center and activity codes

T_SERVICE_GROUPSStandard DataLoad

Load severity codes and descriptionsT_SEVERITYStandard DataLoad

Load physician specialty codes anddescriptions

T_SPECIALTY_CODESStandard DataLoad

Load state DRG table and descriptionT_DRG_STATE_TABLE_NUMSStandard DataLoad

Load state DRG codes by state DRG tableT_DRG_STATE_TABLEStandard DataLoad

Load physician sub-specialty codes anddescriptions

T_SUB_SPECIALY_CODESStandard DataLoad

Load UB revenue codes and descriptionsT_UB_REVENUE_CODESStandard DataLoad



Load payment transaction codes anddescriptions

T_ACTUAL_PAYMENT_TRANSACTION_CODES

Standard DataLoad

Product Line Analysis EncountersThe Product Line Analysis Encounters schedule typically includes detail encounter tables to beloaded according to each facilities time frame (daily, weekly, or monthly). The summarizationprocess is included in this schedule. The schedule type is daily, weekly, or monthly depending onscheduled frequency of loads.

Table 14: Product Line Analysis Encounters schedule


Load the master patient index (MPI) dataT_PATIENTStandard DataLoad

Load encountersT_LOAD_ENCOUNTER_FIELDSStandard DataLoad T_IP_ENCOUNTERS

T_OP_ENCOUNTERS

Load user-defined fields for encountersT_LOAD_ENCOUNTER_EXT_FIELDSStandard DataLoad T_IP_ENCOUNTER_EXT

T_OP_ENCOUNTER_EXT

Load detail chargesT_LOAD_CHARGES_FIELDST_IP_CHARGES_001

Standard DataLoad

T_OP_CHARGES_001

Load the APG codes for the encounterT_ENCOUNTER_APGStandard DataLoad T_LOAD_ENCOUNTER_APG_FIELDS

Load CPT codes for encounterT_ENCOUNTER_CPTStandard DataLoad

Load ICD-9 diagnosis codes for encounterT_ENCOUNTER_ICD9DXStandard DataLoad

Load ICD-9 surgical procedure codes forencounter

T_ENCOUNTER_ICD9PXStandard DataLoad

Load physicians for encounterT_ENCOUNTER_PHYSICIANStandard DataLoad



Load the APC codes for the encounterT_ENCOUNTER_APCStandard DataLoad T_LOAD_ENCOUNTER_APC_FIELDS

Load actual paymentsT_ACTUAL_PAYMENTS_001Standard DataLoad

Load encounter remittance dataT_ENCOUNTER_REMITStandard DataLoad

Load the day types for the encounterT_ENCOUNTER_DAY_TYPEStandard DataLoad

Load the CA patient indicator code for theencounter

T_LOAD_CA_INDICATORStandard DataLoad

Summarizes various data to populate fieldson the encounter table for encounters thatare being loaded.

Summarize patient dataSummarization(Selectnecessary

Merge inpatient and outpatient encounterand charge detail data into 1 encounterrecord.

Merge patient accountsfunctions in theorder they willbe completed.If necessary,

Assign product lines to encounters thatare being loaded.

Product line assignmentmultipleSummarization

Apply rule sets that have been setup inEnterprise Analyst to the encounters thatare being loaded.

Rule setsTasks can besetup for thejob.)

Calculate contract models for encountersthat are being loaded.

Contract modeling

Calculate estimated net revenue for theencounters that are being loaded

Estimated net revenue

Execute activity code and statistictransfers that have been setup inEnterprise Analyst.

Activity code/Statistic transfer

Contract Modeling TablesThe Contract Modeling Tables schedule only displays tables used for descriptive purposes for thedetail encounter records. Tables can be updated yearly, monthly, weekly, or daily. Thesummarization process is not included in this schedule. The schedule type is on-demand.


Table 15: Contract Modeling Tables schedule


Load allowable charges tables anddescriptions

T_ALLOWABLE_CHARGES_TABLE_NUMS

Standard DataLoad

Load allowable charge activity codes bytable and date range

T_ALLOWABLE_CHARGESStandard DataLoad

Load relationship between APC Groupsand CPT/HCPCS codes

T_APC_GROUPSStandard DataLoad

Load APC groups and descriptions by APCtable number

T_APC_GROUP_DEFINITIONStandard DataLoad

Load APC tablesT_APC_TABLE_DEFINITIONStandard DataLoad

Load ASC tablesT_ASC_TABLE_DEFINITIONStandard DataLoad

Load the CPT assigned to each ASCgroup

T_ASC_GROUPSStandard DataLoad

Load ASC groups by ASC tableT_ASC_GROUP_DEFINITIONStandard DataLoad

Load CMG table numbers and descriptionsT_CMG_TABLE_NUMSStandard DataLoad

Load CMG codes and descriptions by tableT_CMG_TABLEStandard DataLoad

Load fee screen table numbers anddescriptions

T_FEE_SCREEN_TABLESStandard DataLoad

Load fee screen values (by HCPCS code)by fee screen table number

T_FEE_SCREENStandard DataLoad

Load fee screen activity tables anddescriptions

T_FEE_SCREEN_ACTIVITY_TABLESStandard DataLoad

Load fee values by fee screen activity tableT_FEE_SCREEN_ACTIVITYStandard DataLoad

Load HCPCS weight table numbers anddescriptions

T_PCM_HCPCS_WEIGHT_TABLE_NUMS

Standard DataLoad



Load HCPCS and HCPCS weights anddescriptions by HCPCS weight tablenumbers

T_PCM_HCPCS_WEIGHTStandard DataLoad

Load technical caps tables anddescriptions

T_PCM_TECHNICAL_CAPS_TABLEStandard DataLoad

Load HCPCS technical cap values bytechnical caps table

T_PCM_TECHNICL_CAPSStandard DataLoad

Load LOS factor tables and descriptionsT_LOS_FACTOR_TABLESStandard DataLoad

Load day of stay factor values by LOSfactor table

T_LOS_FACTORStandard DataLoad

Load comorbidity tables and descriptionsT_COMORBIDITY_TABLESStandard DataLoad

Load ICD-9 comorbidity values bycomorbidity table

T_COMORBIDITYStandard DataLoad

Load RUG tables and descriptionsT_RUG_TABLESStandard DataLoad

Load RUG codes and descriptions by RUGtable

T_RUGStandard DataLoad


Appendix D

Recommended Activity Costing dataschedules

This section contains examples of Activity Costing schedule names and tables, or tasks, to becreated.

Activity Costing TablesThe Activity Costing Tables schedules are generally set up during the implementation processand typically includes all descriptive tables used for the detail encounter records. Tables can beupdated yearly, monthly, weekly, or daily. The summarization process is not included in thisschedule. The schedule type is on-demand.

Table 16: Activity Costing Tables schedule

DescriptionEPSI Database Data DefinitionTask

Load the facilitiesT_FACILITYStandard DataLoad

Load cost centers and descriptions byfacility

T_COST_CENTERSStandard DataLoad


T_REVENUE_CENTERSStandard DataLoad

Load the general ledger chart of accountsby facility including statistics

T_SUB_ACCOUNTSStandard DataLoad

Load monthly general ledger valuesT_GL_ACCOUNT_INPUTStandard DataLoad

Load job classesT_JOB_CLASSESStandard DataLoad

Load pay typesT_PAY_TYPESStandard DataLoad

Load summary pay typesT_SUMMARY_PAY_TYPESStandard DataLoad

Load biweekly labor dataT_EMPLOYEE_RESULTSStandard DataLoad


DescriptionEPSI Database Data DefinitionTask

Load the list of activity codes anddescriptions

T_ACTIVITY_CODEStandard DataLoad

Load the cost categories and descriptionsT_COST_CATEGORY_DEFINITIONSStandard DataLoad

Load the summary cost categories anddescriptions

T_COST_SUMMARY_COST_CATEGORY

Standard DataLoad

Load monthly revenue and usage dataT_ACTIVITYStandard DataLoad

Load the RVUs and descriptionsT_COST_RVUStandard DataLoad

Load RVU assignment to cost types andcost categories

T_RVU_ASSIGNMENTStandard DataLoad

Load RVU values by revenue center andactivity code

T_RVUSStandard DataLoad

Load the overhead statistics anddescriptions

T_COST_STATISTICStandard DataLoad

Load the monthly values for the overheadstatistics by facility and cost center

T_COST_STATISTIC_VALUESStandard DataLoad

Load the materials codes along with unitcosts, purchase units, dispense units anddescriptions

T_COST_MATERIALS_MANAGEMENTStandard DataLoad

Load the materials management categorycodes and descriptions

T_COST_MATERIALS_CATEGORY_DEFINITION

Standard DataLoad

Load the assignments of material codesto material management category codes

T_COST_MATERIALS_CATEGORYStandard DataLoad

Load the capital items for costingT_COST_CAPITALStandard DataLoad


Appendix E

Setting up Data Extender loads

Data Extender loads should be set up in the Product Line Analysis product in Data Studio.

1. Set up Data Extender tables in Data Dictionary.2. Set up a data store or location for the Data Extender database.3. Set up Data Definitions for each Data Extender table.4. Complete the setup of schedules, jobs, and tasks. Select the Data Extender Data Store as the

destination.


Appendix F

Allscripts Clinical PerformanceManagement schedule load

You can use Data Studio to import data from Allscripts® Clinical Performance Management intoEPSi™.

After Allscripts® Clinical Performance Management data is loaded into EPSi, the financial andprocedural patient data stored in EPSi can be reported in conjunction with the quality measuresstored in Allscripts® Clinical Performance Management. The Allscripts® Clinical PerformanceManagement data is available to use in EPSi Reporting Manager, as well as the EPSi EnterpriseManagement Dashboard module. Some of the quality measures tracked in Allscripts® ClinicalPerformance Management include acute myocardial infarction, deep vein thrombosis, diabetes,heart failure, hospital-acquired conditions, pediatric asthma, pneumonia, pressure ulcers, andstroke.

Note: You must own the Allscripts® Clinical Performance Managementapplication to use this functionality.

1. In Edit Job, add a Standard Data Load task to the schedule and double-click the task toopen Standard Data Load Edit.

2. Under Destination for 1 - Database, select EPSI Database.You can drag and drop options from the Toolbox.

3. For 2 - Location, select the destination database location.4. For 3 - Data Definition, select the CPM Assignment Integration Data Definition table.


5. Click Save.6. Select the indicators to load in Configurations.

7. InConfigurations, select SCA Facility Xref Sub Task to set up the cross-reference betweenthe alphanumeric Allscripts® Clinical Performance Management facility ID and the EPSinumeric facility ID.

8. If you want to use the facility cross reference option, click CA Assignment Sub Task inConfigurations and select Use Facility Cross Reference.

9. In Standard Data Load Edit select 4 - File/Database Data Store and click Add Data Store.


Add Data Store opens.

10. Enter the data store source server and source database where the Allscripts® ClinicalPerformance Management data is stored.A user ID and password is required to build this connection.

11. Click Test Connection to ensure that the location is valid.12. Click OK.13. For 6 - Data Definition, select the source table that contains the Allscripts® Clinical

Performance Management data.14. Select or create mapping to map the source Allscripts® Clinical Performance Management to

the applicable target EPSi field.

> CACodeName is the indicator name.> PatientAccount is the encounter number.> FacilityID is the facility.


The Data Studio schedule will run to transfer the Allscripts® Clinical Performance Managementclinical codes into EPSi. After the codes are transferred, you can view them in Product LineAnalysis when using patient searches. Each code will have a source suffix of (CPM) or (EPSI).The codes are available to be selected as criteria throughout the Product Line Analysis andReporting Manager applications.


IndexAactivity based costing51Activity Code/Statistic Transfers41Activity Cost Assignment tab51Activity Costing data schedules76Allscripts Clinical Performance Management 79

Bbatch

deleting57

Batch Record Report56breadcrumbs 7

CClinical Analysis51configuration status54Configurations pane29Contract Modeling tab49control panel

6task engines7

conversion table27

mapping 26

Ddata definition

conversion table27destination20mapping26source21–22

data definitions6Data Extender78Data Manager50Data Studio

6accessing6

Data Studio Clean Up16Database Details25Default Costs37Delete Batch57delimeter22Detail Patient Merge report42Download Error File 56

EEdit Jobs

configuration status54


Index

Edit Schedule window12

configuration status54

Estimated Net Revenue tab50Execute Report Schedule Groups16Execute Report Schedule Groups Task52Execute SSIS Package 16

FFile Details24File/Database Data Store 21

GGeneral Ledger data schedules 61

Iicons 8

Jjobs

14icons 8

Llogs 55

Mmapping

editing26

Merge Patient Accounts tab42

examples 45

Nnet revenue50network share24network shares 6

PPatient Control Panel37Payroll data schedules64portal6post-merge subtasks29, 36pre-merge subtasks

29–30descipriptions34

pre-processing subtasks29Product Line Analysis

37Contract Modeling49data schedules67product lines48

Product Line Assignment tab48product line costing 51

RReporting Manager

29Execute Report Schedule Groups task52

Rule Sets tab 50


Index

Sschedule history8Schedule History58schedules

adding11adding jobs14adding tasks to a job17configuration status54deleting14editing12executing54executing report schedule group52icons8setting up11

solution overview5source data store21Standard Data Load

16, 18, 24–25, 27, 30, 36configuration status54destination data19–20error logs56mapping26source data21–22subtasks29

Stored Procedure16subtasks

29post-merge36pre-merge30, 34pre-processing29

Summarization37

Activity Cost Assignment tab51Clinical Analysis Refresh tab51Contract Modeling tab49Estimated Net Revenue tab50Merge Patient Accounts tab42, 45patient data37Product Line Assignment tab48Rule Sets tab50transferring activity codes and statistics41Variance Years tab50

Summarization Task16Summary Patient Merge report 42

Ttarget database19target location19target table19


Index

task engine6–7, 55

schedules11

task execution6task execution log55tasks

16adding to a job17Execute Report Schedule Groups52standard data load18

tasks (continued)summarization37

toolbar8toolbox 18

Vvariable charge costing51Variance Years tab50View Log Messages55View Reprocessing Table Data 59


Index

EPSi™ Data Studio User Guide> Space > Other July31,2017 ... ProductLine T_ENCOUNTER_CPT Analysis...

Documents

Transcript of EPSi™ Data Studio User Guide> Space > Other July31,2017 ... ProductLine T_ENCOUNTER_CPT Analysis...