Building a database system for my local Medical Association.
What we have is a list with something like 70+ fields of information for each member of the association. Stuff like name, surname, home address, office address, phone numbers, specialty +++ many small details.

At the moment i've built one table with all the information related to the docs + other tables for related stuff like subscription payments, requests, penalties etc.

I'm quite new to database design, and while it works, I find my design ugly. It is logical, as all information in each row is unique and belongs to just one person, but i'm sure there would be a better way to do it.

How would you go for it? Should I do multiple 1:1 tables, 1 for each subject (basic info, contact info, education, etc) or just keep it as it is? One table with 70+ columns.