We are a small medical company and carry out regular examinations for employees of various companies. We’ve been using an MS Access database for a couple of years now for tracking our financial information and scheduling appointments, which has been working flawlessly. Now we would like to take a big step and create our own custom made DBMS to record all medical data of our clients. What we need in development stage 1:
- a database that can manage a growth of around 8-10 thousand new records annually (most of our clients return on a yearly basis)
- high security, since we will store medical data
- functionality to scan previous medical records and link them to individuals as easy as possible (without the need to manually load a separate program and locate scanned images)
- ability to manage 5-10 concurrent users
What we need in development stage 2:
- web interface for employers to check upcoming examinations
- (ideally) a mobile app to be more flexible in scheduling appointments
- ability to manage 100 concurrent users
- (create an invoicing module - maybe stage 3)
I’m pretty good in Access now and my VBA skills are getting better and better.
I did a lot of research and read plenty of forums, so I feel I have the following options
1. use Access as front-end, MySQL as back end, later use php for development stage 2 (I have no experience with php so far) linking to the previously developed MySQL database
2. move from Access to Visual Studio and use SQL server
I would really appreciate your thoughts on this one, which path to choose. Or I am open to any other suggestions you find suitable for our needs.
- a database that can manage a growth of around 8-10 thousand new records annually (most of our clients return on a yearly basis)
- high security, since we will store medical data
- functionality to scan previous medical records and link them to individuals as easy as possible (without the need to manually load a separate program and locate scanned images)
- ability to manage 5-10 concurrent users
What we need in development stage 2:
- web interface for employers to check upcoming examinations
- (ideally) a mobile app to be more flexible in scheduling appointments
- ability to manage 100 concurrent users
- (create an invoicing module - maybe stage 3)
I’m pretty good in Access now and my VBA skills are getting better and better.
I did a lot of research and read plenty of forums, so I feel I have the following options
1. use Access as front-end, MySQL as back end, later use php for development stage 2 (I have no experience with php so far) linking to the previously developed MySQL database
2. move from Access to Visual Studio and use SQL server
I would really appreciate your thoughts on this one, which path to choose. Or I am open to any other suggestions you find suitable for our needs.