Proposed Change to Drug Concept Model
Roger believes that there is a fair level agreement that there are four levels of granularity in the classification of drugs for EMR purposes.
Four levels of granularity for drugs
Level 1: Category
Most general (e.g. Pain Medication, HIV Anti-retrovirals) which is used to narrow the universe of drugs. In OpenMRS, concept sets and, in the future, order sets, can be used to groups orderables into categories.
Level 2: Active Ingredients
What the doctor is trying to specify for the patient.
Level 3 Active Ingredients plus strength and form
Strength (the amount or concentration of each active ingredient in the drug) and form (tablet, liquid, intravenous fluid, etc.). This is what should be on the prescription, along with quantity, frequency, refills and other instructions; this should be stored in the EMR.
Level 3 is the level at which a facility's formulary (the list of drugs it keeps available) is specified.
Level 4 Dispensing and Administration
Level 3 plus manufacturer and lot number. This is what the pharmacist/nurse actually dispenses/administers and should be recorded in the pharmacy system (outpatient) or drug administration record (inpatient).
Levels 2 and 3 are based on the organization of a standard nomenclature known as RxNorm, and other standard vocabularies also focus on these levels. Names in the standard vocabularies are specified as chemical names (e.g. at level 2, stavudine/lamivudine/nevirapine), although they may be known at the facility otherwise (e.g. d4T/3TC/NVP or Triomune or Regimen 1a). We try to encourage people to use the standard nomenclature, with other names maintained as synonyms. We do this by guidance in the wiki and by encouraging the use of the MVP concept dictionary. But we don't require it or validate against it. While in the past we may have had multiple entries for the same clinical drug in the drug table under different names, it is our current expectation that each clinical drug will appear only once as a drug table entry or formulary concept, with other names being synonyms; this is to support links with pharmacy systems and alerting.
If a facility wants the fully-specified name (at level 3) to be Triomune 30 rather than stavudine/lamivudine/nevirapine 30mg/150mg/200mg, we allow it (at least as a synonym). If a facility wants to have separate entries for Triomune and stavudine/lamivudine/nevirapine, it is done through synonyms. We allow the same name to be used, at least as a synonym, at level 2 and level 3; however, all orders use level 3, because only at level 3 is there a drug table or formulary concept subclass. In general, our approach has been for the most part to allow the clinic to go on doing what it has been doing, even though we (and substantially all the authoritative literature) are in agreement that prescribing at level 3 using standard ingredient names and strengths is the best at reducing drug administration errors; however, it is up to the system administrator to assure that appropriate drug concepts, drug table entries/formulary concepts, and synonym definitions exist to support the desired use.
There has been a fair amount of discussion about combination drugs. We want to provide the capability of specifying in strongly-typed fields the strength of each ingredient of a combination drug without either overcomplicating the entry of single-ingredient drugs or requiring a facility to do so. In this regard, it should be noted that each ingredient references a level 2 concept and adds strength (value and units) to it.
Use case | Level 2 concept name | Level 3 concept/drug name | Level 3 form | Ingredient name | Ingredient strength value | Ingredient strength units |
|---|---|---|---|---|---|---|
Single | Aspirin | Aspirin 325 mg tablet | tablet | Aspirin | 325 | mg |
Combo w/o | d4T/3TC/NVP | d4T/3TC/NVP tablet | tablet | d4T/3TC/NVP |
|
|
Combo w/ | d4T/3TC/NVP | d4T/3TC/NVP 30 mg/ | tablet |
|
|
|
|
|
|
|
|
|
|
I think this needs further definition because of the impact this has on drug orders. In particular, an order has to reference a concept.
One way to view the existing concept and drug tables is that the concept contains the active ingredient(s) (e.g. "Acetaminaphen", "emtricitabine/tenofovir") and the drug contains the dosage and form; the relationship is one to many. I believe that Darius likes this and have tried to preserve his viewpoint. However, the existing strength/units fields in the drug table do not support combination drugs. This must be changed if the drug table is to be useful. If we use an Ingredients table, we can include an ordered set of them in the drug table. Furthermore, we need DrugConcept (concept+drug) to be a subclass of Concept so that it can be used in orders.. See "Making the Drug Table Useful" above. Concepts which are not DrugConcepts are not orderable; "Acetaminaphen" is an ingredient concept and not orderable, "Acetaminaphen 1000mg tablet" is a DrugConcept and orderable. The ingredient concepts are used by the UI (see below).
Another way to view the existing concept and drug tables is that concept contains the "formulary drug" or "clinical drug", which includes ingredient(s), dosage and form (e.g. "Acetaminaphen 1000mg tablet", "emtricitabine 200mg/tenofovir 300mg tablet"). In this formulation, each ingredient becomes a concept set containing concepts for each dosage and form; the drug table loses most of its functionality. This is what is described above.
In either case, the concept for the drug order is selected and the dosage and form are copied to the drug order (which also needs a change in the units to support combination drugs.
What the pharmacy inventories and dispenses is the clinical drug as produced by a particular manufacturer in a particular lot.
We also need a way to display these drugs in a way which makes it easy for the doctor to pick the appropriate one(s). This involves the use of drug sets ("Analgesics", "HIV ART drugs"), full synonyms ("Tylenol", "FTC/TDF") and ingredients (N/A, "tenofovir"). We can either keep this information on the concept side (using concept sets, the concept_name table and the ingredients table) or on the reference term side (using term-to-term relationships). The drug set can include DrugConcepts and ingredient concepts; the UI will show all their synonyms as well; if an ingredient concept is chosen, then a list of all DrugConcepts containing that ingredient is shown. If we keep information on the concept side, only one active ingredient(s) or clinical drug concept should be in the concept table (the "fully-specified" concept); all other names should be synonyms. These relationships should not involve the drug table; each dosage strength/form should relate to one and only one fully-specified concept. This is not the case with our test data, which must be changed.