Manitoba Centre for Health Policy export

The export process for MCHP uses the file MCHP Export.mdb to generate a date-named file which is then sent to Manitoba Health, where it is de-identified before they send it on to MCHP.

checklist

• how about the ALERT score (MOST), this was not given before but we can add now, what do you think?
• itiss?
• data dictionary

Instructions

Preparations

Copy the following files all to one folder:

• a centralized_data_front_end.mdb with up-to-date created_variables
• Centralized_data.mdb
• PHI.mdb
• CCMDB.mdb
• Legacy TMS Data.mdb
• TISS28_Data.mdb

generating the export file

• open
• click the "Generate output" button

sending

• copy MCHP Export.mdb to a memory stick or CD
• delete the modules and forms, they contain Passwords
• send the memory stick or CD to Jason Berry, Privacy Policy Analyst, of Information Management and Analytics, Manitoba Health, Healthy Living & Seniors (4040D -300 Carlton Street, Winnipeg MB R3B 3M9) and email the password to him (Jason.Berry@gov.mb.ca); Manitoba Health with de-identify the data and pass it on to MCHP.

Data

Structure is same as we use except:

TISS

• will only send L_TISS_Item table

Splitting L_Dxs

• L_Dxs table will be split into L_DXs_MCHP table and L_Tasks_MCHP table.
• L_Dxs table itself will not be sent

Tmp

A subset of Category:All_Projects

• L_TmpV2 table: query L_TmpV2_MCHP filters this to only include entries with MCHP field true in s_tmp table and send as L_TmpV2_MCHP table
• L_TmpV2 table itself will not be sent

Old Data

• old pharmacy (Legacy TMS Data.mdb)
• TISS76 (Legacy TMS Data.mdb)
  • I would include them since MCHP knew these data already - same as previously given. But we can ask Task Grp.
    • added it to task discussion list Ttenbergen 11:56, 2017 April 25 (CDT)