Posts Tagged ‘Data sets’

Open Medication Datasets

July 11, 2013

In our quest for CCHIT Oncology Certification, we will also be required to be CCHIT Ambulatory EHR certified. This Ambulatory certification has a good amount of overlap with the Meaningful Use requirements, including most of the medication/allergy/drug interaction requirements. I have spent many hours going through medication datasets trying to find the right combination that will give us what we need. This post serves as both a recap of my research for documentation but will hopefully provide a good starting point for others looking for open datasets for medications and allergies.


General medication list requirements include:

1.Keeping  a dataset of prescribable  medications. This list must include at a minimum drug name, generic name, dose, strength and route. This list should be comprehensive and concise enough to provide the prescriber with a terse, yet complete list of medication options.

2. A mechanism for documenting current and past medications and keeping that list up to date.

3. A way for providers to add new prescriptions and send them to the pharmacy as (non-faxed) eRx.

4. A way to provide information on any drug interactions.

5. The ability to create CCD/CDA documents for continuation of care.

6. The ability to accept continuation of care documents from other facilities.

7. Not cost a fortune.


Given the above requirements, two fundamental notions must be captured in the medications dataset: The drug list and a list indicating drug interactions.


Many of the proprietary medication datasets (FDB, Medi-span, etc.) are not open and I am sure they are not cheap.  There are no prices on their website which makes me weary of their pricing strategy. I don’t have time or energy to negotiate pricing and worry about whether I got a good deal.


There are open alternatives, the main one being RxNorm.  This dataset is very comprehensive and is freely available. however, it is more of a translation device between other datasets than a terse, canonical list of medicines.  RxNorm is constructed by collating medicines from many sources, FDA, VA, Gold Standard, SNOMED-CT, even the proprietary medications are linked.  Because of the vast breadth of this RxNorm, it is not immediately suitable for fast data entry.


This is why Kin-Wah Fung of the Lister Hill National Center for Biomedical Communications, NLM has led the effort to create RxTerms. RxTerms is a curated list of drugs derived from information in RxNorm and is designed for efficient provider data entry. The medication names are distinct, concise and include the required information for prescribing. And each medication or concept in RxTerms links to corresponding concepts in RxNorm. Here is a great demo of their work.

However, RxTerm was not designed to directly provide drug interaction data.


For medication interaction data, we will be using the NDF-RT dataset, created and maintained by the U.S. Department of Veterans Affairs, Veterans Health Administration (VHA). This dataset is linkable to both RxNorm and RxTerm and is also freely available.

The queries will be a bit cumbersome but all of the needed data is there. You can try the demo of this interaction mapping at the RxMix site.


With these two datasets, RxTerms and NDF-RT, we will be able to provide concise lists of medications to our providers, check drug interactions and transmit and receive continuation of care documents to and from external providers or HIEs.