Search form design

[SturlaP]

Hi!



I hope it allowed for newbees to post here? If not just ask me to get lost
I am new to MS access but thanks to YouTube I have managed to make a working database with a nice form to fill in data. My problem now is to design a start-up form for others to use.
This is a medical register where data about a certain patientgroup are collected. So what I am trying to make is the following:

- A start up form where people can choose either:
1. Register new patient (pressing this button will open up a new empty registration form)
2. Search for existing patient (search options will be "Last name" and/or "First name" and/or "DOB+Social security number) If this search turns up an existing patient I would like it to open up that patiens registration form so it can be edited. If the patient is not registred I would like a new empty form to open.

I have the database, the registration form, the query and a simple search form made.

Is these functions something I can easily manage or should I just start to study more of the basics of Access and come back when I know more?

Thanks in advance!

[Missinglinq]

You mention 'Social security number,' so I assume that you're in the US...and since this involves EMRs (electronic medical records) one of the really, really important things you have to consider, is how are you going to stay in compliance with HIPAA security regulations!

One of Access' main weaknesses has always been in the area of data security, and the general consensus, from discussions on this matter that I've seen, is that all-Access databases simply cannot comply.

These discussions usually agree that you can use Access as the Front End, but that you need to use a more robust Back End, such as SQL Server, which is much more secure.

Linq ;0)>

[AccessPower]

You should have no problem navigating between forms, opening forms, etc. Is there a reason for having three forms, though? You could simply have a single form, have the search at the top or bottom, and the registration part right below/above the search. That way you're not clicking between forms.

You can really pretty things up. I have an article on my blog about user interface design if you're interested: https://accessgurublog.wordpress.com...ser-interface/

Sounds like a simple enough database to have as an introduction to database development

[AccessPower]

You mention 'Social security number,' so I assume that you're in the US...and since this involves EMRs (electronic medical records) one of the really, really important things you have to consider, is how are you going to stay in compliance with HIPAA security regulations!

One of Access' main weaknesses has always been in the area of data security, and the general consensus, from discussions on this matter that I've seen, is that all-Access databases simply cannot comply.

These discussions usually agree that you can use Access as the Front End, but that you need to use a more robust Back End, such as SQL Server, which is much more secure.

Linq ;0)>

I agree with this, but if it's going to boil down to security, a bit of research should be conducted first so that the data isn't exposed to hackers. All it takes is one SQL injection in any unsanitized input to demolish even the most robust back-ends. Hardcoded front-ends are probably your best bet in that case.

[SturlaP]

Thanks for your replies!
I am not in the US, I just used social security number in my post since I guess that its the most generally known name fro these kinds of person-specific numbers. That being said, the regulations about security of such data is pretty fierce here in Norway also. But these data will be stored in an in-hospital secure server and both the front- and back-ends will be localized here.