I am building an electronic medical record for my clinic. Much of what is involved in an electronic medical record is moving stored data like past medical history, family history etc., into a note which is created for a particular visit date. Some of my scripting seems clumsy. Here are two of the techniques I have been using, but seem clumsy to me. I would like to know if they are sound techniques and if there is a better way?

1. I have created text fields which temporarily holds text while I am creating a note. When the note is finished I click a "sign note" button and the text is stored in a notes table by way of [go to portal row (last)] and then set field command. The create notes field is cleared and ready for the next note. This way, when the past notes are viewed in a portal they are viewed a calculated fields and thus cannot be altered. If I typed directly into a portal this would not be the case.

2. In my scripting, I have the script go to another layout and then loop through a portal using a set field command at each protal row to put text into a field that is then incoporated into my note. An example is moving a list of medications the patient is using from a portal into their note. This happens quickly and the switch to other layout is invisible.

Toffler

The way I've set up my EMR is to have two text fields in each record for patient notes, Results, TextToAddToResults. I type into the latter and upon signing, add to the field Results. I also have a validation in the Define Fields for Results that will not allow the user to change the content of Results unless a global field, gKey=1. This allows complete control of users entering or changing the content of their notes.

I would suggest individual files for PMH, PSH... You will find many great uses when separated. For instance, when the patient is admitted you can create a great HP template to start with.

This information would be in a table for each patient. Then another table for each Note.

This sounds like a great project. I started like you did about 10 years ago and has grown to a great database for the office.