Hi Reinier,
On 4 February 2012 13:02, Reinier Battenberg < [email protected]> wrote: > Hi, > > Can you give a use case for this that is useful for a clinic where a > patient > shows up at the counter desk? > This blog post provides various use cases for the bar code: http://www.meanmicio.org/2012/02/qr-codes-in-gnu-health.html Regards Ronald > > rgds, > Reinier > > On Saturday 04 February 2012 11:59:26 Benjamin Tayehanpour wrote: > > That may have been true ten or twenty years ago, and of course still > > true for technology from that time, but today most new installations > > use a camera and decode the bar code in software, the benefits being > > you can support virtually any type of code and cheaper hardware. The > > only modern installations with hardware decoders I've seen are in > > time-critical content-controlled environments such as conveyor belts, > > because the camera + software variant is a bit slower. > > > > On Sat, Feb 4, 2012 at 11:50 AM, Reinier Battenberg > > > > <[email protected]> wrote: > > > Why not just add another explanation of what barcodes (and barcode > > > readers) are. > > > > > > They are a keyboard. > > > > > > How it works: > > > > > > - You install a barcode font from the web. > > > - You print the customer number you already have, on the customer card, > > > in the barcode font (so it looks like stripes) > > > - When the client comes in with the card, you place your cursor in the > > > customer number searchfield in your application > > > - You scan the barcode, and the barcode software on your machine > inserts > > > the customer number in the customer number field > > > - You find the client. > > > > > > The 2 biggest advantages of this: > > > > > > - Its fast > > > - It makes far less errors than a human > > > > > > That is all barcodes will do for you. (and sometimes that is very very > > > useful) > > > > > > rgds, > > > reinier > > > > > > On Saturday 04 February 2012 13:46:12 [email protected] wrote: > > >> Barcodes like magnetic stripes on CC are great for retrieving data > > >> quickly like in a supermarket but provide zero ability to > > >> authenticate the person holding the card, is who they are supposed to > > >> be. To do that you need some kind of biometric system usually like a > > >> fingerprint scanner or pin code. > > >> > > >> The question is more one of effort and cost, also making sure you have > > >> good checks and balances on the services the patient uses. If someone > > >> comes in with another patients card and uses the service then the > > >> real patient comes in and can't because 'their friend' used it up > > >> they should get the message pretty quick. > > >> > > >> On 4 February 2012 13:36, Godfrey Baluku <[email protected]> wrote: > > >> > Benjamin,**** > > >> > > > >> > The problem here is updating the members who have subscribed to > > >> > the > > >> > insurance scheme. I usually get over 300 members. Updating the > > >> > system > > >> > takes me time because I have to input one member at a time. **** > > >> > > > >> > ** ** > > >> > > > >> > Thanks**** > > >> > > > >> > ** ** > > >> > > > >> > *From:* [email protected] [mailto:[email protected]] > > >> > *On > > >> > Behalf Of *Bernard Adongo > > >> > *Sent:* 04 February 2012 13:31 > > >> > > > >> > *To:* Uganda Linux User Group > > >> > *Subject:* Re: [LUG] Barcode generator and reader software/ > > >> > barcode > > >> > scanner**** > > >> > > > >> > ** ** > > >> > > > >> > So what is the barcode for, again?**** > > >> > > > >> > On 4 Feb 2012 13:22, "Godfrey Baluku" <[email protected]> > > >> > wrote:**** > > >> > > > >> > Thanks Benjamin,**** > > >> > > > >> > **** > > >> > > > >> > What I forgot to tell you is that, I’ve got an existing database > > >> > that > > >> > has > > >> > a photograph of the beneficiaries to this scheme. Through this, I > > >> > can > > >> > identify if the person is the real owner of the ID Card.**** > > >> > > > >> > **** > > >> > > > >> > Many thanks.**** > > >> > > > >> > **** > > >> > > > >> > *From:* [email protected] [mailto:[email protected]] > > >> > *On > > >> > Behalf Of *[email protected] > > >> > *Sent:* 04 February 2012 13:14 > > >> > *To:* Uganda Linux User Group > > >> > *Subject:* Re: [LUG] Barcode generator and reader software/ > > >> > barcode > > >> > scanner**** > > >> > > > >> > **** > > >> > > > >> > Hello fellow Tech Baluku. > > >> > > > >> > Two questions: > > >> > 1. How do you propose to prevent identity theft? > > >> > 2. How do you propose to prevent identity lending? > > >> > > > >> > Regards, > > >> > Benjamin T**** > > >> > > > >> > Godfrey Baluku <[email protected]> wrote:**** > > >> > > > >> > Hello Lug,**** > > >> > > > >> > **** > > >> > > > >> > I’ve got this idea of implementing a health insurance system using > > >> > barcode reader/scanner. This is the flow of the tasks. **** > > >> > > > >> > 1. Print identity cards with bar codes and issue them to > > >> > the > > >> > beneficiaries of the insurance scheme.**** > > >> > > > >> > 2. After a person has subscribed for a period, let’s say 6 > > >> > months, I update his/her details in the database by use of a > > >> > barcode scanner. This is how I will do it:-**** > > >> > > > >> > a. He/she presents his card.**** > > >> > > > >> > b. I update his/her details by use of the barcode > > >> > scanner.**** > > >> > > > >> > 3. When this perso n wants to access medical services, > > >> > he/she > > >> > comes > > >> > with his/her ID Card.**** > > >> > > > >> > 4. I use a barcode scanner to identify the validity of this > > >> > person. **** > > >> > > > >> > Where and how can I find the appropriate Device/Software.**** > > >> > > > >> > **** > > >> > > > >> > Thanks**** > > >> > > > >> > **** > > >> > > > >> > *Godfrey Baluku > > >> > IT Tech > > >> > Bwindi Community Hospital > > >> > www.bwindihospital.com > > >> > www.facebook/gbaluku > > >> > KypeID: bmgodie***** > > >> > > > >> > *Yahoo:balugodie > > >> > +256784420939/+256791844512* > > >> > > > >> > “*Total abstinence is so excellent a thing that it cannot be > > >> > carried to great an extent. in my passion for it i even carry it > > >> > so far as to totally abstain from total abstinence itself*." Mark > > >> > Twain**** > > >> > > > >> > **** > > >> > > > >> > **** > > >> > > > >> > _______________________________________________ > > >> > The Uganda Linux User Group: http://linux.or.ug > > >> > > > >> > Send messages to this mailing list by addressing e-mails to: > > >> > [email protected] > > >> > Mailing list archives: > > >> > http://www.mail-archive.com/[email protected]/ > > >> > Mailing list settings: http://kym.net/mailman/listinfo/lug > > >> > To unsubscribe: http://kym.net/mailman/options/lug > > >> > > > >> > The Uganda LUG mailing list is generously hosted by INFOCOM: > > >> > http://www.infocom.co.ug/ > > >> > > > >> > The above comments and data are owned by whoever posted them > > >> > (including attachments if any). The mailing list host is not > > >> > responsible for them in > > >> > any way.**** > > >> > > > >> > _______________________________________________ > > >> > The Uganda Linux User Group: http://linux.or.ug > > >> > > > >> > Send messages to this mailing list by addressing e-mails to: > > >> > [email protected] > > >> > Mailing list archives: > > >> > http://www.mail-archive.com/[email protected]/ > > >> > Mailing list settings: http://kym.net/mailman/listinfo/lug > > >> > To unsubscribe: http://kym.net/mailman/options/lug > > >> > > > >> > The Uganda LUG mailing list is generously hosted by INFOCOM: > > >> > http://www.infocom.co.ug/ > > >> > > > >> > The above comments and data are owned by whoever posted them > > >> > (including attachments if any). The mailing list host is not > > >> > responsible for them in > > >> > any way. > > > > > > _______________________________________________ > > > The Uganda Linux User Group: http://linux.or.ug > > > > > > Send messages to this mailing list by addressing e-mails to: > > > [email protected] Mailing list archives: > > > http://www.mail-archive.com/[email protected]/ Mailing list settings: > > > http://kym.net/mailman/listinfo/lug > > > To unsubscribe: http://kym.net/mailman/options/lug > > > > > > The Uganda LUG mailing list is generously hosted by INFOCOM: > > > http://www.infocom.co.ug/ > > > > > > The above comments and data are owned by whoever posted them (including > > > attachments if any). The mailing list host is not responsible for them > > > in any way. > > _______________________________________________ > > The Uganda Linux User Group: http://linux.or.ug > > > > Send messages to this mailing list by addressing e-mails to: > [email protected] > > Mailing list archives: http://www.mail-archive.com/[email protected]/Mailing > > list settings: http://kym.net/mailman/listinfo/lug > > To unsubscribe: http://kym.net/mailman/options/lug > > > > The Uganda LUG mailing list is generously hosted by INFOCOM: > > http://www.infocom.co.ug/ > > > > The above comments and data are owned by whoever posted them (including > > attachments if any). The mailing list host is not responsible for them in > > any way. > _______________________________________________ > The Uganda Linux User Group: http://linux.or.ug > > Send messages to this mailing list by addressing e-mails to: > [email protected] > Mailing list archives: http://www.mail-archive.com/[email protected]/ > Mailing list settings: http://kym.net/mailman/listinfo/lug > To unsubscribe: http://kym.net/mailman/options/lug > > The Uganda LUG mailing list is generously hosted by INFOCOM: > http://www.infocom.co.ug/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The mailing list host is not responsible for them in > any way. >
_______________________________________________ The Uganda Linux User Group: http://linux.or.ug Send messages to this mailing list by addressing e-mails to: [email protected] Mailing list archives: http://www.mail-archive.com/[email protected]/ Mailing list settings: http://kym.net/mailman/listinfo/lug To unsubscribe: http://kym.net/mailman/options/lug The Uganda LUG mailing list is generously hosted by INFOCOM: http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The mailing list host is not responsible for them in any way.
