as far as I know, there’s a good number of Servoy developers providing healthcare solutions.
I’ve been asked to project a solution that, if approved, will involve several hospitals and external resources.
Can you help me to list the features of Servoy that you think can be the most appealing for a structure like a hospital?
I can imagine that security is one of the most important, so I thought it could be a good idea to talk about native ssl support.
Ease of deployment is another excellent topic, I think. Do you think that the need of java in every machine could be a problem?
I run a company called McCann Medical Matrix. We provide an electronic medical records solution for ophthalmologist and are currently expanding into other surgery subspecialty fields.
I choose Servoy for a number of different reasons which may be reasons you should consider.
Out of box ability to use multiple backend databases and to mix and match a solution with a number of different backbends. Many hospitals data spread between different legacy system and you will want to be able to use as much of the data as possible.
Out of the box SSL encryption and good performance over the WAN. Many medical offices and hospitals have satellite facilities.
Rapid application development. Medical records applications are complex and the rules are constantly changing. If you cannot change your application at the same speed that the rules change you cannot succeed.
Zero deployment clients [other than the need to install Java]. This reduces the number of support calls by an order of magnitude.
Easy to develop interfaces that look a lot like the web which reduces training time.
idoctor:
I run a company called McCann Medical Matrix. We provide an electronic medical records solution for ophthalmologist and are currently expanding into other surgery subspecialty fields.
I choose Servoy for a number of different reasons which may be reasons you should consider.
Out of box ability to use multiple backend databases and to mix and match a solution with a number of different backbends. Many hospitals data spread between different legacy system and you will want to be able to use as much of the data as possible.
Out of the box SSL encryption and good performance over the WAN. Many medical offices and hospitals have satellite facilities.
Rapid application development. Medical records applications are complex and the rules are constantly changing. If you cannot change your application at the same speed that the rules change you cannot succeed.
Zero deployment clients [other than the need to install Java]. This reduces the number of support calls by an order of magnitude.
Easy to develop interfaces that look a lot like the web which reduces training time.
Scalability
A lot of good points, indeed
Thanks, John: this kind of comments is exactly what I was looking for…
Riccardino:
I can imagine that security is one of the most important, so I thought it could be a good idea to talk about native ssl support.
I think the 3-tier architecture is also a strong security point. In other words, only the Servoy Application Server needs to connect to the data server. Unlike many other client/server environments where the SQL server must allow for connections from multiple clients. The need for only very limited access to the data server by only one computer is a big plus, IMO.
Riccardino:
I can imagine that security is one of the most important, so I thought it could be a good idea to talk about native ssl support.
I think the 3-tier architecture is also a strong security point. In other words, only the Servoy Application Server needs to connect to the data server. Unlike many other client/server environments where the SQL server must allow for connections from multiple clients. The need for only very limited access to the data server by only one computer is a big plus, IMO.
kazar
It certainly is. I wasn’t considering this aspect because, probably, the project will be based on Servoy + PHP.
Anyway, it could be a good point for SHC…
Riccardino:
It certainly is. I wasn’t considering this aspect because, probably, the project will be based on Servoy + PHP.
Anyway, it could be a good point for SHC…
I would think twice before building anything health care in PHP. If you do so don’t forget to search on Google for Php and security and read all articles.
Riccardino:
It certainly is. I wasn’t considering this aspect because, probably, the project will be based on Servoy + PHP.
Anyway, it could be a good point for SHC…
I would think twice before building anything health care in PHP. If you do so don’t forget to search on Google for Php and security and read all articles.
I’ll tell my PHP developers to do that
At the moment, the (potential) customer uses an asp application: is php more vulnerable than asp?
