sets

[Conrad Lindes]

Thanks to those of you who reponded to my recent post, but I may not have explained my problem clearly.


1. I want to have a table to list all my patients, with data such as:
name
address
birth date
etc. (one record for each patient)
I must be able to add records to this table independent of anything described below.

2. I want to have a table that lists various problems, such as:
diabetes
well child care
hypertension
etc. (one record for each problem)

3. I want a table or set that lists various follow-up items appropriate for each problem, such as:
recheck in 3 months
CBC
Blood pressure
etc. (several items for each proble)
I want to be able to go to this table or set, choose a problem previously listed under item 2. (but be prevented from listing any new problems), and add as many follow-up items as I want.

4. I want to have a table or set which will allow me to pick any previously registered patient (but not add new ones), and add a record for each problem that that patient has and have the system add a record for each follow-up item for each problem.
Records in this table or set might be like�

NAME PROBLEM FOLLOW-UP
John Smith1 hypertension2 BP check every 3 months3
John Smith1 hypertension2 Chem 7 every year3
Ann Jones1 hypertension2 BP check every 3 months3
Ann Jones1 hypertension2 Chem 7 every year3
Ann Jones1 diabetes 22 HgbA1c every 2 months3
Ann Jones1 diabetes 22 Ophthalmologist every year3

the superscripts indicate the tables from which items have been taken. This final table or set would then be used to create follow-up ticklers.

How do I do all that?

Conrad

[Tom Cone Jr]

RE: sets

Conrad,

If you're unfamiliar with the process of designing a relational database, using linked tables of related data, perhaps the best thing you could do would be to employ a qualified database consultant. It sounds to me like you have a pretty clear picture of what you want the system to be able to do, and that's a good first step. Some time spent with a designer would pay dividends even if you decide to build it yourself.

Having said that, if you want to attempt it on your own, I recommend you start small. Build one table and get it working exactly the way you want, then add one related table at a time, testing thoroughly as you go. Count on making mis-steps which will have to be re-done. It's part of the learning curve your database consultant has already climbed.

-- tom

[Ken L Herrold]

RE: sets

Conrad:

Tom's is precisely right. What you're asking is WHAT WE DO! For either ourselves or a client we start with a plan, much as yours, and start building the tables we need to collect and store the data. During that process we make sure to have common fields in each table for the links we'll need in the sets that will follow.

As Tom suggests, a lot of it is trial and error - something the industry prefers to call 'debugging'.

Keep experimenting - one day it will come together. And you'll be richer from the experience.

Ken

[Trimcom]

RE: sets

Hi Conrad,

What you are looking for already exists. There are not only doctors using Alpha in their offices, but at least one of the top Alpha programmers, and author of several important books on Alpha programming is a doctor: Dr. Peter Wayne.

You should go to the Alphasoftware.com site and look for the list of consultants. Any application used in a doctor's office, regardless the specialty, would need much less adjustments than to begin from scratch.

An additional benefit to looking at a finished, working product would be that you would gain some ideas you haven't thought of, although you do seem to be pretty clear in what you want.

Last point: From what I can see from your post, I can assure you that all of it can be designed in Alpha in a simple step by step manner.

All the best,

TR

[John Lemisch]

RE: sets

"Physician Heal Thyself!" Apparently, you are trying to be your own programmer without the years of knowledge and expertise required. Much like some of us on the board self-diagnosing, and self-medicating........not a good idea!

[whanigsberg]

RE: sets

Now, Now, John:

I don't think that is quite fair.

Sometimes reinventing the wheel is justified, if only because after having done so you really understand wheels and are able to deal with all the problems your wagons throw at you.

So if somebody wants to do it, more power to them. And as we all know the strength of A5 is that we can do for ourselves.

The advice has been good. Start slow, build in small pieces, and test as you go. Above all, read.

And when you get stuck post a question to the board.]

Bill

[russ Boehle]

RE: sets

I agree with a lot of what has been said. I needed a solution years ago and went with Alpha 4 eventually running a business with Alpha 4V6. Having designed the app I can do things with it that I wouldn't get from a program some other company built. that said there is a learning curve. Eventually, with the help of the amazing people here on the board I think I got pretty good at Alpha 4. Now I'm starting all over in Alpha 5 and plan to redo the whole thing in A5 with lots of added features. To me it's worth it since I enjoy it and its sort of my hobby even though I'm really a neophyte in A5. (My wife thinks I'm nuts as do many others, oh well)
If you have the tenacity and time to learn it I think you'll find Alpha 5, especially v5, worth the effort - and like I said this board is pretty unique. I don't know of too many support boards or newsgroups with the kind of participation, understanding and handholding offered here.
Sooo -- if you're up to it give it a go....You may or may not end up with what you want but you'll sure learn a lot in the process.

My 2 cents
Russ

[Trimcom]

RE: sets

Hi again everybody,

You know what is missing in all this advice? I think if we polled this board we would find out that many, if not most of the programmers are busy with some other primary vocation.

So why are we all spending so much time with Alpha? The following may be two very strong points for the PR team:

1. We realize that with Alpha even amateurs can relatively easily get what they need in data processing, in ways they could never get by purchasing a program that they cannot tweak themselves. It's frustrating to try to get a programmer who knows nothing about your business to understand the exact detail you are seeking.

2. Maybe this is the most overlooked and important strength of Alpha, and much more so with the upcoming v5. It is VERY ENJOYABLE, RELAXING AND SATISFYING to design solutions to solve your problems and overcome various challenges, and then watch your own handiwork perform beautifully. We then keep tweaking and tweaking, and get excited when an upgrade comes out that addresses our own requests. We ourselves are subconsciously overlooking this hidden pleasure as the reason for actually choosing this work as a hobby.

Curious how others feel about this.

All the best,

TR

[John Walsh]

RE: sets

Conrad,

You might want to give this a try;

Create following child tables with required fields plus a linking field

Patient_Table: (field1,field2,... etc., patient_num[the link field])


Diagnosis_table: (field1, field2, ... etc., diag_code[again the link field])

treatment_table: (field1, field2, ... etc., treat_code)

Then create the parent table

Master_table: (patient_num,diag_code,treat_code, "other as needed")

Create a set linking the children on a one to one level. Create a form showing the various fields to display. In the field rules for the master_table create lookups for the child linking fields and have the lookup values display (i.e patient_table->patients_name) but only fill the linking field (i.e. patient_table->patient_num; filling master_table->patient_num).

You might have to play around with it but I think this will give you what you want. Good Luck

[Peter.Greulich]

RE: sets

"without the years of knowledge and expertise required"

So John, how do you get all those years of experience w/o starting at square one?

Peter

P.S. to Conrad - don't do what I did (i.e. learn the hardway). Take the sound advice of the many experts on this board. It may prevent you from having to rebuild your app the "right way" years later, as I have been forced to!

[Conrad Lindes]

RE: sets

Thanks, John Walsh for some specific advise. Thanks TR for the encouragement. I could do what I want to do on Alpha4, but Alpha5 confusing. I'll let folks know how it goes.

[forskare]

RE: sets

Why not? If he wants to spend the ime learning, etc., I think it's a great idea. On the other hand, if he's limited by time, a consulant WILL be needed. Eitehr way, he wins, one win will simply take longer than the other.

kenn

[forskare]

RE: sets

Tovia,

WELL SAID!!

kenn

[Thomas Henkel]

RE: sets

You will need to build several sets. The beauty of sets is that once you have your information in distinct tables, you can arrange and attach them in whatever fashion you NEED.

You need a form built on the patient table for patient entry/edit.

you need a form built on the patient->diagnosis set fo diagnosis entry/edit.

you will need another form built on the patient->diagnosis->follow-up set

What I am getting at here is that you need to create sets for distinct purposes. Don't try to do EVERYTHING in one set or table. Modularity is the key to flexibility.

Good Luck,

Tom

[russ Boehle]

RE: sets

Amen

Russ