<< | Index | >>
---
Continue work. Add test to download file from EPHA. Example is still interaction is between Marcoumar and Aspirin.
After discussion with Zeno we agreed that the following links should work. (In decreasing priority to implement)
The presentation of interaction should be textual. It might be helpful to add a link to the 3-dimensional view of epha.
Looking at the results of the first import I see that I forgot, that you have often more than 1 interaction for one atc_code. Therefore I must rethink about what is the unique key for the epha-interactions.
I will probably need a epha_interaction_observer where the following methods would probably be util. others, other(atc_code) to find other atc_codes. This should work whether we specify first atc_code_1 or atc_code_2. Looking at sequence_observer I think the following utility-classes should also be defined:
Question: Should we attach also a history to each interaction-record as defined by the csv? Then we should probably create a helper gem like the swissmedic-diff?
From Epha.ch/de/interaktionen I get a coding for the values in :severity: A => Keine Massnahmen notwendig B => Vorsichtsmassnahmen empfohlen C => Regelmässige Überwachung D => Kombination vermeiden E => Kontraindiziert 0 => Keine Angaben
Created (local, throw-away) helper script to run all epha_interactions related unit test. Refactored epha_interaction to require atc_code_self and atc_code_other as parameters to new.
Import took about 15' minutes. We should probably have a comparator to only import changed items. No, Zeno plans to run the import manually only when the data changes (once or twice a year).
To get the name and other interesting stuff of the atc_code we can use in bin/admin
atc_class('N06AB06')
-> Sertralin
atc_class('N06AB06').packages.first.name
-> Zoloft, Filmtabletten
ch.oddb> atc_class('N06AB06').packages.first.iksnr
-> 52251