Home/ Questions/Q 229231
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T19:44:54+00:00

I’m writing a medical billing application and am using MVC (Spring) for the first

  • 0

I’m writing a medical billing application and am using MVC (Spring) for the first time so I’m struggling to get an approach that feels right. Thoughts/comments would be appreciated.

My “domain” classes

  • Doctor
  • Patient
  • Claim
  • BusinessLogic

My controller classes

  • ListPatients
  • EditPatients
  • FindPatients
  • SubmitClaim

My repository classes

  • IPatientDao
  • IDoctorDao
  • IClaimDao

My application is very “rule heavy”. For example, doctors can’t delete the patients of other doctors. Patients can’t be deleted if they have been billed for something.

I think these rules should not be captured in Controllers, which feels dirty, especially if a rule needed to be utilised in several controllers. Similarly, I feel my DAO objects are for reading & writing only, not validation. As a consequence, I have made a BusinessLogic object which has the brains. So I can call something like:

businessLogic.deletePatient(patient,doctor); //returns true/false and sets a message

This does a check to see if the logged-in doctor has the right to delete a specific patient.

To me this seems the best way of keeping everything tidy.

Good or bad? What would be better?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I feel for a MVC architecture… here should be the flow of LAyers….

    a) Action class..like we have in Struts…all the parameters from webpage should be handled in this class… all validations should be handled by validators of forms…

    b) from this action class call your business class which does all the busniess logic for a given action …. say billing patients … this will get the doctors associated with it and say give some comission to doctors for that …

    c) DTO layers…getter setter for all classes in ur application … can be used by all the layers … patients, Bills, doctors, etc can be few example…

    d) DAO layer..the oe whihc interacts with the databse… it can be interacting using hibernate, JDBC etc … has all the queries written in them … do all the caching stuff etc…

    So the layers are

    Action calls the Business layer call the DAO layer ..DTO can used by all layers and can be also send as a request object back to the JSP page for displyaing data…

    • 0