Hi,

I want to build a scalable and modular application to manage patient data for a doctors office. With modular I mean there should be support for more than one medical specialty, thus, each specialty would have its own dll, or something like that. My problem is how to handle the database operations when I have this kind of "plugin" structure. Should all the insert/update/delete/select operations be on the core application side? Or be defined in each module? Plus, database operations would be very related to the UI, meaning the data to insert/select is given/showed on textboxes, etc, which means lots of hardcoding in each module... or is there a better way to do it?
Can anyone help me with some directions, or paradigms I should follow for this type of application? Or, if you're kind enough, some more specific examples?

Thank you very, very much

The front end forms should always be as static as possible. The main intent is to provide a window into the database but also serves to protect the information through validations.

Most of the work should be done on the database end as far as determining which records to display. Stored Procedures or Views will more than likely prove to be the most helpful.

It sounds like this development is in a very infant stage. Once the idea has progressed, repost and we can guide you deeper into the concepts.

Adamus

The front end forms should always be as static as possible. The main intent is to provide a window into the database but also serves to protect the information through validations.

Most of the work should be done on the database end as far as determining which records to display. Stored Procedures or Views will more than likely prove to be the most helpful.

It sounds like this development is in a very infant stage. Once the idea has progressed, repost and we can guide you deeper into the concepts.

Adamus