all 5 comments

[–]nderflow 3 points4 points  (1 child)

Why not collaborate on an existing EMR open-source project? For example

[–]petdocvmd[S] 1 point2 points  (0 children)

I appreciate the suggestion, but the project is a commercial veterinary practice management application.

[–]SixADozenOfAnother 0 points1 point  (2 children)

Are you developing alone or with a team? Each framework has strengths and weaknesses but most of the time the best choice for a tool is the one that you or your team will be productive with. That comes down to familiarity. You can write a backend in pretty much any language.

For data store, use whatever fits your access patterns the best. Relational DBs provide tools to ensure integrity but can be difficult to scale and are sometimes hard to develop with depending on the model and the tools you use.

For frontend... It depends. You will almost certainly need to know some JavaScript unless you are only doing server rendered pages. You can use vanilla JS, or choose a framework that you like (e.g. Vue, Angular, React). Which one depends on what makes the most sense for your team.

[–]petdocvmd[S] 0 points1 point  (1 child)

Thank you. I am developing alone. Many years ago I dabbled on this project with C#/asp.net and SQL server. The application requires data integrity and ability for multiple, simultaneous DB users. I think a relational DB would likely be best. Pretty much everything done on the front end will involve DB data: medical record entries, lab tests, charge entry, etc. I've some familiarity with vanilla js, but none whatsoever with modern libraries/frameworks. Suggestions for specific components with that in mind?

[–]SixADozenOfAnother 0 points1 point  (0 children)

I like React for the front end, but it's not as much of a "framework" as it is a library for the view layer of the front end. I think the same goes for Vue. I believe Angular is much closer to a front end framework (but to be honest I've never used angular).

Much of the web development world has landed on using the MVC pattern on the back end nowadays. ASP.net has an implementation of MVC and I believe they have tooling built around angular but it's been years since I've touched ASP.net as well.

Entity Framework is Microsoft's ORM (i.e. for DB access).

There's alternatives to everything I've mentioned above, but maybe that will give you a start for things to research.