Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Database Structure of Expanding System Requirements...
Message
De
29/10/2001 06:13:09
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00574116
Message ID:
00574361
Vues:
24
>>Different laboraty sections or even exams in same section greatly differ in nature. From that point it would be good for them as separate tables. However from viewing point a doctor would want to see info consolidated to one form as much as possible at times. Maybe you could combine it with 2 or more different view options. Also as a doctor (as reaaly originating from there:) I would like to see data with its progress in time (typically from last to first). As to my experiences different clinics would want to see different groups together. For example SGOT alone doesn't mean much and its meaning would be different based on companion exams plus clinic (IOW patient history, physical exam, laboratory etc complete each other). Probably you should talk and go per clinics basis on this. Good luck.
>
>Cetin,
>
>Yes! Your inputs are will taken seriously here because you're a physician by profession and we also speak the same language (IT language). With separate tables per section, the only disadvantage I can think of is a consolidated report. We've gathered info. already from 4 different hospitals (private and public) and we are thinking of the database structure I mentioned in this thread which you are confirming it to be that way. How about pictures/images? Which is better: store it in the database or just store it directly in the disk wherein the latter's file name will be stored in a table field as reference for opening it?
>
>Thanks.

As for images\pictures I think I'd keep them as separate files. Pathing for them should somewhat be enhanced to keep CD (or DVD) number, label and path. Yes CD, because hospital images are greatly static and need to be archived. A VFP or SQL server with terrabytes of space would be small for hospital imaging. Even there are images that are recordings of a say angiography session. Apart from images there are image templates per clinic that they 'mark' important locations (like an eye diagram for lesion marking). They might be embedded filling initially from a template picture (typically a black\white drawing). They're small enough to be embedded in general fields.

PS: Even if you do a perfect storage for imaging it's doubtfull patient's original hard copy images would be discarded.
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform