technology hms
  • MNJ-IS is developed on a robust and well planned architecture
  • The prime design goal was to develop a solution where technical upgrades and functional upgrades can be done independently of each other
  • The complete Object Oriented Design of application has resulted in a huge class library where design wise all the functions are insulated from each other.

Windows Based Solution

  • It works on a LAN based environment but can be connected to any module on intranet and exchange information in a secure and controlled manner
  • In this way we are able to exploit the potential of intranet without exposing our application and data to web based threats
  • We took a deliberate decision to design a Windows based application rather than a web (browser) based application because
  • Most of the healthcare providing units in India are Single Company - Single Location organisation
  • In that case it is given that user organisation will have a LAN based network architecture where server will be located in the same premises.
  • Most of the users of software will be accessing it from the same building or campus where it is installed
  • Hence a web based application will bring hardly any benefit to the user organisation
  • Moreover we have achieved benefits of web based applications like all upgrades are done at server and there is no need to visit client terminals
  • The robustness of this approach can be judged by looking at MNJ-IS implementation.
server client


  • Thin client (Dumb Terminals) based computing is not a very popular concept in most of the user organisations
  • In almost all user organisations we find Fat Clients i.e. terminals with storage and processing capacity.
  • The reason is simple as almost all the terminals are used for multiple applications with different resource requirements.
  • The distributed computing architecture of MNJ Information System exploits this aspect of to full extent.
  • The Software has 4-tier Client-Server architecture where presentation and user interface layer gets executed on client terminals.
  • By doing this we fully exploit the processing capability of client terminals, reduce the workload on servers and hence the need for costly high end servers
  • However if any user organisation wants implementation on thin clints then we have a THIN CLIENT version of MNJ-IS also available
  • The architecture is flexible enough to allow unified or distributed database (database located on different machines) based computing both


  • User organisation can choose to create network and host database in any flavour of DB2, Oracle, SQL Server.
  • MNJ Servers can be hosted even on basic desktop OS like Windows XP Pro
  • Client Terminals will require OS that support Microsoft’s .NET framework