What's new

Image to IBID Linking Changes. Link images to an iBID record for the following (in order):
If the image is dated within the date range of the iBID,
If the image is within 6 weeks following the latest date of the iBID, or
If the image is within 4 weeks prior to the earliest date of the iBID record.
For clarification: any images that are not linked to an IBID record, are still imported & exist within the patient folder. They are assumed to be wound/skin assessment related images, and so won't appear in the IBID-Image query results.
Imported images are now logged to the Import Report spreadsheet - including which iBID record they were attached to,
iBID records that have no "end date" are assumed to be active admissions if the earliest date is within 2 years, otherwise assumed to be single day admissions (the 6 & 4 week grace periods still apply).
Add the LIVE IMPORT option to the Import software
Added a couple of missing Trauma related lookup list entries ready for the TM user interface modules in AquilaCRS
Small fixes to the Demographics Import & Merge Logic.
Add an option to reset the flags on the imported records in the tm_migration.db database - to allow a full re-import after the test import.

Improved patient demographic record update logic:
Updates core demographics (NHS No, DoB, Sex etc) based on comparison of update dates between TM & AQ, and will fill in any gaps in record.
Will update each section (Name, Address, GP details) based on comparison of last update dates between TM & AQ. Will not "gap-fill" as record integrity may be compromised.
Fixed Image to IBID linking logic:
Images for a patient linked to any single IBID record regardless of date
Images for a patient with multiple IBID records are linked to the IBID record that covers the date of the image, or
..any IBID record that is still active (ie not discharged) and where the image does not pre-date that IBID record.
"Live Import" function available for the first time.
Create Import Report still available which does not modify either the target AQ database or the exported data log.
Creation of Audit Trail during import fixed so that core patient records are replicated to the national database (needed just in case patient becomes a burns patient), but TM and Image data is not.

Previous Telemarque Episode of Care types (Skin, Scar, Wound) are now imported & visible in Aquila (from Aquila v2.10.3 up)

Version 2.12.24 - 17th August 2018

Fixes bug where the software won't start if the config file (tm.ini) does not exist in the expected location
Minor memory leak fixed

New "Export Migration Data" feature in the Aquila - TM Merge software, creates a spreadsheet to make it easier to send support data.
New "Validate Migration DB" feature - allows the user to compare the patient master file with the internal migration workflow data and sort any problems.
Increased efficiencies in algorithm and reporting.

Large update to patient identifying algorithm
Application now includes complete customisation of all algorithm inputs
Outputs an Excel Spreadsheet with potential and actual matches, algorithm settings and any exceptions.

New patient identifying algorithm
New Early Beta of an Excel based migration analysis spreadsheet
Fixed: Export to not overwrite any local edits to key demographics fields in Patient Master File editor
Fixed: Export to make backup of Patient Master.Json file prior to updating

Updated patient merge algorithm
NEW: Import Test function to run a dummy merge/import and create Excel spreadsheet of results
NEW: desktop/start menu icon for "TM/Aquila Import"

FIXED: File opening bug with TM Patient File Editor if tm_migration.db in an "unexpected" location
FIXED: tm_migration.db file location verified within the TM Export. Continues to use the users %localappdata% m_migration folder if present, otherwise will use the %exportdir% m_migration folder.

NEW: Export structure changed. Now stores demographics records for all patients in a single file PATIENT_MASTER.json in the export folder root (as opposed to discrete demographics.json files in each patient sub-folder
NEW: Migration log is stored within the export folder, not the users local app data folder. It's inside a hidden "tm_migration" folder & is called tm_migration.db
NEW: Telemarque Patient Master File Editor - allows the user to edit the demographics of all records and view the exported files and status.

Fixed start up bug with TeleMarque Patient File Editor if initial path did not exist
Fixed bug with patient file viewer

Patients Demographics records are exported to a central Patient Master Index (PMI) file for centralised editing by authorised personnel post-export, pre-import.

Used alternative method of gathering yearly statistics on missing demographic data.

fixed "convert" error. See https://evohelpdesk.manuscript.com/f/cases/5457/tm2-exe-v1-1-0-10-bug-report-EConvertError-2018-04-04-16-26-48-647ms

Created with the Personal Edition of HelpNDoc: Easily create iPhone documentation