W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > March 2019

Re: 7 days left to comment (was Re: representing potential drug-drug interaction knowledge and evidence - Last commenting period for the W3C Community Group report

From: Macfarlane, Colin R. (ELS-LOW) <c.macfarlane@elsevier.com>
Date: Thu, 21 Mar 2019 13:06:22 +0000
To: "public-semweb-lifesci@w3.org" <public-semweb-lifesci@w3.org>
Message-ID: <BN7PR08MB3924101917C06145258A4390F3420@BN7PR08MB3924.namprd08.prod.outlook.com>
Dear Rich,



It is great to finally have a model in the drug interaction domain that is grounded in the clinical requirements of day-to-day practice. The comments I have are not about the model per se (which I think is spot on) but about how you represent the model in your report and about some of the value sets used to illustrate the examples.



Firstly, it would be nice to see some graphical representation of the model; this would certainly help reader-interpretation of the narrative text and ensure that, as readers, we are envisaging the model in the same way as the development group. For instance, this would help determine whether <Seriousness> is an attribute of <Clinical consequences> or an attribute of the <PDDI> directly.



The one area that I might take issue with the model itself is in your definition of <Contextual information/modifying factors>. In particular, the inclusion of product formulation (dose form) in this category. A medicinal product's dose form is one of its defining characteristics and it is therefore not a feature that can be changed without changing the medicinal product entity itself. And if you change the medicinal product entity then you have a different PDDI (because the <Drugs Involved> have changed). The report illustrates this nicely with the example PDDI between warfarin and NSAIDs, in particular the focus on warfarin and diclofenac. On the one-hand  there is <topical diclofenac> for which the Operational Classification yields "No special precautions", and on the other-hand there is <non-topical diclofenac> (let's assume for a minute that that means oral/parenteral diclofenac) for which the Operation Classification indicates that evasive action may be necessary. I would argue that the description of the clinical consequences ("Increased risk of bleeding including gastrointestinal bleeding, intracranial hemorrhage, and cerebral hemorrhage") is simply not accurate for <warfarin + topical diclofenac> and that's because <topical diclofenac> is a fundamentally different medicinal product to <oral/parenteral diclofenac> with a fundamentally different drug interaction profile.



This is quite different from considering a PDDI that is modified because a patient's renal function is significantly impaired. Here, the PDDI and its associated clinical consequence are essentially similar irrespective of the patient's renal function, but the impact of that PDDI may be very different because of the patient's inability to clear a metabolite, for instance.



Staying with the NSAID example, drug class-level PDDIs are fine in principle, but all members of that drug class must have uniform drug interaction characteristics. That is not something that can be said of NSAIDs, at least not as the report defines them in A.1.4.12. For instance, the NSAID value set includes <1236089 | Benzydamine hydrochloride 3mg oral lozenge> which, according to the UK Summary of Product Characteristics produces peak plasma levels that are "not sufficient to produce pharmacological systemic effects".. So, like the topical diclofenac discussed earlier, benzydamine lozenges have a very different drug interaction profile to say, parenteral ketorolac or oral celecoxib. As such they cannot all be in the same grouper interactant (namely "NSAIDs").



Another difficulty with the NSAID value set is that it includes ingredients e.g.  <3355 | Diclofenac> as well as clinical drugs e.g. <1442116 | Diclofenac 18mg oral capsule>. Just as an ingredient cannot treat a disease, so too ingredients are not capable of participating in PDDIs - this is a feature of formulated medicinal products designed to be administered to patients. With this in mind, it would be better to avoid including ingredient concepts in your NSAID value set.



In Section 3.1, describing the interactant as "NOT topical diclofenac" creates an ambiguity since this entity includes oral, parenteral, rectal, and ophthalmic forms of diclofenac. The latter has a different drug interaction profile to the other dose forms which deliver active ingredient to the systemic circulation and, like topical diclofenac, needs to be considered as a separate entity to the oral/parenteral/rectal formulations.



In Section 4.2, first paragraph, there is a typo: "pharmacists"



Section A.1.4.2 is an example of where RxNorm is used to group together both single-ingredient medicines and multi-ingredient medicines within a single-ingredient grouper (in this case, "aldosterone antagonists"). This gives the impression that, for instance, <198224 | Hydrochlorothiazide 25mg / Spironolactone 25mg oral tablet> is a type of aldosterone antagonist which, as a combination product, it cannot be. A better alternative would be to use SNOMED CT which has made significant changes in the last couple of years to its handling of multi-ingredient medicinal products; for example, <SCTID: 346312000 | Product containing aldosterone receptor antagonist>.



Based on the content of Section A.1.4.4 I suspect you are referencing ICD-10-CM rather than the unmodified ICD-10. If that is indeed the case, it would be worth specifying that in the section title.



Now, I'm not an expert in anatomy but it looks to me like the title of Section A.1.4.4 is inaccurate because there are several disorders listed that are not cerebral hemorrhages. For instance, subdural, subarachnoid, and cerebellar hemorrhages are siblings of cerebral hemorrhage not subtypes of it. Also, <S06.8 | Other specified intracranial injuries> (the last item in this listing) includes some descendant concepts that are not hemorrhagic in nature.



In Section 3.2 the clinical consequence uses the term "chronic myeloid leukemia" to refer to a disorder. However, in Section A.1.4.5 where the corresponding SNOMED CT codes are listed, the last item in the list (<SCTID: 128826001 | Atypical chronic myeloid leukemia, BCR/ABL negative>) represents a morphological abnormality. As such, this would not typically be found in a patient's problem list.



Finally, I think it would be more accurate to label Section A.1.4.7 as "Upper gastrointestinal bleeding...".



Once again, this report is a great piece of work and I think will be extremely valuable in the future.



Kind regards

Colin Macfarlane

Colin Macfarlane
Medicines Optimisation Team Lead
ELSEVIER | Clinical Solutions
Received on Thursday, 21 March 2019 15:42:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:22:16 UTC