Sent files naming conventions: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) Dawna - (and anyone) if there are more questions about this, always feel free to post again. |
Ttenbergen (talk | contribs) m legacy and link clean up |
||
| Line 1: | Line 1: | ||
Legacy, no longer relevant now we are not sending to [[TMSX]] | |||
We have a tight convention for the file names used in sending data. Adherence to this is required for our automated processes to work. Since file generation is automated as well, this is for reference only and should not affect data collection. | We have a tight convention for the file names used in sending data. Adherence to this is required for our automated processes to work. Since file generation is automated as well, this is for reference only and should not affect data collection. | ||
| Line 8: | Line 10: | ||
for example: M_12_HSC_H4H_gh.csv | for example: M_12_HSC_H4H_gh.csv | ||
[[Category:Legacy Data Processing]] | |||
[[Category: | [[Category:Master Database Programs]] | ||
[[Category: | |||
Latest revision as of 15:45, 2015 May 13
Legacy, no longer relevant now we are not sending to TMSX
We have a tight convention for the file names used in sending data. Adherence to this is required for our automated processes to work. Since file generation is automated as well, this is for reference only and should not affect data collection.
The sent files naming conventions' are:
- <identifier>.csv - the actual data file
Where <identifier> stands for
- <M for medicine or C for icu>_<batch #>_<3-letter hospital>_<2-3-letter ward>_
for example: M_12_HSC_H4H_gh.csv