=================== iDART 3.8.0 ===================

iDART is a software solution designed to support the dispensing of ARV drugs in the public health care sector. It supports pharmacists in their important role of dispensing accurately to an increasing number of patients whilst still being able to engage and assist the patient.

Requiremets

• Java runtime environment.
• PostgreSQL database server
• 200 MB hard disk space
• 512 MB RAM

Installation and Upgrade

Full instructions on installing and upgrading iDART can be found in the iDART support manual.

If you have any difficulties the best way to get help is to send an email to the implementers mailing list, idart-implementers@lists.sourceforge.net.

If you are not already a memeber you can join the list by going 
to this url: `<http://lists.sourceforge.net/lists/listinfo/idart-implementers>`_

ChangeLog

iDART 3.8.0

This release contains the following changes:

• Added ATC codes and MIMS References to drugs and drug components (chemical compounds).
• Extended Editing of chemical compounds.
• Added Tier.net data export functionality

iDART 3.7.x

• ensure correct data type for package.weekssupply database column
• fix null pointer if patient search activated with null patientid
• fix null pointer when saving new drug group
• fix bug IDART-290: patient details not loading
• fix blank column in packages leaving report
• don't snap calendar dialog to nextAppointment button on Packaging screen to avoid loading patient history report when selecting date
• in idart.properties file split 'showBatchOnLabels' property into 'showBatchOnSummaryLabels' and 'showBatchOnDrugLabels'
• changes to label printing to fix duration issue: if a batch other than the default batch is chosen when dispensing then the drug labels and summary labels shows 1 of a week prescription even if the duration is 1 month.
• change barcode label printing code to use Barbecue barcode library to fix some eKapa barcode scanning problems
• update to Communicate 2.3 api ** Configurable MSISDN validation
• Update patient packaging to work better for multiple patients with same identifier
• adjust widgets in DestroyStock that were overlapping with the table
• Changes to AlternateIdentifier table caused an error with the Patient History Report
• Non-unique national identifiers in test data caused error when creating a new database with test data
• Re-branded with the new logo's
• Added multiple patient identifiers

Upgrade notes

When upgrading from a version prior to 3.7 you may encounter errors due to duplicate patient identifiers. To assit you in removing duplicates you can use the following query which will append '-duplicate' to any duplicate patient ID's or national patient identifiers.

UPDATE patient 
SET 
   patientid = patientid||'-duplicate'
WHERE 
   id in (SELECT id
          FROM patient a
          WHERE a.id = (SELECT max(id) FROM patient
                WHERE patientid = a.patientid   
                GROUP BY patientid
                HAVING count(*) > 1)) ;

UPDATE patient 
SET 
   idnum = idnum||'-duplicate'
WHERE 
   id in (SELECT id
          FROM patient a
          WHERE a.id = (SELECT max(id) FROM patient
                WHERE idnum = a.idnum   
                GROUP BY idnum
                HAVING count(*) > 1)) ;