What could be a possible option is installing PHP/GTK on the user's computer. Then, the GUI front-end could simply call a windows application to scan in the document. Perhaps you could control the scanner application via COM automation.
The PHP-GTK GUI would tag the image with a unique ID and upload it to the server. The server would then thumbnail it and put it into a "newly scanned dox" folder that could be accessed thru a web-interface, and some human at the office could then review it and put it into the appropriate patient's file. So, in total, the doctor would click a single button and an office assistant would look at an image and decide which patient's file to put it into.... pretty simple ;-) -- Scott Hurring Systems Programmer EAC Corporation scott (*) eac.com -- "Dash McElroy" <[EMAIL PROTECTED]> wrote in message ABA3F1F1A223D411BE6C006008A6F7E260446E@MSX1-PTON">news:ABA3F1F1A223D411BE6C006008A6F7E260446E@MSX1-PTON... > I would think the only way to get the info automatically into the patient's > file is if you had some kind of seriously accurate OCR software that knew > where to look on the image and then used that for it's criteria of where to > go. Knowing that OCR is periodically unreliable... you won't want to do > that. > > Realistically, _someone_ will have to tell the document where to go. You'll > also need to develop a process for auditing accuracy and other audits to > make sure that the info is in the right spot. Here's an idea: > > 1. The document needs some sort of identification, be it a cover page or a > sticky note in a strategic space > 2. User scans document and tells it where to go (however you write this...) > and PHP puts it in that patient's database entry (assuming you're using a > database. You're using a database, right?). > 3. At the end of the scanning, user audits their scanning to make sure all > is well > 4. Periodically (i.e. weekly, monthly, whatever the doc decides), someone > does an audit to make sure that all the data is where it should be. > > I've worked on a system like this, and while it was a bit of a pain > sometimes, the process is what makes the product usable. It _is_ a part of > the product. > > Good luck (and don't say Visual Basic again :-> ) > > -Dash > > -----Original Message----- > From: Todd Williamsen [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 11, 2002 6:11 AM > To: [EMAIL PROTECTED] > Subject: Re: [PHP-WIN] Re: Calling Windows DLL Files > > > Luis, > > That is fine and dandy for anybody, but this needs to be idiot proof; > meaning he has a bunch of girls maybe high school kids working there doing > this stuff and if the wrong information goes into the wrong patients files > he could get his ass in a sling legally. > > You are right, re-writing a scanning program is the wrong way of doing it, > but there is a way to do an API call which would call the TWAIN32.dll file, > Photoshop does it, and most imaging applications do as well. Now, being > able to tie in the scanning application with this application looks like the > easy part, the hard part is getting those newly scanned files in a folder > where they belong and being automatically tied into the patient's > information is the hard part. > > I am thinking PHP isn't up to this task, and Visual Basic will be better > suited, damn I hate saying that! > > > > "Luis Ferro" <[EMAIL PROTECTED]> wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Hi there, > > > > For a complex task as such, and without needing to "rewrite" the wheel > > (that means write a new scanning program) i would use: > > > > a) a scanner that works in a networked environment and as the ability to > > send the scannings to emails (i remmeber that the network scanners from > > HP can do it - even if they are a bit weird to configure...) > > b) create either a global mail drop box to send all scanned documents to > > it or create a mail box for each patient... > > c) write a much simpler pop3/imap program to handle the archiving needs > > with a web interface... > > > > For scanning, the good doctor would only need to go to the scanner, > > place the document and press a button... in the scanner > > > > For archiving, he would just go to the site and place the newly scanned > > documents in the patient file... > > > > Cheers, > > Luis Ferro > > TelaDigital > > > > P.S.- warning... the HP net scanners are weird to configure as they > > require a domain to "distribute" the scannings and have some limitations > > with regard of the ip network settings of the scanning server and the ip > > of the scanners by themselfs. They must reside in the same net mask... > > which in large distributed networks is a no-no... apart from that, they > > work very well... > > > > > > > -- > PHP Windows Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
