Case Study: Custom DotNetNuke site for medical profession
Abstract
Client for this DNN development is a US based consulting company, mainly providing software service to
Life Science industry. Nova was chosen to develop three functional DNN modules, design the DotNetNuke Skin/Container,
and enhance the stability of the system..
Requirements
The requirement includes three DotNetNuke function modules and some design about
DotNetNuke Skin/Container.
The first module is to rewrite a module to query and view the physicians' specific
information. To ensure each physician can access to the system, the physicians'
information are required to be associated with DotNetNuke user account.
The 2nd Module is a referral module, an referral system that is similar to email
system ¨C send referrals for the patient and accept/reject the referrals between
physicians themselves, and between physicians and clinics as well. Whether the physicians
accept or reject the referral, this module needs to send email as notifications
To Whom It May Concern.
The third module is to implement registration and login supported by windows authentication.
Solution
Technology Required
- IIS6/IIS7
- DotNetNuke
- Microsoft SQL Server 2005
- Visual Studio 2008
- ASP.NET
- ASP.NET AJAX 2.0
- Web Service
- jQuery
System Architecture
As the database used in the modules was not DotNetNuke Website's own database, we
decided to establish a Web Service as a DAL layer, and use the transaction Scheduling
Mechanisms of the DotNetNuke and the Web Service provided by the client to achieve
data synchronization. Meanwhile we designed the special interface to associate account
with physicians' information.
The main function of the first module is to query the physicians, add information
for new physicians and associate the physicians' information with the DNN user.
We combined Web Service and UserInfo API of DotNetNuke Framework to achieve this
module.
In the second module, the client had a high-level and very strict requirement on
the interface, such as displaying information and pop-up with ToolTip. To obtain
the purpose we wrote a lot of JavaScript, refactored some ASP.NET Controls and established
the flow model to control it.
Some technical Difficulties existed in the third module-windows authentication module.
Although the skin module was built-in windows authentication on DotNetNuke 4.8,
it wasn't in line with the client's interface and requirements. Hereby we refactored
the module on the existing skin module and rewrote it to a standard DotNetNuke module.
Challenges of the development process
- The operate flow was complex in the second module; it needed to interact with the
first module. According to the requirement, the data used in the two modules should
be separated to the data in DotNetNuke website; meanwhile it should be synchronize
with the existing database through Web Service provided by the client.
After comprehending the requirements, we drew the flow diagrams for the indistinct
requirement and attached the detailed Textual description, and confirmed it with
the client by Email.
- After submitting the first version, we found the clients were not familiar with
the DotNetNuke deployment.
We made some videos to help the client comprehend how to install and deploy the
system about the relative modules.
Benefits to the Client
- The end client is satisfied with our program.
- The system has good stability because we considered Parallel Processing and transaction
Processing.
- The DotNetNuke we undertook cooperate well with the whole website.
Contact us
To find more details of our technical expertise and previous experience, please
fill in the form below and our sales will contact you as soon as possible. Any
enquiries from you are welcome, we will respond to you as soon as possible.
