1 / 63

Portal Concepts

Portal Concepts. MedIC MyMedic Shands secure web site. Earl Robbins earl@ufl.edu. Agenda. Why would we want to have a portal? MyMedIC. What is a portal? Portal implementation principles. What might be on a portal? Some examples of our portal solution.

maurice
Download Presentation

Portal Concepts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Portal Concepts MedIC MyMedic Shands secure web site Earl Robbins earl@ufl.edu

  2. Agenda • Why would we want to have a portal? • MyMedIC. • What is a portal? • Portal implementation principles. • What might be on a portal? • Some examples of our portal solution. • Benefits of MyMedIC. • Wrap-up.

  3. Why should we have a portal? • How many userids and passwords do you currently maintain? • How many web sites do you have bookmarked that are job related? • How many bookmarks do you have that are personal? • What happens if you use a computer at a different location? • What happens if you need information from the enterprise that is not provided by any vendor?

  4. Why should we have a portal? • Your users need access to all the data and applications – not just links - to do their work, teaching, research, and administration. • Your users need access to all enterprise reports, projects, administrative systems, etc. that they use – and nothing more. • Your users need the ability to access, delete, and update everything for which they are authorized – and nothing more. • Need to provide the web page a user will always use first.

  5. Why should we have a portal? • To provide user-centric information center and self-service. • The place for the user to do transactions. • The place for planning and what-ifs. • To mine global and enterprise information sources. • To integrate your Data warehouse into the information center. • To enable sharing and collaboration of critical information.

  6. Why should we have a portal? • What happens today if one’s personal information changes? (get married or get promoted, or change your address, …) • How many people is it necessary to notify? • How many systems have to be changed? • With a portal the user can tell the portal (self-service) and it can change everything necessary.

  7. MyMedIC (Medical Information Center) • We have created a web site that addresses all of these issues and is the first step in bringing a one-stop, seamless web presence to the Shands Enterprise. • This new Portal is known as MyMedIC. • MyMedIC is powered by EAGLE.

  8. EAGLE Enhanced Application Generator for the Enterprise EAGLE is the name of the application development environment used to build the portal and some applications now available on the portal and others soon to be made available.

  9. EAGLE is a product of

  10. EAGLE/Portal Platform The Portal runs under CICS on an IBM mainframe and uses SUN Web Servers at Shands. At UF, IBM SP2 nodes serve the pages. The applications that attach to the portal may be on any platform but use the portal for authorization and authentication. The portal provides XML-based communications to allow attachment of applications. The EAGLE functions use the mainframe to generate the HTML and the web server to serve the graphics and perform the encryption.

  11. EAGLE What is EAGLE? EAGLE is a mainframe-based data distribution engine and application development environment.

  12. EAGLE What does EAGLE do? EAGLE also enables you to rapidly create new Web applications to access your existing data and business logic in an integrated environment.

  13. EAGLE EAGLE method Web server TCP TCP client (WWW, e.g) OS/390

  14. EAGLE EAGLE tools EAGLE includes powerful application development tools: • ESP is a mainframe development engine similar to ColdFusion, ASP, PHP, and JSP on other platforms. • HTML generator is built-in • Diagnostic and development tools

  15. What is a Portal? One way to define a portal is to define its effect on the typical web user. Portals represent a basic change in the way information is presented to users on the web. And the way in which they use the web.

  16. Portal Effects? • A place to get more of your work done yourself. • The need for outside help is greatly reduced. • All the tools you need are in one spot. • The portal is your specialist in every area of your work. • Today, the web makes it possible – if you are good – to find things … But, a portal assists the user in using information to make decisions.

  17. Portal features? • Most of what you need is on the first page. No more searching for things that are hard to find. • Don’t add another bookmark to get the 1% of a web page you need. Add the info to a portal channel and have it all the time. • Work the way you want. Personalize. • Single sign-on.

  18. What is a Portal? A. A Portal is a home page with the word “portal” on it? B. A Gateway to web access? C. A Hub from which users can locate all the web content they commonly use? D. A user-centric web page? E. BUSCAPS

  19. Structure Databases Portal Channel 1 Channel 2 Channel 3 Channel 4 Channel 5 . . . . . .Channel n Links Applications Siemen’s Peoplesoft Dept Apps EAGLE, etc.

  20. Portal/EAGLE Implementations • MyMedic is currently providing a production roles-based portal with channels for major applications. • Production at UF since Spring 1997. • Production for state-wide FACTS system since Spring 1998. • Production at Shands since September 2001.

  21. MyMedic Capabilities • We have completed projects that provide interoperability with Siemen’s (GSM), and PeopleSoft. • We have projects underway to provide interoperability with Citrix (for client-server applications), IDX, and SoftMed. • Interacts with enterprise roles and directory databases. • Use open-standards for communications. XML and HL7 compliant with parsers for each.

  22. Guidelines for MyMedic • SPA - Single Point of Access • CARR - Condensing Authorization Roles and Rules • LAF - Look and Feel

  23. SPA - Single Point of Access • Single Signon - Crosswalk database • Application handshaking and trusted relationships • State Management with context • Interoperability - seamless intermixing of pages from various sources

  24. CARR - Condensing Authorization Roles and Rules • Combining roles into fewest possible number of databases • Trusted relationships for role passing • Rules that apply to information retrieval • Common directory across the enterprise

  25. LAF - Look and Feel • Color scheme - Similar appearance for all pages • Logos - Visual clues • Links - all appropriate functions are available • Ergonomics - usability, easy recognition • Navigation - easy to get around

  26. Principles for MyMedic Portal BUSCAPS • Business-oriented • User-centric • Secure • Customizable • Adaptable • Personalizable • Scalable

  27. Business Oriented • Access to applications that apply to my job • Access to information that applies to my job • The business applications are the center of the focus on the portal • Other web pages and information easily retrievable • Diverse set of products from multiple vendors brought together under one logical web site

  28. User-centric • Gives you just the data, applications, web pages, tools, etc. that you need. • Role-based. It knows your cohorts and roles – and you - and adjusts to match. • It changes whenever you change. • Your personal view of the world wide web, not the institution’s view.

  29. Secure • Information should be restricted by the user’s role. • Systems should be protected. • Delivery of information should be encrypted. • Good password management should be emphasized.

  30. Customizable • Customizing done by the portal software when you authenticate. • The more the portal knows about you the better job it can do. • Re-customizes every time your cohorts, roles, and functions change. • Customizes differently for different hardware - desktops, laptops, palmtops, net appliances, i-watches, etc.

  31. Adaptable • Knows your schedule and workflow. • Changes as the environment changes. • Automate portal time-oriented functions. • Saves common things you do.

  32. Personalizable • Lets you change the portal for the way you work. • Subscribe/unsubscribe to channels and alerts • Set application parameters – reports and report parameters, how to communicate with me (e-mail, fax, alerts, etc.) • Format portal page – default pages, … • Create/edit profiles • Add/remove links

  33. Scalable • Must allow for heavy peak loads • Must allow for large number of users • Reliable platform (always available)

  34. MyMedic Features Graphics Document Images Links Directory Administrative functions Help Cameos Alerts Channels Channel subscription Search Navigation – Tabs, Icons, Links, etc. Data Warehouse

  35. Search • May be at the portal level or within a channel • Search the world • Search the portal • Search the institution • Search a channel • Search a channel database(s)

  36. MyMedic Portal What does MyMedic look like?

  37. MyMedic

  38. Tutorial

  39. MyMedic Patient List

  40. Study Billing

  41. R99 Display

  42. Potential Portal LAF Portal Look and Feel

  43. Potential Portal GURTH GURTH Reports

  44. GURTH

  45. Unformatted

  46. Formatted

  47. MyMedic Link Link to MyMedic Start Page

  48. User ID Identification of User

  49. Logout Logoff to do clean-up.

  50. Jump Navigation enabler

More Related