Hospital Management Software How We Designed and Developed

1. Standalone software market

2. INTRODUCINGEXSTRATICS BETA2
A tour of powerful and consistent Hospital Management System
(Ophthalmologist Specific)

3. EXSTRATICS Beta 2
The Name, Being Beta, The Objective!

4. The Name
 Exstratics Made of Two Words.
 EXSTRATICS= EXTRA + STATICS
 Software designed keeping
“Consistency” and “Stability” as
main underlying objective.
 That’s What Exstratics is,
Consistent and Stable!

5. Being Beta
 Indicates development cycle of software.
 Beta 2: The Second Base Code Complete Test Version!
Alpha Design
•Feature Set
•Code Writing
•UI Designing
Beta Builds
•Test Version
•Base Code
Complete
RCs
•Implemented
Versions
•Final Test
Version
RTM Build
•Ready To
Manufacture
•Commercial
Build

6. Objective
 Software basically deals
with Hospital
Management
 Specified for
Ophthalmology Section

7. EXSTRATICS Beta 2
The Making, The Base code,

8. The Making
 Visual Basic 6 Been The
Underneath Programming
Language.
 Backend, Database,
Supported by Microsoft
Access DB Manager.
 UI Designing and Graphics
Content Created Using
Photoshop CS.

9. The Base Code
 158 A4 Size Pages
 43,438 Lines of Codes
 98, 448 Characters
 38 Alpha UI Design
 12 Final UI with 19 MicroUI
 17 Windows API Used

10. EXSTRATICS Beta 2
The Features, The USP

11. Lineup
Queue Management
Transaction
Management
LAN Based
Dynamic Data
Exchange
iVSAT Secure
Login
Appointments
Letters And
Certificate
Templates
Theme
Extensive
Ophthalmology
Data Support
Printable
Format
Prescription
SearchWithEase
High End HDIMG
QuickNote
High End database Support
Search Multi
Data Support
Session Lock
Backup And
Restore
Windows Vista
Flip 3d Support
Encrypted
Prescription
Format
Exstratics
Specialized
Tabbing

12. The USP
High End HDIMG and Graphics

13. Exstratics Theming UI
The USP

14. Exstratics About UI
The USP

15. Exstratics Window Option
UI
The USP

16. Exstratics Unlock Session
UI
The USP

17. EXSTRATICS
Conclude
 Ultimate Tool
 Provides Standardized Management
Environment
 Unlimited Future Scope
 Its Exciting New UX
 Stable And Highly Efficient

18. NEXTGENTECHNOLOGIES
THEWORLDISCHANGING

19. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Build 90 1242818164125162440029000357404100947090548845180835840381565276435840527404150447144471353814436988537882700319000
Build 43 124281251612516220002200044000440002287835889457772200022000220002200022000220002200022000220002200022000140007785
Avg. build 90 3709137091370913709137091370913709137091370913709137091370913709137091370913709137091370913709137091370913709137091
Avg. build 43 2338223382233822338223382233822338223382233822338223382233822338223382233822338223382233822338223382233822338223382
0
10000
20000
30000
40000
50000
60000
MemoryInKilobytes Exstratics Memory Consumption

20. The Decision
 Build 43
 Was the last build with low memory consumption.
 Flicker issue was visibly present in this build.
 To overcome we finally loaded all needed forms at
startup only.
 That leads to much more memory consumption for
even running Exstratics.
 The decision sustained and even finals builds are
about 20K KBs more memory consuming.
 Advantage, flicker issue resolved.

21. Thank You For Listening
2009 NEXTGen Technologies

22. DESIGNINGEXSTRATICS BETA2
Designing Simple Solutions For Complex Probelems

23. The Design Process

24. Research
 Windows Vista Aero UI
 Office 2007 Ribbon
 The Scenic Prototypes
Debuted For Windows 7
Native Applications
 UAC UI
 Windows Live Home Page

25. The Design Process

26. Design Ethics
 The Need of Centralized Workspace Framework.
 Windows Live, Windows Vista New CPI.
 Focus On The Content And Environment as well.
 Search Must Be Smooth, Efficient And Accessible.
 Technology Counts But Interface is Essentials

27. Final UI Element
 Search UI
 The Google!
 Bing!
 Windows Live Search
 ESTs
 Office 2007 Design Prototypes
 Windows 7 Scenic
 Centralized Work UI
 Windows Live Home
 Google Wave Alpha
 Themes
 Orkut
 Original Concepts
 FocusOne
 Customized Dialogue Box
 The Float
○ User Interface Experience
○ Alpha Blend
 Quick Help
 Navigation
 The Floating About
 Welcome Screen

28. The Design Process

29. Core Development (Confidential)

30. The Home Screen Actual
Design
During Design Mode

31. Early Standalone
Prototypes
Individual Modules
Lineup Add Patient (Later Used to Edit Patient Details)

32. Office 12 Concept
One Of The Proto We Considered A Lot
The Radial Interface Navigation: Caused
Loads of Problem Due To Its Curved Edges,
We Finally Removed It!
This is Actually Event Calendar: Scheduler
and Appointment Management is an option
to consider, but its micro preview just didn’t
worked out, Another dropped feature!
Circular Navigation Button: Ours are better
then this!

33. The Flow UI
One Of The Proto We Considered A Lot
This Proto was one we can’t implement,
since Visual Basic does not allow smooth
imaging, we dropped this as well!

34. The Scraps!
One Of The Proto We Considered A Lot
Highly praised concept, we tried doing this,
but as lots of variable and information
aggregation are needed at home screen, we
finally sort of dropped it!

35. The Design Process

36. Home Screen Evolution
During Design Mode
Build 43 Build 53

37. The UI Evolution
Journey
Build 48 Build 76

38. The UI Evolution
Journey
Build 43 Build 97

39. The UI Evolution
Journey
Build 43 Build 97

40. Themes
The Float UI
Design Time
View
Run Time
View

41. Quit Exstratics?
Custom Dialogue Box
Build 50 Build 73 Build 97

42. Initially
Beta 1
Build 43

43. Finally
RC
Build 97

44. Thank You For Listening
2009 NEXTGen Technologies

45. Projects And Exstratics Future

46. EXSTRATICS FUTURE
•We might be starting project 2.0 soon.
•Currently We Considering other ideas.
•The Next Exstratics Will be network
capable.
•More efficient and smoothness will be the
key.
•The Main Interface…Might Change!

47. “Ideating”
 While post analyzing Exstratics, We come across the
need of collaborative and communicative platform across
the networks.
 The project we conceptualizing is one that is capable of
data transfer mechanism across the networks, sharing
common workspace and yet rich in standalone apps
content.
 We looking for technologies which might help.
 Windows Socket Programming Interface is been under
testing, we figured out it!
 P2P model will be explored and server will be eliminated.

49. Collaborative.
Connected.
Content.

50. •Network Communication
•Across the network data exchange capability.
•Remote technologies
•Rich content standalone features.
•Developer SDKs.
•“The Stage” Interface!