FUNCTIONAL SPECIFICATION

DESIGN

Enterprise Information Management
Reporting & Analytics
Report/Application Name: Patient Revenue - by Medicare Line and
Accommodation Type by Medicare Reporting Company
Report/Application Number: RFN01769
Project Name: IBI Focus Replacement

This document has been prepared solely for Mayo Clinic’s internal use.
The information it contains is proprietary and remains the property of:
Mayo Clinic
200 First Street SW
Rochester, MN 55905

0 3/23/09 Kyle Werner Created spec 1.2 6/30/10 Linda Helder Revisions Document Reviewers: Name Review Attention Tami Tripp Teresa Beard Matthew Goss Information Only: Name Role Enterprise Information Management Reporting & Analytics Page 2 of 12 9/13/2010 .FUNCTIONAL SPECIFICATION DESIGN Document History: Version Date Author Comments 1.1 4/7/2009 Kyle Werner Revisions 1.

........................4...... 4 1..............................................................................................................................2........ Report Parameters-User Prompts: ............... 4 1.............................. 10 3.............................4.....................................................................................2...................................................................................................... Primary Contacts.......................................................................................................................... Brief Description ...................................... Assumptions..5.................................................................. Report/Application Content and Layout ................................................................................... 12 Enterprise Information Management Reporting & Analytics Page 3 of 12 9/13/2010 ............ 4 1............................................................................ 6 2.........................................................................................FUNCTIONAL SPECIFICATION DESIGN TABLE OF CONTENTS 1.......................... REPORT STANDARDS.......................................................... Security Requirements .............................................................................................................................................................. 7 2...................................... INTRODUCTION................. 10 4.............................................................5........... Purpose and Business Need........................................................... 11 5..................................................................................... 4 2..........1...... 9 3......... Detailed Report Functionality ........................................................................... 4 1......................1.................................... 6 2.......... REPORT/APPLICATION OVERVIEW ...............................1................3......... 4 1......................................................................... 10 3.......................... 9 2....... 11 6...................... 6 2....................................................................... Report Conditions .... FUNCTIONAL SPEC SIGN-OFF.......................................... Report/Application Summary.......................... TEST CASE SCENARIOS........... Scheduling Requirements........................................................... Notes ...................2...3............................................. REPORT EXAMPLES...................

1. INTRODUCTION: This document provides the Design Specification of the following report to be developed as part of IBI Focus Replacement initiative. Enterprise Information Management Reporting & Analytics Page 4 of 12 9/13/2010 . Brief Description: The report is used for the identification of specific revenue such as that earned for medically justified private days and surgical procedures.3. This report needs to be able to use a Point In Time Data Mart.4. Assumptions: This report will be used for year-end reporting but will be run on a monthly/YTD basis. It is grouped by the Medicare Reporting Company and listed by Accounts. 1. The report also includes the RB tran type (year end Medicare Allocations – 2006 only) based on Medicare Reporting Company. This is a report used for regulatory purposes which provides gross revenue. This report is used by the Mayo Clinic Medicare Strategy Unit to assist with yearly reports that are provided to the government.2.FUNCTIONAL SPECIFICATION DESIGN 1. This shows the RRIS balances by Medicare Reporting Company. The report detailed in this document is: • Medicare Patient Revenue by Line Number and Account by Medicare Reporting Company (formerly named MD85R/03) 1. Purpose and Business Need: The report is used for the identification of specific revenue such as that earned for medically justified private days and surgical procedures.1. It is a regulatory report. Detailed Report Functionality: This report will list the revenue by an inpatient and outpatient breakout. This document contains as much information as is possible to gather before development starts. 1. then by Medicare Line Number and then by Account.

5.FUNCTIONAL SPECIFICATION DESIGN 1. Primary Contacts: Role Name Phone Number Business Owner (signs-off) Tami Tripp 6-4850 R & A Business Partner Lead Janet Rosedahl 4-1932 Subject Matter Expert (SME) Tami Tripp 6-4850 Functional Support Analyst Janet Rosedahl 4-1932 R&A Data Management Specialist Anne Marcou Kroening Report Developer Jim Richards Eric Adjei Kyle 4-3278 4-4975 8-4728 6-1180 IT Lead(s) Others Enterprise Information Management Reporting & Analytics Page 5 of 12 9/13/2010 .

Patient Admission Status.FUNCTIONAL SPECIFICATION DESIGN 2.1. intended audience) Medicare Strategy Unit Report Frequency Scheduled Monthly (after month-end close). the report will always be run on a YTD basis Retention Report Format Landscape Report File Name Semantic Layer Marts Total Volumes Facts Total Volumes Dimensions Accommodation Type. REPORT/APPLICATION OVERVIEW: 2. GLS Enterprise Information Management Reporting & Analytics Page 6 of 12 9/13/2010 . Report/Application Summary: Report Title Patient Revenue by Line Number and by Account by Medicare Reporting Company Report Reference RFN01769 Category Name Report Type Medicare Report Audience (# of users.

ACMDN_TYP_MD T. GLS_MDT. Inpatient TOT_VOL_MMT. GRS_REV_AMT See Report Conditions Outpatient TOT_VOL_MMT.2. Report/Application Content and Layout: Format: Landscape Data Groupings / Formulas: Report needs to be run by Medicare Reporting Company Order By: Disclaimer: Confidential Title Page: Report Content: Column Heading Business Name Description GLS_MDT.ACMDN_TYP_D ESC Display the Accommodation Type Description.FUNCTIONAL SPECIFICATION DESIGN 2. ACMDN_TYP_MD T.ACMDN_TYP_C D Display the Accommodation Type.MCARE _LINE Display the Medicare Line. Medicare Line Number Medicare Line Description Accommodation Type Accommodation Type Description Total Enterprise Information Management Reporting & Analytics Total of Inpatient + Outpatient Page 7 of 12 9/13/2010 .MCARE _LINE_DESC Display the Medicare Line Description. GRS_REV_AMT See Report Conditions.

SLH or SCOTS is equal to the Medicare Site Group and where the following conditions are met to determine Inpatient and Outpatient: INPATIENT: (GLS) (PT_ADM_STAT) (PT_ADM_STAT) Medicare Rpt Co.3 Report Conditions: Where RRIS Class = 1. SMH. Mcare_Site_Grp Mcare_Adm_Grp RMH RMH OUTPT RMH MCR OUTPT SMH SMH OUTPT SMH MCR OUTPT SMG SMG OUTPT SLH SLH OUTPT SCOT SCOT OUTPT OUTPATIENT: Enterprise Information Management Reporting & Analytics Page 8 of 12 9/13/2010 . where Medicare Reporting Company: RMH. SMG. Mcare_Site_Grp Mcare_Adm_Grp RMH RMH INPT SMH SMH INPT SMG SMG INPT SLH SLH INPT SCOT SCOT INPT (GLS) (PT_ADM_STAT) (PT_ADM_STAT) Medicare Rpt Co.FUNCTIONAL SPECIFICATION DESIGN 2.

FUNCTIONAL SPECIFICATION DESIGN 2.4 Report Parameters-User Prompts: Parameter Description 2.5 Notes: Enterprise Information Management Reporting & Analytics Page 9 of 12 9/13/2010 .

2 □ Crystal Report □ MS Excel □ MS Excel (Data Only) □ MS Word (RTF) □ Adobe Acrobat □ Rich Text □ Editable Rich Text □ Plain Text □ Paginated Text □ Tab-Separated Text □ Character-separated values Archiving: □ Yes □ No Explain requirements: Enterprise Information Management Reporting & Analytics Page 10 of 12 9/13/2010 .1 View on Demand or Scheduled: □ View on Demand □ Scheduled: 3. REPORT STANDARDS: 3.1 Security Requirements: 3.FUNCTIONAL SPECIFICATION DESIGN 3.2 Scheduling Requirements: 3.2.2.

List any specific examples that should be included in the test plan. REPORT EXAMPLES: Patient Revenue by Medicare Line and by Account by Medicare Reporting Company Enterprise Information Management Reporting & Analytics Page 11 of 12 9/13/2010 . TEST CASE SCENARIOS: THIS SECTION SHOULD BE FILLED OUT WITH THE BUSINESS OWNER AND R&A BUSINESS PARTNER LEAD.FUNCTIONAL SPECIFICATION DESIGN 4. What are the first things you check for? What are known areas of focus? Are there known previous problems? What are the critical success factors? 5.

FUNCTIONAL SPEC SIGN OFF FORM: R&A Business Partner Lead Preparer __________________________________ Date ___________ Business Owner Sign-off ______________________________________________ Date ___________ R&A Data Delivery Walk Through Sign-off: _____________________________ Date ___________ R&A IT Walk Through Sign-off: ______________________________________ Date ___________ … Functional Specification is updated with any changes and checked into PVCS.FUNCTIONAL SPECIFICATION DESIGN 6. Comments: ___________________________________________________________ _____________________________________________________________________ ____________________________________________________________________________ Enterprise Information Management Reporting & Analytics Page 12 of 12 9/13/2010 .

Sign up to vote on this title
UsefulNot useful