This is the roadmap for FreeDiams. It can be also concidered as a part of the changelog between main stable versions.
|Next version||Coding started at||Planned release|
|1.0.0||jan 2014||Sept, 2016|
|0.9.2||jan 2014||July, 2014|
Where possible, kindly avoid multiple small edits.
|DDI database update||Jun/Aug 2014||critical||50%|
|French drugs database update||Jun/Aug 2014||critical||100%|
|Canadian drugs database update||Jun/Aug 2014||critical||70%|
|FDA drugs database update||Jun/Aug 2014||critical||50%|
|DDI checking unit-tests (if possible)||Sept 2014||low||0%|
|Allow not-GUI usage of FreeDiams for interaction checking only||Dec 2014||critical||0%|
|Full integration of PIMs computation||Late 2014 / early 2015||critical||30%|
|FreeDiams CorePlugin unit-tests (if possible)||Sept 2014||low||0%|
Currently available workforce in FreeMedForms community is unable to regularly update and review a ddi database. Members of the FMF French community will select a non free ddi database without links to pharmaceutical industry and write a plugin to integrate it with FreeDiams. See External French drugs database & FreeDiams.
lintian -i -I *.dsc *.deb
Now that I've consolidated the GNUmed FreeDiams API I'd like to further develop it. The two use cases I would want to cover next are: 1. pass a list of drugs to FreeDiams and tell FreeDiams “show me what you think about the combination of these drugs in a patient” Ideally, the information could be passed back to the caller in a parseable format. 2. pass a drug to FreeDiams and tell FreeDiams “show me everything you know about this drug” Ideally, the information could be passed back to the caller in a parseable format. Please suggest how we can cooperate on these two things.
How will FreeDiams try to match “non-UID” drugs imported from external EMRs…
The next generation should include some new changes:
Printing should include patient identification and parameters. FreeDiams used with FMF EMR should not rely on the user specified prescription headers (and its tag system) to give acurate and useful information to the pharmacist. For instance, FreeDiams should systematically print the patient's age in months or years and months for pediatric patients under 3 years old. Weight in kilograms only (as recommended by all American and British best practices) must be automatically added to pediatric patient's orders. Some drugs require specific parameters such as body surface area. Knowing renal function can be useful for certain drugs or drugs combinations. Setting all these parameters according to age, sex, or prescribed drugs would be impossible with the current way of handling patient's id information through header and tags.
Question from Jim Busser:
Some time ago, I made some notes that future versions will directly handle umol/L and mg/dL
Is FreeDiams the object of any more development currently, and can it be on any roadmap soon that the units of * mg/dL * umol/L
can be made to recognize and be correctly shown when the following are passed “in” ?
<Creatinine value="1.36" unit="mg/dL"/> <Creatinine value="120" unit="umol/L"/>
Next, can CrCl (mL/min) be auto-calculated for such parameters? The conversion factors are:
* µmol/L / 8.4 –> mg/L * mg/dL x 10 –> mg/L
and for CrCl (mL/min –> mL/sec) the conversion is
* mL/min x 0.0167 –> mL/s
and I would remove mmol/L from the UI, since I do not think those units are anywhere used.
freediams --convert prescription.xml