Changes between Version 2 and Version 3 of i2b2 - UHL clinical informatics system integration PATS v1

Timestamp:

03/12/13 11:16:57 (13 years ago)

Author:

Richard Bramley

Comment:

--

i2b2 - UHL clinical informatics system integration PATS v1

@@ -45 +45 @@
 ||GGHPCI_INITIALGGHPCIVIEW||2||DateOfProcedureCCAD||
 
+=== Duplicate CATH_CATHINITIALVW investigation
+
+Reasons:
+a. Procedure abandoned
+a. 2nd record has very little data
+a. Different procedure site
+
+=== Duplicate CS2003F_PostProcedure investigation
+
+Reason:
+a. 2 procedures.  One of which has very little data.
+
+DateOfDischargeOrDeath is the only relevant date against the record.  However, there is a days post op field that is different for both records which could be used to calculate a date.  However, this could still produce duplicates.
+
+=== Duplicate CS2010F_PostProcedure investigation
+
+Same reason and patient as for CS2003F_PostProcedure.
+
+=== Duplicate EPS_EPSINIVW investication
+
+Reason:
+a. Field 'IsThisARe_Do' is set to yes.
+
+The field DateOfAdmission is used as the start date for the EPS_EPSINIVW table.  Alternative fields for start date on this table are date_timeOfProcedure and procedureStartTime.  Both of these, however, also have records where the date is NULL.  All three fields could be coalesced to reduce the risk of an error.
+
+===  Duplicate GGHPCI_FLWGGHPCIVIEW investigation
+
+a. Status changed
+
+This looks like a table where they can go in and change the status of a previous procedure.
+
+The dates look like they might be from an import, so this might explain it?
+
+=== Duplicate GGHPCI_INITIALGGHPCIVIEW investigation
+
+a. More than one procedure on the same day for both duplicates.
+
+DateAndTimeOfOperation seems to be unique.