Presenter(s): Bobbi Tate. Topic Advanced Background Business Processor Maximizing Performance and Capacity Level 300

Transcription

1

2 Presenter(s): Bobbi Tate Topic Advanced Background Business Processor Maximizing Performance and Capacity Level 300

3 Safe Harbor Provisions/Legal Disclaimer This presentation may contain forward-looking statements within the meaning of the federal securities laws, including statements concerning future prospects, events, developments, the Company s future performance, management s expectations, intentions, estimates, beliefs, projections and plans, business outlook and product availability. These forward-looking statements do not represent a commitment, promise or legal obligation to deliver any material, code or functionality. The development, release and timing of any features or functionality described for our products remains at our sole discretion. Future products developed beyond what is contemplated by existing maintenance agreements, will be priced separately. This roadmap does not constitute an offer to sell any product or technology. We believe that these forward-looking statements are reasonable and are based on reasonable assumptions and forecasts, however, undue reliance should not be placed on such statements that speak only as of the date hereof. Moreover, these forward-looking statements are subject to a number of risks and uncertainties, some of which are outlined below. As a result, actual results may vary materially from those anticipated by the forward-looking statements. Among the important factors that could cause actual results to differ materially from those indicated by such forward-looking statements are: the volume and timing of systems sales and installations; the possibility that products will not achieve or sustain market acceptance; the impact of incentive payments under The American Recovery and Reinvestment Act on sales and the ability of the Company to meet continued certification requirements; the development by competitors of new or superior technologies; the timing, cost and success or failure of new product and service introductions, development and product upgrade releases; undetected errors or bugs in software; changing economic, political or regulatory influences in the health-care industry or applicable to our business; changes in product-pricing policies; availability of third-party products and components; competitive pressures including product offerings, pricing and promotional activities; the Company's ability or inability to attract and retain qualified personnel; uncertainties concerning threatened, pending and new litigation against the Company; general economic conditions; and the risk factors detailed from time to time in the Company s periodic reports and registration statements filed with the Securities and Exchange Commission.

4 Agenda BBP Management Advanced Features Maximizing BBP Performance What s Next?

5 BBP Overview Purpose: WHEN..Best times to schedule BBP Packages HOW.Many packages per BBP server BBP Enterprise Setup: Size of the enterprise Available hardware resources Package schedule frequency

6 Requirements are unique to the Enterprise/Practice and rely on the amount of data to be processed, the number of required BBP processes, and the unit workflow. The BBP cannot process data faster than end users.

7 System Requirements System Requirements Minimum requirements to run all NextGen applications apply BBP runs it s own local instances of NextGen applications Must be treated as a regular workstation during upgrades BBP Server Requirements Must be on a separate workstation or server (either physical or virtual) with applicable NextGen instances installed See Best Practices whitepaper on Virtual Servers

8 System Requirements (Continued) Server Requirements (continued) Minimum Server Requirements: Single Processor, 2GB Memory, any supported OS in Legacy mode (x32 bit) Recommended Server Requirements: Dual Core Processor (or greater), 4GB Memory, any supported OS in Legacy Mode (x32 bit) Note: PM (and by extension BBP) run in 32-bit mode. This does NOT mean that BBP cannot be installed on a 64-bit platform rather simply that it is run in 32-bit legacy mode

9 How to Manage BBP Scheduling Single Server versus Multiple Server Error Management How to review and troubleshoot errors/failures Notification How to be notified of errors/failures BBP Report Practice Management Review duration

10 Scheduling Processing Load Categories for Package jobs: Severe: Two (2) or more hours in duration Heavy: Less than two (2) but more than one (1) hour in duration Moderate: Less than one (1) hour but more than thirty minutes (30) in duration Light: Standard package less than thirty minutes (30) in duration

11 No more than one BBP package be scheduled to run at a given time per BBP server available Job Queue overrun time considerations: o Blackout period overflow does not kill job/package execution o Setting overrun time ensures execution instead of skipping Restrictions

12 Additional Considerations Job length of time: reflective of the same amount of processing time an end user takes to complete a process Job sizes also can vary from day to day, week to week, etc. that impact processing time Database activity: Database intensive jobs need to consider each other. SQL Server database jobs also need to be factored into scheduling Report Server: Utilizing report server for running offproduction database reports can have a positive scheduling impact

13 Maximize Performance Single server scheduling: Schedule Heavy and Severe packages first Schedule packages to run back to back o If Package 1 finishes between 2:15 a.m. and 2:30 a.m. every day, Then Package 2 should be scheduled to start at 2:35 a.m. Run packages daily

14 Maximize Perfomance Multiple server scheduling: Spread out large packages Example: BBP server 1 Package: Billing practice 0001, scheduled at 6:00pm Package: Billing practice 0002, scheduled at 9:00pm BBP server 2 Package: Billing practice 0003, scheduled at 6:00pm Package: Billing practice 0004, scheduled at 9:00pm

15 Maximize Performance Break up Heavy to Severe jobs Example: BBP server 1, Package: Billing practice 0001a, 6:00pm, Settings: Providers A through M BBP server 2, Package: Billing practice 0001b, 6:00pm., Settings: Providers N through Z

16 Package Scheduling/Job Billing and Batch Posting: May need to ensure scheduling prior to midnight to apply accurate process date Batch Posting ERA Segregate and filter jobs as much as possible and run concurrently where jobs can be separated by practice or financial class as much as possible Statements: Schedule packages after batch posting

17 Report Running Group reports and utilize the Report Server Utilize Snapshot Run dissimilar reports in parallel o o Aging Reports and Scheduling Reports EHR Patient Reports and Collection Reports

18 Error Management Where to locate errors within a Package/Job History Details What does the error mean Security Printing Server Availability How to test

19 Planning for Growth Estimates: A good way to determine how many BBP servers may be needed in the future is through estimating the growth of Items Processed. Example: Using the Bill Encounters Job, the Items Processed will be encounters. If a practice is billing 5000 encounters a day with 50 providers, and is about to hire an additional 25 providers, it is safe to estimate that this practice is going to be billing around 7500 encounters in the future. Determine the current Package s capacity: How many more Items Processed can a Package do before it needs to split out to another server?

20 Items Processed Formula SPI - Second Per Item(s) JD - Job run duration (in seconds) IP - Items Processed SPI = JD / IP

21 Items Processed Using the same Billing example as above, find the number of items the Billing Job can do. IP will be different depending on the number of Claim Edits the practice is using. SPI -? JD - 6 hours which is seconds. IP encounters SPI = / 5000 SPI = 4.3 (seconds per encounter)

22 Growth Capacity Formula Get the Job run duration for the estimated growth SPI seconds per encounter JD -? IP the encounters that the practice is estimated to need billed JD = IP * SPI JD = 4.3 * 7500 JD = (seconds) which converts to 8.9 hours. (1hr = 3600 sec)

23 What s New UD2 version : notifications at the job level Encounter billing package no failure due to claims edits

24 What s Coming?

25 Package schedule viewable in a chart

26

27 Items Processed Total Items Processed Per Second

28 Server Capacity Overview

29 New report fields within BBP Schedule Report Package Run Duration Job Run Duration Items processed Second Per Items

30 BBP Schedule Report Graphing Package capacity based on seconds per item within each job graphed as a percentage

31 BBP access from within Practice Management

32 Session Survey Please take a moment to complete a brief survey regarding this session. 1. Open your ONE UGM Mobile App (please note: you must have already logged in and accepted the Terms of Use to access this feature) 2. Click the Navigation Button at the top left of the screen 3. Select Sessions 4. Search for and select this session 5. From the sessions details screen, select Survey at the bottom right of the screen 6. Remember to hit Save at the bottom of the survey once you have answered the questions

33 Any Questions?