Answer the question
In order to leave comments, you need to log in
Are web technologies suitable for a busy medical system?
There is a decent medical system with several medical centers, a huge number of entries every day and I suspect about 1-2k online.
Now it seems to be using a native application (windows?) with Oracle Database (?).
Complaints: the system is outdated, complex, lags and does not really scale.
They want: to raise some kind of online application (intranet), which will gradually completely replace the current solution.
Problem areas: Making an appointment (registration) - the speed of searching for a patient and enrolling in a queue, entries in patient cards - the cost of an error is high, generating reports - speed, a large amount of data
Maybe someone had experience with a similar or similar task? Any tips? maybe this is not a format at all?
So far plan: laravel, postgres, sphinx/elastic
Google somehow sends to another steppe ...
Answer the question
In order to leave comments, you need to log in
Undoubtedly fit
. Some sites have traffic and online for 100 thousand roll over. It all depends on the hosting and application developer.
If you need a distributed network, which you already have, then in any case, web technologies have already been used there. What the interfaces are written on is a secondary matter) in any case, you need to start from the architecture with the API, data processing rules, the choice of authentication method, etc. in general, there are more architectural issues than the work itself
I would decompose the problem into separate tasks and not mix them up unnecessarily.
Obviously, you need a public web face to record with up-to-date data. But there is absolutely no need to keep confidential information on the same server. Moreover, it should be available in the clinic even when the Internet is turned off.
It makes sense to create several isolated, but communicating nodes - say, a web-face on the Internet and a web-face on an internal server that employees work with, but it does not stick out to the Internet. The internal server asks the site what the schedule is, but the connection is one-way, and hacking or dropping the Internet will not seriously break anything. The internal servers of several clinics support a common database, but already slowly, without a link to a constant uptime...
Web technologies are also different. I know at least a couple of large medical institutions in Irkutsk that use web technologies based on Java EE.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question