Presentation on theme: "George E. Jenkins, CPA, MBA"— Presentation transcript:
0HEALTHCARE INTEGRATED GENERAL LEDGER ACCOUNTING SYSTEM (HIGLAS) Association of Government Accountants – DC Chapter Conference May 9, 2007
1George E. Jenkins, CPA, MBA Deputy Director, Financial Management Systems GroupOffice of Financial ManagementCenters for Medicare and Medicaid ServicesDepartment of Health and Human Services“Modernizing the Agency and Transforming Healthcare”
2CMS Vital Statistics“CMS - Modernizing One of The Largest Healthcare Purchasers In The World!”Over 1.2 billion Medicare claims are processed each year.Medicare enrollment includes approximately 44 million beneficiaries and is growing.CMS is one of the largest purchasers of health care in the world and represents 33 cents of every dollar spent on health care in the United States.
3What is HIGLAS?Healthcare Integrated General Ledger Accounting System (HIGLAS)HIGLAS provides CMS a uniform financial management system to account for over $600 billion spent in outlays for healthcare each year.Oracle Federal Financials was selected by CMS as the base COTS application to improve the Agency’s ability to manage the benefits and administrative accounting functions.
4HIGLAS Program Vital Statistics To date, HIGLAS produced the following:$138.2 billion in Medicare Benefit Payments (As of April 24, 2007)284.6 million Claims Processed(As of April 24, 2007)$5.2 billion of AR/AP netted funds(Through March 2007)$36.3 million Interest earned in the trust funds (Through FY06)
5Benefits RealizationImplemented COTS-Based Dual-Entry Accounting System (Meets Federal Standards)Recoups Medicare Overpayments through NettingImproves Collection of DebtsSavings as of January 2007:Preserved $4.58 Billion in Medicare Trust FundsEarned additional interest ($36.3M) in the Medicare Trust Funds (through FY06)Other Savings and Benefits :Fewer Improper Payments - Decreases the need for Recovery Actions (Less “Pay and Chase”)Reduced Costs due to Decommissioned Cuff Record SystemsHIGLAS provides FFMIA Compliance & supports DHHS ComplianceImprovements in Automated Debt Collection/Referral ActivitiesCreates Audit Trails for every Transaction/Payment/Claim in HIGLASImproves Financial Audit Ability
6Functionality Analysis for Integration -as an example… Current EnvironmentHIGLAS EnvironmentShared System - FISSShared System - FISSClaims AdjudicationClaims Adjudication837 AdjudicatedClaims835 RemittanceInfoFISS Financial ModuleAccountsPayablesAccountsReceivablesHIGLASGeneratePaymentAccountsPayableNettingCuff SystemsCFOReports750/751AccountsReceivableIntegratedFinancialReportsGeneral LedgerNo Transactional AccountingDouble Entry Accrual AccountingNo General LedgerIntegrated Financial ReportingMultiple Cuff SystemsSingle Transactional SystemNo Financial IntegrityDetail Accounting Audit Trail
7General Ledger Business Processes – as an example… AccountsPayableSet of BooksAccountsReceivableGeneral LedgerJournalsManual JournalsPostingProcess Automated/Manual JournalsProcess Recurring JournalsAutomatic/Manual Journal ReversalsManually Post JournalsSchedule Journal PostingDaily Reconciliation ProcessMaintain Accounting CalendarProcess GL Month End CloseProcess GL Year End CloseGenerate Period End Reports and QueriesCalendarEvery transaction carries the ACSDaily transfer of entries from AP & AR to GLFor financial integrity you would be performing a month-end close based on the Accounting CalendarMajor Application Features providedSet of Books DefinedSegment Values DefinedAccounting Calendar Defined to Sep-06Cross Validation RulesAliases DefinedRollup Groups DefinedRecurring Journals DefinedSecurity RulesTransaction Codes DefinedGL ReportsAccount Analysis ReportChart of Accounts ReportsFSG Definition ReportsGeneral Ledger ReportsJournal ReportsTrial Balance ReportsReporting
8Multiple Users within HIGLAS Medicare Contractor AMedicare Contractor BMedicaid, Other Admin. ProgramsFISS / MCSPricer & ClaimsAdjudicationPricer & ClaimsAdjudicationAllotment, Pay & MonitorHIGLASAccountsPayableAccountsReceivableAccountsPayableAccountsReceivableAccountsPayableAccountsReceivableOtherAccountsWorkload AWorkload BCMS Integrated General LedgerFinancial ReportingCMS Financial Reporting
10HIGLAS Release 1 - Financials & HTB Integration HIGLAS Oracle eBusiness Suite - Release 11iApplicationFoundationApplicationModulesStagingTradingCommunityArchitecture(TCA)271/274Provider/Bene.837AdjudicatedClaims835RemittanceAdviceMulti-OrgApplicationSecurityAccountsReceivableAccountsPayableHealthcare Transaction Base (HTB)Audit TrailETLConcurrentProcessingDocumentSummaryGeneralLedgerOnlineScreens& ReportingCashManagementExtendedFunctionality
11HIGLAS Technical Operations AUDITSExternal AuditsCFO EDPCircular A-123, Job MappingSecurity Testing and EvaluationInternal AuditsNESSUSVulnerability AssessmentRoles and ResponsibilitiesSystem IntegratorSystem UsersPOA&M
12HIGLAS AccessJob Roles, Responsibilities, and Job Role Constraints
13Basic Design for Access Functionality and Access is assigned based on the various HIGLAS Modules or Job Role CategoriesAccounts PayableAccounts ReceivableGeneral LedgerCash Management , Bank InformationLoans ManagementAuditAR CollectionsThird Party Payments (TPP)Federal AdministrationHealthcare Transaction Base (HTB)User access to HIGLAS is defined and implemented through the Job Roles and Responsibilities matrix.The users may be granted update or inquiry/view access to any of the Oracle applications employed by HIGLAS.Most users need access to only a segment of each Oracle application to perform their assigned job duties.Furthermore, to comply with security and segregation of duty requirements, the Standard Oracle applications listed on this slide and the previous slide are broken down into more detailed lower level segments called Job Roles and Responsibilities.Access is granted by assigning the users one or more HIGLAS standard job roles.
14FunctionalityWithin the modules you either have Update or Inquiry CapabilityThe capability is determined by what Job Role is assigned to youEach job role has associated responsibilities and each responsibility provides specific functionality. It is a tiered approach.A standard Job Role is a level of authority in the Oracle application that will allow HIGLAS users to access one of the listed applications within a “data partition” (i.e. workload or Org ID).There are currently 33 Job Roles in the Job Roles and Responsibilities Matrix. Although there is not a one to one relationship between the Job Roles and Responsibility, each Job Role has at least one Responsibility.Each of those responsibilities provides access to view and/or update various types of data, and in many cases run selected standard and/or custom reports.These job roles provide the flexibility necessary for each Medicare Contractor to segregate and limit user access while protecting sensitive data.Examples follow on the next few slides.
15Functionality Outline Tiered Approach – AP Module Update AP PaymentsAdd Update Inquire AP PaymentsAdd and Update AP PaymentsInquire AP Payments, payment batches form, payments form, payment overview form and withheld amounts formView Accounting LinesAP Setup InquiryControl Payables Periods InquiryOpen Interfaces Invoices InquiryRun and View Selected AP ReportsEvery Job Role has specific functionality and access determined by the responsibilities associated with that Job Role.The first tier (Update AP Payments) represents the Job Role.The second tier (Add Update Inquire AP Payments) represents the Responsibility.The third tier represents the functionality and access associated with that Responsibility.The purpose of this design and it’s application for the Medicare Contractors is to:Define the appropriate access to HIGLAS for all users so that each individual may perform their assigned duties. (Not more access than they need)Map all HIGLAS users consistently by the Standard Job Roles and ResponsibilitiesValidate that access granted to users in each job role does not violate security or segregation of duties requirementsWork with the HIGLAS Security Team to plan and validate system configuration and load users into the designated HIGLAS instance for testing, production, or maintenance.
16We will take a look at some examples of the Job Role Functionality Outline from the AP Module. The format is the same across all Oracle modules.AP Module
17Update AP Payments Add Update Inquire AP Payments Provides access to view, update, and add claim payment data in the AP module and drill down capability to the invoice information.Provides access to run selected standard and custom AP reports.Add Update Inquire AP InvoicesProvides access to view, add, and update invoice claim information in the AP module.Provides access to run selected standard and custom AP reports.Update AP Payments is the Job Role.Add Update Inquire AP Payments is the associated responsibility.Specific Functionality for this responsibility is:add/update AP payments,inquire AP payments, payment batches form (form is an Oracle term for screen), payments form, payment overview form and withheld amounts form,view accounting lines,control payables periods inquiry,run and view selected AP reports.Add Update Inquire AP Invoices is the Job RoleAdd Update Inquire AP Invoices is the ResponsibilityFunctions associated with this responsibility are:add and update AP invoices, invoice batches form and invoices form;inquire AP invoices, invoices batches form, invoices form, invoice overview form and withheld amounts form;view accounting lines;AP setup inquiry;control payable periods inquiry;view profile settings and change personal profiles;run and view selected AP reports; andenter settlement transactions (Part A only).
18Update AP AR Customer /Supplier Add Add Update Inquire AP SuppliersProvides access to view, add and update Provider / Beneficiary / Employee / Insurers data in the AP module.Provides access to run selected standard and custom AP reports.Add Update Inquire AR CustomersProvides view, update and add capability to Provider / Beneficiary / Employee / Insurers data in the AR module. (Quick Standard and Summary Customer Forms, and Customer Profile Classes).Provides access to run selected standard and custom AR reports.Update AP AR Customer / Supplier Add is the Job RoleAdd Update Inquire AP Suppliers is the ResponsibilitySpecific functionality for that Responsibility isview accounting lines;add and update suppliers;supplier inquiry;update supplier holds;supplier holds inquiry;AP setup inquiry;control payables periods inquiry;view profile settings and change personal profiles;run and view selected AP reportsUpdate AR AR Customer / Supplier Add is the Job RoleAdd Update Inquire AR Customers is the Responsibility Note that this Job Role has two associated responsibilities. – Add Update Inquire AP Suppliers (previous screen) and Add Update Inquire AR Customers. (see the Job Role Functionality Outline)Specific functionality for this Responsibility is –add and update customers standard form, summary form, profile classes and quick entry form;AR setup inquiry;run and view selected AR reports;HIGLAS invoice status setup inquiry;multiple fund setup inquiry;PSA lookups inquiry;auto invoice interface lines inquiry;auto invoice interface exceptions inquiry.
19Job Role ConstraintsPart of our Job Role Functionality Outline is the Job Role Constraints Section.A work group reviewed the Job Roles and Responsibilities and developed a listing which indicates how to provide access without compromising segregation of duty requirements.One of our biggest challenges is to make sure that the HIGLAS users have the access they need to do their jobs without providing access that will cause them to violate segregation of duty requirements.For example, if a user is able to update AP payment information, they should not be able to update the provider or beneficiary data in the AP module, or update their address or banking information.Examples follow on the next screens.
20Job Role Constraints Access To Update AP Payments Update AP Invoices Add and update claim payment data in the AP module orUpdate AP InvoicesAdd and update invoice claim informationUpdate AR Apply Receipts /AR TransactionsAdd update receivable transaction dataApply /reverse receipts (e.g. apply cash receipt to a receivable)Should Deny Access ToUpdate AP AR Customer Add orUpdate AP Supplier Address orUpdate AP Supplier EFT orUpdate BanksUpdate AR ReceiptsAdd update cash receipts in AR module, but can’t apply/reverse the receipt to an AR.Example:With Update AP Payments Job Role you can add and update claim payment data in the AP module and have drill down capability to the invoice information.With Update AP Invoices Job Role you can add and update invoice claim information in the AP module. You can also enter settlement transactions ( Part A only).Based on the fact that you can impact payments, you should not have access to the Job Roles on the right side of the screen.They allow you to:Add or update Provider /Beneficiary / Employee/ Insurer data in the AP module;Add or Update Provider/Beneficiary/Employer/ Insurer data in the AR module;Update Provider/Beneficiary address information;Update Provider/Beneficiary EFT information; andUpdate Provider, Customer bank account information.If you have access to Update AR Apply Receipts / AR Transactions Job Role, you can (see the two bullets).You should not have access to Update AR Receipts Job Role.Having both would allow you to complete the circle of adding or updating a receivable transaction, adding or updating a cash receipt in the AR module and applying that cash receipt to a receivable or reversing that receipt.
21Job Roles, Responsibilities, and Job Role Constraints The Job Role and Responsibility Matrix was used to create the Job Role Functionality Outline.This document outlines the Job Roles, Responsibilities, and associated functionality. It also defines Job Constraints in a format that is easy to read and understand.The contractors determine access needs based on the functionality as defined by the job roles.HIGLAS access is defined based on the Job Roles and Responsibilities in each of the modules.The Oracle application administers it via the HIGLAS Menu Matrix which sets access to screens, inquiry or update capability, and access to view and run reports. This is done for each HIGLAS User within their contractor workload.
22The next several slides represent the job role constraints that were identified by the Job Mapping Workgroup. The Job Roles are identified followed by the job role constraints.Job Role Constraints
23Job Role Constraints Update AP Payments Non-Manager Job Role Constraints: Should not have Update AP AR Customer/Supplier Add or Update AP Supplier Address or Update AP Supplier EFT or Update BanksUpdate AP InvoicesUpdate AP AR Customer/Supplier AddNon-Manager Job Role Constraints: Should not have Update AP Invoices or Update AP AR Collections / Refunds or Update AP Payments or Update AP CM Recon or Update AP Supplier EFT or Update Banks or Update Interface AP Invoices or Update CMEach contractor is provided with the Job Role Functionality Outline during their Transition Kick Off meeting. This way they can review what access is provided, and be fully aware of the Job Role constraints and guidelines that have been identified.
24Job Role Constraints Update AP AR Collections / Refunds Non-Manager Job Role Constraints: Should not have Update AP AR Customer/Supplier Add or Update AP Supplier Address or Update AP Supplier EFT or Update Banks or Update AR ReceiptsUpdate AR Apply Receipts / AR TransactionsNon-Manager Job Role Constraints: Should not have Update AR ReceiptsUpdate AP CM ReconNon-Manager Job Role Constraints: Should not have Update AP AR Customer/Supplier Add or Update AP Supplier Address or Update AP Supplier EFT or Update Interface AP Invoices or Update Banks or Update GLIt is the responsibility of the Contractor’s CMS Authorized Approver (CAA) to request HIGLAS access sufficient for job performance, while avoiding situations that would create Segregation of Duty violations. This document serves as a great resource when making decisions concerning employee access.
25Job Role Constraints Update AR Receipts Non-Manager Job Role Constraints: Should not have Update AP AR Collections / Refunds or Update AR Apply Receipts / AR TransactionsUpdate GLNon-Manager Job Role Constraints: Should not have Update CM or Update AP CM ReconUpdate BanksNon-Manager Job Role Constraints: Should not have Update AP Payments or Update AP Invoices or Update AP AR Customer/Supplier Add or Update AP AR Collections / Refunds or Update AP CM Recon or Update AP Supplier Address or Update CM or Update AP Supplier EFT or Update Interface AP Invoices
26Job Role Constraints Update AP Supplier Address Non-Manager Job Role Constraints: Should not have Update AP Invoices or Update AP AR Collections / Refunds or Update AP Payments or Update AP CM Recon or Update AP Supplier EFT or Update Banks or Update Interface AP Invoices or Update CMUpdate CMNon-Manager Job Role Constraints: Should not have Update AP AR Customer/Supplier Add or Update AP Supplier Address or Update AP Supplier EFT or Update Interface AP Invoices or Update Banks or Update GL
27Job Role Constraints Update AP Supplier EFT Non-Manager Job Role Constraints: Should not have Update AP Invoices or Update AP AR Collections / Refunds or Update AP Payments or Update AP CM Recon or Update AP AR Customer/Supplier Add or Update Banks or Update Interface AP Invoices or Update AP Supplier Address or Update CMUpdate Interface AP InvoicesNon-Manager Job Role Constraints: Should not have Update AP AR Customer/Supplier Add or Update AP CM Recon or Update AP Supplier EFT or Update Banks or Update AP Supplier Address or Update CMLoans AgentNon-Manager Job Role Constraints: Should not have Loans Manager