START

1. START 00:00 Thursday, 20th March, 2003 By: Mamello Thinyane BSc Hons – Rhodes University Supervisor: Greg Foster Project Proposal for: PAW

2. PAW Overview • Problem Statement • Introducing PAW • Aims of the project • Literature review • Implementation

3. PAW Problem Statement “The role of information technology is to empower people with applications, communication, and information. Mobile information technology extends these services to make them more broadly and easily accessible” (microsoft.com)

4. PAW Problem Statement “Demand for information technology remains high within the medical technology community. The Internet is rapidly emerging as the de facto medical information-sharing standard among healthcare providers, patients, and payers” (Canon Communications)

5. PAW Problem Statement • Medical industry information needs • information sharing e.g. patient monitoring and laboratory • accurate and up-to-date information • just-in-time information delivery e.g. for operations etc • accessibilty – remote, flexible etc • current usage of information technology in the medical industry is mostly based on wired networks

6. PAW Problem Statement • Solutions provided by mobile information technology • remote access • flexibility – access from a variety of devices • timely information delivery • information when and where it is needed • Distributed workforce - doctors • Increased responsiveness to patient needs

7. PAW (PatientAnyWhere) Introducing PAW PAW • PAW = PatientAnyWhere system • Description • A wireless patient records system that allows a doctor to access patient records remotely using any appropriately configured mobile device.

8. PAW (PatientAnyWhere) Aims of the project • To design and implement PAW • Device independence • Robust • Fast information access • Flexibility

9. PAW (PatientAnyWhere) Aims of the project – PAW phone interface

10. PAW (PatientAnyWhere) Aims of the project - PAW

11. PAW (PatientAnyWhere) Aims of the project • To produce a thorough write-up on • design considerations • rendering content on different devices • usability issues • ease of data entry • ease of navigation • implementation issues • developing for fast information download • intergrating available technologies • etc,

12. PAW (PatientAnyWhere) Literature review

13. PAW (PatientAnyWhere) Implementation : Challenges • Devices need different markup languages, e.g. HTML for PDAs, WML for WAP cell phones, and cHTML for i-mode phones. • Different factors to consider, e.g. varying numbers of display lines, screen orientation, and color/black and white displays. • Different network connectivity, ranging from 9.6 KB cellular connections to 11 MB Wireless LANs. • Different capabilities. Some devices can display images, some can make phone calls

14. PAW (PatientAnyWhere) Implementation Development technologies • IIS • VisualStudio.NET • VisualBasic.NET • ASP.NET • ADO.NET • MMIT • Openwave emulators

15. PAW (PatientAnyWhere) Implementation Why • MMIT reduces the challenge of developing and maintaining web application geared at specific web browsers • ASP.NET server controls automatically render the appropriate markup language i.e. HTML, WML, cHTML • ASP.NET takes into consideratioin screen sizes and device capabilities when rendering web content • Additional device support can be added using MMIT extensibility features

16. PAW (PatientAnyWhere) Implementation System Architecture

17. PAW (PatientAnyWhere) Implementation • Install required development tools • IIS, VisualStudio.NET, MMIT, device emulators etc • Determine data requirements – use case modeling • Review screen design considerations • Design and model user interface – screen flow diagrams, etc • Develop the middle tier, business logic • Develop the data objects • Test, Retest and Optimize • Deploy

18. END That’s PAW for you… Thank you very much!!! Any Questions?