1. Web Enabling Sunrise Decision Support Manager

2. Sunrise Decision Support Manager (SDSM) Development began in 1981. Developed on M204. Transition Systems Incorporated founded in 1985. Released for AS400 in 1994. Eclipsys Corporation acquired TSI in 1998. 1,100 Customer Sites 69 of 123 US academic medical centers

3. System Honor Roll RankingVendor 1. Johns Hopkins HospitalEclipsys 2. Mayo ClinicEclipsys 3. Massachusetts GeneralEclipsys 4. Duke University Medical CenterEclipsys 5. UCLA Medical CenterEclipsys 6. Cleveland ClinicEclipsys 7. Stanford University HospitalEclipsys 8. Brigham & Womens HospitalEclipsys 9. Barnes-Jewish HospitalOther 10. UCSF Medical CenterEclipsys 11. Hospital of the University of PennsylvaniaNone 12. University of Chicago Hospitals (tie)Eclipsys 13. University of Michigan Medical Ctr. (tie)Eclipsys 14. University of Washington Medical CenterOther Eclipsys DSS market share of Americas Best Hospitals Eclipsys 79% Other 14% None 7% Source: U.S. News & World Report, Americas Best Hospitals, July 27, 1998

4. Major Functions of SDSM Phase of Care Episode of Care Clinical Indicators Care Map Variances Clinical FunctionsFinancial Functions Budget Modeling Contract Management Revenue & Cash Management Product Line Management Department Analysis

5. Integration of SDSM Modules Analyze performance Analyze performance Model changes Model changes Build plans Measure and monitor Measure and monitor

6. SDSM Audience Director of Finance Director of Decision Support Utilization Manager CFO, COO, CIO Quality Assurance Manager Director of Budgeting Clinical Systems Analyst Financial Systems Analyst

7. SDSM Data Flow Payroll General Ledger Medical Records Billing M204 Or AS400 SQL Server

8. SDSM M204 Trivia

9. SDSM M204 Techniques Controlling Code Execution: ?&ACT %TOT.CST = %TOT.CST + TOTAL ACTUAL CST PRINT %TOT.CST Supporting Customizable File Names: IN ?&COPARM FOR 1 RECORD WHERE Supporting Customizable Field Names: ?&COMPANY.CODE = %COMPANY

10. A Tale of 2 Code Bases or Converting from Connect Star to Janus Web Server

11. Chapter 1: Connect Star M204 Data Object Business Object Client Object Record Set Variant Array Variant Array M204 Data Object Business Object Client Object Record Set Record Set Record Set VB Project C++ Project

12. Chapter 2: Janus Web M204 Data Object Business Object Client Object http/xmlxml M204 Data Object Business Object http/xmlRecord Set VB Project C++ Project

13. Chapter 3: Janus Web Pt II M204 Data Object Business Object Client Object http/xmlxml M204 VB Data Object Business Object http/xml Record Set VB Project C++ Project SQL Server Record Set Record Set Client Object http/xml

14. Words of Advice Data Object Business Object You gotta keep them separated. -Offspring

15. Legacy Development – Form Security http://xxx/sys/kitxa 1. User selects URL [id] [pw] 2..Net retrieves M204 ID & PW from security table in Sql Server..Net creates a page with Id & Pw fields and sends page to URL. 3. If user does not have a valid SESCOOKIE, Janus routes user to security procedure. NEWSESOPEN FILE X NEWSESCMD 'IN FILE X INCLUDE TRY.LOGIN' SESCOOKIE 'DSM204W'

16. Legacy Development – Form Security 4. If User Id or Pw missing, then redirect to error page. 7. If steps 5 or 6 go ok, then user will receive SESCOOKIE. 5. If New Pw present, then attempt change of password with $SIR_LOGIN 6. If New Pw not present, attempt normal login with $SIR_LOGIN Passed BUT…

17. Legacy Development – Form Security 8. If $SIR_LOGIN fails or Receives notice of pending password expiration, Security procedure calls error page on.Net. 9. Based on error code,.Net prompts user to correct missing or incorrect login information. 11..Net again submits page to Janus Web. 10..Net saves new info to security tables in Sql Server. Id ? [id] [pw]