The VA monograph (http://www.va.gov/vista_monograph/) for IFCAP - VA's Integrated Fund Control application says:
� Inventory management functionality includes defining desired stock levels of items, autogeneration of replenishment orders, dispensing of goods to supported services or end user, identification of items via bar code technology, supporting communication of inventory information between a secondary inventory point and its associated automated supply cabinet(s), and reports displaying inventory level, distributions and dollar values. Since inventory management is just a part of a larger application, I don't know how readily it can be adapted. Fil Y. Beza Oakland OI Field Office <mailto: [EMAIL PROTECTED]> -----Original Message----- From: Andrew Ho [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2003 10:24 AM To: [EMAIL PROTECTED] Subject: Re: Open-source hospital level medical stock control system On Tue, 22 Jul 2003, Willem van der Walt<[EMAIL PROTECTED]> wrote: ... > Inline with that I want to find out if there are any hospital level > medical stock control systems under development using open-source. Willem, I am not aware of any open-source "medical" system that is currently being used to do stock control. I don't know what the U.S. Veterans Administration uses but a stock control system may be part of VistA. Hopefully one of the VistA experts on this mailing list can answer that. One of our collaborators (Nandalal Gunaratne) talked about creating OIO forms to track medical supplies at their hospital in Sri Lanka. I don't know whether they actually went ahead with that proposal. I have also built an eCommerce site using OIO, complete with product database and inventory control. You can read about the OIO project at www.TxOutcome.Org. You can view the eCommerce site at www.OptoLight.com. (You won't be able to see the "store owner's interface" without a password but I can provide some screenshots and/or a demo if you are interested.) > We might considder developing such a system using a user requirement > specification that we have. If you are able to publish your requirements, some of us may be able to comment more specifically. Rather than starting from scratch, it is possible that you can save some time and money by starting with an existing code base. For example, most of what we need to manage hospital inventory may already exist in the eCommerce application built on OIO code. > I would like to get in touch with people in open-source health systems. Yes, since you have subscribed to the openHealth list, you have found a bunch of us. :-) Best regards, Andrew --- Andrew P. Ho, M.D. OIO: Open Infrastructure for Outcomes www.TxOutcome.Org
