$19.95 Buy and instantly download this paper now
The paper explores the decision to support dual architectures for the Integrated Clinical DataBase (ICDB) and explains how it capitalizes on the inherent strengths of the J2EE and Microsoft .Net development platforms and increases the options available to independent developers to extend its functionality. The paper specifically compares J2EE to Microsoft .Net, in terms of the differences in speed of development, approach to programming, attainment of security, cost and performance. The paper points out that the dual strategy of support is a challenging one, but the reliance on one over the other potentially takes away from both their key strengths.
From the Paper:"J2EE's strengths are well-suited for the ICDB's current requirements and future objectives. Java-based development and its many variations including AJAX and the associated XSLT style sheets have over time become de facto standards in rapid application development environments. The configuration of the ICDB on an open source Apache Server running the Oracle 9iAS dataset on the Dell 2650 illustrate the flexibility that J2EE was specifically designed to achieve. The reliance on a shared database server, the Dell 6600, also illustrates why UNIX from a scalability standpoint, compliments the mission of the ICDB. The Oracle 9iAS integration to Microsoft .Net and also to the Database Server also illustrates why UNIX is critical to have in this configuration as well. The shared operating system structure of the ICDB configuration will need to be continually fine-tuned to the specific processes each medical facility seeks to automate. UNIX's kernel-based architecture has over time had less of an impact on J2EE development tools (Williams, 2003), eventually leading to greater levels of business process agility and speed of execution (Hamilton, Jacob, Koch, Quammen, 2004). J2EE support for XML integration to .Net (Noumeir, 2008) accomplishes one of the major goals of the ICDB, which is the development and continual refinement of an enterprise architecture from a distributed process standpoint. Java Service for XML Binding (Devore, 2009) and the defining and release of the SOAP API for Nava further supports the build-out of the open-source approach to creating an enterprise platform as well."
Sample of Sources Used:
- Roger Barga, David Lomet, German Shegalov, & Gerhard Weikum. (2004). Recovery guarantees for Internet applications. ACM Transactions on Internet Technology, 4(3).
- Wendy L Currie, Xinkun Wang, & Vishanth Weerakkody. (2004). Developing Web services using the Microsoft.Net platform: technical and business challenges. Journal of Enterprise Information Management, 17(5), 335-350.
- Alexander Davis, & Du Zhang. (2005). A comparative study of SOAP and DCOM. The Journal of Systems and Software, 76(2), 157-169.
- Devore, S. (2009). Hardwiring process changes. Nursing Management: IT Solutions,10. (Hamilton, Jacob, Koch, Quammen, 2004)
- Connie Hamilton, Janet M Jacob, Shawna Koch, & Robecca L Quammen. (2004). Automate best practices with electronic healthcare records. Nursing Management, 35(2), 40E-F.
Cite this Analytical Essay:
Executive Healthcare Information Systems (2012, May 18) Retrieved July 19, 2019, from https://www.academon.com/analytical-essay/executive-healthcare-information-systems-151023/
"Executive Healthcare Information Systems" 18 May 2012. Web. 19 July. 2019. <https://www.academon.com/analytical-essay/executive-healthcare-information-systems-151023/>