PHI.mdb: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
(→‎How PHI data travels: confirmed that PHI data gets updated.)
m (password -main office)
Line 22: Line 22:
# PHI.mdb can be re-linked with [[centralized_data.mdb]] using [[centralized_data_front_end.mdb]]
# PHI.mdb can be re-linked with [[centralized_data.mdb]] using [[centralized_data_front_end.mdb]]


==Password==
Located:  M:\Passwords_mainoffice


[[Category: IT Instructions]]
[[Category: IT Instructions]]
[[Category: 2013 data upgrades]]
[[Category: 2013 data upgrades]]

Revision as of 17:53, 2015 March 2

Data sent via Copy PHI.bat and PHI copy automation and query send_PHI

  • first name
  • last name
  • full DOB (as opposed to the month/year sent to Centralized data.mdb
  • PHIN
  • hospital chart number

in addition the following field is included to re-link the data:

  • D_ID: R_Location & "-" & Pat_ID

This data will be stored in X:\CCMDB\PHI\phi.mdb


phi.mdb change log

2014-02-03

  • added indices for firstname, lastname, phin and chart, to speed up linking tables.

How PHI data travels

  1. regular data enter into CCMDB.mdb by collector
  2. at sending, query send_PHI is called to export all (ie not only complete) records to Regional Server\Output\_PHI
    • this means that previously sent data will get updated, e.g. if a name or PHIN is corrected or added
  3. PHI copy automation: a scheduled task uses Copy PHI.bat to move the files to X:\CCMDB\PHI and to import it into x:\CCMDB\PHI\PHI.mdb
  4. PHI.mdb can be re-linked with centralized_data.mdb using centralized_data_front_end.mdb

Password

Located: M:\Passwords_mainoffice