ODDB.org is an OpenDrugDatabase that enables the search for Drugs by their ActiveAgent, Name, Producer, ATC-Code. You can do a price comparison between the Original Drug and the Generic by Clicking on the Drug’s Name (‘Omed’ is a nice example). The database tells you when the Drug has been registred in Switzerland. ODDB.org exports the complete Data in the YAML.org Format (14’702 registred products). The database is updated at least once a month through the official government publications by Swissmedic and the BSV. We would like to inculde drugs from other countries as well. Next step should be the Drugs registred in Canada. Check it out and drop us some Feedback or a Donataton ;-). The site is still in German only ;-( English will come soon.
Slashdot currently has a post on OSS Grants with the example of a medical records system. Looks like some LinuxMedNews types, like Irving Buchbinder of FreeMed fame, have started to weigh in, but I thought I’d add it here.
Largely as a result of the discussion on the OpenHealth(tm) list, the American Medical Informatics Association will now accept open format submissions, such as RTF, to its 2004 Medinfo conference. Previously AMIA would only accept the proprietary .doc format. Congratulations to both FOSS advocates and AMIA!
Blogger Con 2003: Oct 4-5
Harvard Law School campus
Weblogs in Medicine and Research: (Oct 5)
Moderater Jacob Reider
“…With the explosion of medically related information and products now available on the Internet, medical weblogs can serve an important role in providing insight into the practice of medicine for both healthcare providers and the public…”
I would add that they can also be quite effective for information within an institution. Perhaps there are features or processes that a weblog (klog) does well that would be good to have in a medical.
Plus, there are opensource weblogging tools.
It looks like the American Academy of Family Physicians deal with Medplexus is off. However, it looks like VistA might be in the running now: ‘…This rejection was a disappointment, but it did not dampen the AAFP members’ or leadership’s interest in EHRs. Momentum continued to build for a low cost, standards based EHR solution. During this periood between January and the present, –we received many hundreds of emails from AAFP members, as well a other specialists in both primary care and the subspecialties, in support of the AAFP’s activist approach and encouraging the AAFP to continue to seek a solution that would afford physicians greater access to EHR technology; –we established relationships with people in the Veterans Administration (VA), led by Gary Christopherson, VA CIO, and the Centers for Medicare and Medicaid Services (CMS), many of whom who share our interest in creating a breakthrough in EHR adoption among AAFP members and other primary care physicians. We now talk regularly with the people in charge of VistA (the VA’s excellent EHR systems) about its possible wider use outside the VA…’ Complete text of Dr. Kibbe’s announcement is within.
First, let me explain that your name is included in this e-mailing
because I believe you contacted me at one time about the AAFP’s EHR
project asking for information, and you are either an AAFP member or a
close friend of the AAFP.
If you do NOT want to receive information about AAFP activities to
promote low cost, standards-based health information technology (HIT)
for family medicine, or I have you on this list in error, please reply
informing me of that fact. In that case, my apologies. Everyone hates
Conversely, I encourage you to forward this news on to your friends and
colleagues in the AAFP and elsewhere who are interested in these
topics. If they email me, I will add them to the list.
Secondly, this email is going to be rather longish. I will try to make
subsequent memos shorter. But, as you’ll see, there is a lot happening
within the AAFP on the subject of EHRs and HIT generally.
A BRIEF RECAP — As most of you know, the AAFP Board of Directors passed
a resolution in January of 2003 supporting the establishment of a new,
non-profit organization (the Foundation) that would further develop and
distribute a low cost open source EHR. The effort was made possible
because a start-up company, Medplexus, which also has a HIPAA-ready PMS
product, offered to gift its EHR software product to the AAFP for this
The impetus behind the AAFP’s decision to become more active in
promoting the use of EHRs among the membership was an earlier Board
resolution, passed in January of 2000, that set two goals: that all
AAFP members would use the Internet by 2003, and all would be using
EHRs by 2005, in their practices. The leadership within the AAFP feels
strongly that the future of family medicine is linked to FPs having
excellent information management skills and technology, and that these
are key to improving quality and safety of care.
While that first goal has largely been met, we are still a long way from
completing the second: only about 5-8% of AAFP members currently use
EHRs in their practices, although there is data suggesting that many
more of us would acquire and use EHRs if the barriers of high cost and
lack of standardization could be dealt with.
To address and reduce those key barriers directly, the AAFP Board of
Directors in January 2003 passed a resolution that directed the AAFP
staff,, to develop a business plan for the open source EHR, and also
committed money for the Foundation, PROVIDED at least three (3)
additional medical specialty societies could be recruited to join the
AAFP in this effort to produce a low cost EHR solution. The AAFP felt
the right thing to do was to make this a joint venture with other
medical specialty societies, and to share the leadership with them.
For about 6 months, the team led by Douglas Henley, MD, AAFP Exec. VP
and myself worked very hard to convince our medical specialty society
colleagues to join the AAFP. Speaking personally, this was a valuable
and educational experience, and I came to know many of the people in
the ACP, AAP, ACOG, AMA, and other societies quite well.
For a number of reasons, however, best left to the individual medical
societies to explain, we did not get their support for an open source
EHR or the new non-profit, shared-governance organization to distribute
it. In May of 2003, not getting the critical mass needed to carry out
the AAFP Board’s directive of Jan 2003, we withdrew the plan and
released Medplexus from our agreement with them. The AAFP did not
spend any monies, as the conditions mentioned above were not met.
MOVING ON — This rejection was a disappointment, but it did not dampen
the AAFP members’ or leadership’s interest in EHRs. Momentum continued
to build for a low cost, standards based EHR solution. During this
periood between January and the present, –we received many hundreds of
emails from AAFP members, as well a other specialists in both primary
care and the subspecialties, in support of the AAFP’s activist approach
and encouraging the AAFP to continue to seek a solution that would
afford physicians greater access to EHR technology; –we established
relationships with people in the Veterans Administration (VA), led by
Gary Christopherson, VA CIO, and the Centers for Medicare and Medicaid
Services (CMS), many of whom who share our interest in creating a
breakthrough in EHR adoption among AAFP members and other primary care
physicians. We now talk regularly with the people in charge of VistA
(the VA’s excellent EHR systems) about its possible wider use outside
the VA; –we met with Tom Scully, CMS Administrator, and his staff, and
with William Yasnoff, MD, director of the NHII office, about the
importance of family physicians in the establishment of a national
health information infrastructure (NHII), and to federal government
efforts to improve quality of care for patients with chronic illnesses;
–many software and IT firms, large and small, began to contact the
AAFP to discuss ways to collaborate with us. We have learned that
there is strong IT industry support for the AAFP’s stance on
affordability and standards for office-based HIT; –we received an
invitation from CMS to submit a proposal for a Pilot Project to
implement the EHR application in a small number of family practices
across the country, in part to study ways to make implementation
efficient and in part to incorporate quality measurements into the
routine of EHRs.
SPECIFIC PROJECTS and ACTIVITIES –The Pilot Project has received some
national attention, in part because in July the AAFP received the
backing and support of HIMSS, the largest IT industry membership
The Pilot Project is truly becoming a collaborative effort. The planning
of the Pilot Project is being worked on by a 12 member Steering
Committee that now meets every other week, while we await word on
funding from CMS. HIMSS staff are providing very valuable project
management skills and administrative services. Medplexus has continued
to work with the AAFP to improve its features and functionality, and
will provide its software to the Pilot Project practices at no charge.
Siemens has agreed to assist the AAFP with engineering expertise and
managed hosting for the Pilot Project, and a large national hardware
manufacturer has offered to provide computers to the participating
practices. We are hopeful that the Pilot Project roll out will occur
in early October. There is still time for practices who want to
participate in the Pilot Project to apply, and any who do should
contact me immediately.
In addition, we are now negotiating with a number of software and IT
firms to provide lower cost options for acquisition and use of EHRs,
and to encourage collaboration on standards, such as interfaces between
PMS and EHR software, that will make these systems more compatible and
less costly to own and maintain. We are encouraging vendors to commit
with us to the principles of affordability, compatibility,
interoperability, and data stewardship. We hope to announce the
results of several of these agreements later in the fall, and therefore
to make several new options available for our members who wish to
One of the most important standards under development is the Continuity
of Care (CCR) document standard, which the AAFP is co-sponsoring with
ASTM, the Mass Medical Society, HIMSS, and others. This is an XML
document standard that will contain a core set of health information on
each patient — problem list, medications, allergies, etc. — and which
will be capable of being imported and exported from a number of
vendors’ software products, or carried by a patient on a smart card,
USB memory stick, or via secure email attachment. Think of the CCR as
a referral document or “face sheet” or mini-medical history, which is
able to be read by a universal reader, a browser, in PDF file format,
or in Microsoft Word 11. Several EHR vendors have already agreed to
use the CCR as the first step in EHR interoperability. I am seeking
AAFP member help with this standard, and would love to hear from any of
you who want to contribute your expertise. The AAFP is hosting a CCR
Consensus Meeting in Kansas City on October 23. Please contact me if
you have an interest in attending this meeting.
Finally, the AAFP is working with all of the major standards development
organizations, such as HL7, ASTM, and WEDI, to participate in EHR
definitional standards. We will play a role in these as the
opportunities arise to do so.
In summary, then, the AAFP will not be developing our own open source
EHR, nor doing so in concert with other medical specialty societies as
per the plan of several months ago, at least in the near term.
However, we will be working with many different vendors, the
government, with health plans, and national IT firms to help create a
breakthrough in price, service, and standards that will make it
possible for family physicians and others to acquire and use this
technology in their offices for the first time. And we will be making
additional AAFP resources available to our members to assist them in
selecting, implementing, and making good use of EHRs.
I hope you find this email helpful. If you’re going to be at the Annual
Scientific Assembly in New Orleans Oct 1-5, please make a point of
getting together with me. I’m very interested in your points of view.
With very kind regards, DCK
David C. Kibbe, MD
Director Health Information Technology
American Academy of Family Physicians
Chapel Hill, NC
The next VistA Community Meeting will be held in Norcross, Georgia on Thursday, October 16 through Sunday October 19, 2003. The main meeting will be at The Royal (http://www.royalnorcross.com), with additional meeting space at the New City Hall (http://www.norcross-ga-gvt.com/Information/information_maps.asp). Complete details can be found here.
PhpMed is proud to announce the availability of both incoming and outgoing fax service capability as well as integrated inter-office communication via a built in webmail interface.
Incoming Fax Service works like this:
All incoming faxes are converted to a pdf file.
You can then use the full version of Adobe Acrobat to edit the pdf file if necessary. The incoming faxes all get spooled to a network share, which allows you insant access to drag and drop the files to their correct destinations.
Outgoing Fax Service works like this:
At the time of adding a refill to a medication, if you select “faxed” as the method, a window appears with all the refill infomation, patient information, etc. You choose a pharmacy from the drop down list and hit send. That’s it! A record of the fax, who it was to, date, patient name, med name, etc is automatically recorded to a fax log which is then viewable from the administration panel.
You can also set up a “fax” printer on your windows clients and submit jobs to it from any windows application like a normal printer. Upon doing so, you are presented with a window which asks you to select a recipient, which is pulled via ODBC from the fax server. So all your fax recipients are pulled from the same source, no need for duplicate phonebook programs. Once you select a fax recipient, hit okay and the file is sent to the fax server. You can them monitor the progress of the file being sent.
This is not a flashy thing, just a real world implentation that works.
Please see the screenshots on the website.
The EHR Collaborative Final Report is out. Free and Open Source are mentioned on page 16 ‘The two things that will kill implementation of this standard are cost and user interface, neigher of which were addressed today. The cost issue can be addressed by making these standards completely free, transparent, down to the nth degree of granularity, and then supporting free open source development of the functional components. This can work with the vendors, not against them.’ and 48 ‘Implement quality issues with free and open source public domain software or database.’ I think I can take credit for the comment on page 48, but it bears only a little resemblence to what I actually said. Oh well. Would anyone like to take credit for page 16?