On Tuesday 03 July 2007 11:17, Dave Crozier wrote:

Hi Dave!

> With the greatest respect you have been talking about this for years as you
> say - and are still no further forward. Doesn't this tell you something?

Your criticisms are helpful to me, and I appreciate them. I realize that we 
use different jargon terms in our separate professions. I think that is the 
lesson of the many years, I ask questions and then misunderstand the answers. 
Bugs everybody that I can't speak the same English they do, but that part is 
[OT].

> I offered myself to help you out about 18 months ago now but found that
> your overall understanding of the requirements relating to the "computer"
> interface and you view of the finished product was lacking to say the
> least.

I remember your offer, thanks.

> 1. You must have a good idea of how you want the finished article to look.

Look? Gee, I was just using the default interface of whatever I was using. I 
am glad you brought this up.

> If you haven't got this then how do you expect to convey the finished
> produce concepts to the developer?

Now that you force me to think about it, I want a very plain look in a small 
window - more an applet than an application. I want it to be low bandwidth 
with modest system requirements and my thought is that plain and small will 
be low bandwidth and modest system requirements.

> 2. You must define all the industry specific terms as completely as
> possible. You may well understand the meaning "Medical History" but it
> means absolutely "diddly squat" unless you give examples and more
> importantly where and how you use this information.

Medical History is the text of the questions and responses that comprises the 
first interview with the patient. Usually it doesn't mean as much as the 
patient's current examination findings, but the law requires it to be in the 
patient's record.

> 3. You need to know what you need "in to" and "out of" the system.

I have a series of questions, mostly Yes or No, a few such as No, Seldom or 
Frequent. Some pick lists, and a very few text box answers.

>  Let the  developer decide how to transform the data from one form to 
>another. You just put your magic hat on and decide what you would like to do 

When there is a positive (non No) response to the question, I want that 
question and its answer recorded. The negative answered questions would be 
left out of the report.

The law requires an "Acupuncture Impression" which I have been using as the 
title of the system's data output.

The law also requires the record to contain a "Treatment principle", which 
would be a text statement drawn from whatever the acupuncture impression was. 
The law also requires that the acupuncture points used in the treatment be 
listed, I have a heading called "Possible Points" where I put that. I also 
include a heading called "Herbal Pills".

My "System" at this point is just a word processor document. The first part is 
the medical history which usually doesn't mean a lot and is just there to 
satisfy the law. A few screens down is the "Four Pillar Examination" which is 
just Acupuncturist jargon for a four part examination.

Considering the first question of these:
Unhealthy complexion. Yes or No. (no spirit)

If the answer to this first question is "no" it is omitted from the report, if 
it is "yes" it is included, and the (no spirit) is what an unhealthy 
complexion indicates in Traditional Chinese Medicine.

Once I get this purpose defined I was going to try to develop this into a 
questionnaire in PHP Survey, or some similar open source web question thing.

http://sourceforge.net/project/screenshots.php?group_id=109356

I would need someone to do the first question. From that example I could dope 
the next so many together myself until the form of the question or answer 
changed, then I would need another example. Once I had it all together I 
would run it off a website for a while and see what happened.

This is somewhat like these on line personality tests you can take and at the 
end it spits back an interpretation.
-- 
Regards,

Pete
http://www.pete-theisen.com/


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to