Changes between Version 3 and Version 4 of i2b2 - UHL clinical informatics system integration PATS v2


Ignore:
Timestamp:
09/29/16 10:35:01 (8 years ago)
Author:
dan.lawday
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • i2b2 - UHL clinical informatics system integration PATS v2

    v3 v4  
    33Tags: [[i2b2]]
    44
    5 Version 2 of the i2b2 PATS data integration load will also use SSIS, but will address the following issues with version 1.
     5=== The PATSV2 data all comes from [UHLDWH].[DWBRICCS].[DWPATS] To add another field from here into the Databases on UHLSQLPRIME01\UHLBRICCSDB (for instance the Genvasc or Briccs DB) you will need to do the following:\\ \\
     6
     7Summary:
     8Step 1. create a new proc in [UHLDWH].[DWBRICCS]
     9called [dbo].[CBRU_ETL_CreateObservations_DWPATS_XXXXXXX]
     10with XXXXXXX being the name somthing like CSPost with CS meaning **C**ardia**S**urgery and Post meaning post surgery.
     11 
     12Step 2. Add the new proc to PROC [UHLDWH].[DWBRICCS].[dbo].[LCBRU_ETL_CreateObservations]
     13
     14Step 3. Add the new field/s to the ontology [i2b2ClinDataIntegration].[dbo].[!OntologyCode] and [i2b2ClinDataIntegration].[dbo].[!OntologySourceCode] tables
     15useing the proc [i2b2ClinDataIntegration].[dbo].[!CreateOntologyCode]
     16\\@OntologyID           =
     17\\@ParentID                     =
     18\\@Name                         =
     19\\@!SourceSystem                =
     20\\@!SourceCode          =
     21
     22step 4. This gets automatically done by the way however is importance to acknowledge, The ontology needs to be undated through the other Databases using proc dbo.!UpdateOntologyConceptCodes
     23
     24
     25Details:\\
     26Step 1. to create the [dbo].[CBRU_ETL_CreateObservations_DWPATS_XXXXXXX] you will need to find all the PostProcedure and PreProcedure tables relevant and union join them all together, these are the different formats that have been produced over time any which vary slightly over each iteration, however with a little data manipulation they can be stitched together.
     27for example to gain data from CardiaSurgery you will need all of the following tables all from ([UHLDWH].**[DWPATS]**.dbo.):\\
     28* CS_PostProcedure
     29* CS_PreProcedure
     30* CS2003F_PostProcedure
     31* CS2003F_PreProcedure
     32* CS2010F_PostProcedure
     33* CS2010F_PreProcedure
     34* CS2010G_PostProcedure
     35* CS2010G_PreProcedure
     36and also for the WHO_SYSTEM_NUMBER and NHSNumber...
     37* DWPATS.dbo.Demographics_ALLDEMOGRAPHICS
     38* DWBRICCS.dbo.I2B2_Project_Patients
     39\\
     40as you can see the Pre and Post versions listed above were revised in 2003 and twice in 2010 leading to four versions!.\\ With each version you'll get a Followup, Post, Pre and Sub, however for this example we only needed Pre and Post.
     41
     42The
     43
     44
     45Step 2.
     46
     47
     48
     49
     50\\
     51\\
     52=== Below to be deleted...
     53
     54Version 2 of the i2b2 PATS data integration load will also use SSIS, but will address the following issues with version 1.\l
    655
    7561. Address and document the correct procedure for dealing with duplicates and missing data, by getting Claire Hutton to define which items are true duplicates and may be discarded and identifying a means of distinguish between duplicates where both should be loaded into i2b2.
     
    9581. Move the SSIS packages onto the BRICCS SQL Server so that we can control their running and updating.
    10591. Be configurable so that the source and destination databases can be changed more easily.
     60=== end to be deleted
    1161
    1262[[BackLinks]]