TISS28 Form Scanning: Difference between revisions

m Text replacement - "[["Copying" Centralized_data.accdb]]" to ""Copying" Centralized_data.accdb "
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Legacy process 2020-Dec-7  (a few forms still coming and scanned Feb 2021 in from Dec 2020 backlog)
The purpose of this article is to outline the process of scanning TISS28 paper forms, verifying the data in Teleform and committing the data to the [[TISS28_Data.mdb | TISS28 MS Access database]].
The purpose of this article is to outline the process of scanning TISS28 paper forms, verifying the data in Teleform and committing the data to the [[TISS28_Data.mdb | TISS28 MS Access database]].


Line 9: Line 10:
== Preparation ==
== Preparation ==
=== Get files to PC ===
=== Get files to PC ===
*a. Follow the process in [["Copying" Centralized data.mdb]] to copy files used by this process into the [[Frozen]] folder on the [[Data Processor]]s desktop
*a. Follow the process in [["Copying" Centralized_data.accdb]]
to copy files used by this process into the [[Frozen]] folder on the [[Data Processor]]s desktop
*b. Open [[TISS28.accdb]] (use shortcut on processors desktop)  
*b. Open [[TISS28.accdb]] (use shortcut on processors desktop)  
**click the "'''Reconnect .MDBs'''" button <!-- this is NOT [[Reconnect CFE and initial error checks]], the cross checks involved with that don't apply here. -->
**click the "'''Reconnect .MDBs'''" button <!-- this is NOT [[Reconnect CFE and initial error checks]], the [[cross check]]s involved with that don't apply here. -->


=== Teleform scan station prep ===
=== Teleform scan station prep ===
Line 44: Line 46:


Info only:  
Info only:  
* When you click commit the batch sits in [[X:\]]TISS28\ExportData
* When you click commit the batch sits in {{S:\MED\MED_CCMED}}TISS28\ExportData
* See [[TISS28 form images]] for how these images are dealt with after processing
* See [[TISS28 form images]] for how these images are dealt with after processing


Line 71: Line 73:


When all forms/batches for "this round" have been scanned (possibly less often, we'll catch in the end), run each of the TISS_Error_* queries.   
When all forms/batches for "this round" have been scanned (possibly less often, we'll catch in the end), run each of the TISS_Error_* queries.   
{{Discuss | who = Tina | question = _dev_TISS
*Put the queries in a drop down list or accessible through a button in TISS.mdb, similar to way queries are set up in CFE. [[User:TOstryzniuk|Trish Ostryzniuk]] 11:21, 2019 February 7 (CST)}}


* In the following, if there is data for an extra TISS day that is identical to previous, just delete it; if the "offending" TISS day is different from surrounding, then confirm with collector  
* In the following, if there is data for an extra TISS day that is identical to previous, just delete it; if the "offending" TISS day is different from surrounding, then confirm with collector  
Line 91: Line 90:
The reason the checks are done in TISS rather than CFE, even though a frozen version of CFE is used to look up and email, is to reduce push-pull cycles. Could not pull current version of CFE to make changes because TISS Scanning is always done while collectors are [[Sending Patients]].
The reason the checks are done in TISS rather than CFE, even though a frozen version of CFE is used to look up and email, is to reduce push-pull cycles. Could not pull current version of CFE to make changes because TISS Scanning is always done while collectors are [[Sending Patients]].
*Cannot scan tiss if CFE is in pull. I do scanning when CFE is in push and do the checking at the same time.
*Cannot scan tiss if CFE is in pull. I do scanning when CFE is in push and do the checking at the same time.
{{Discuss | who=Pagasa |
* If a frozen version is kept available during TISS scanning anyways then there is no reason to not do these checks in CFE, is there? Or rather, collectors sending would not be the reason. Pagasa, let's talk about this. Maybe we can make this more convenient for you. Or write down the actual reason why it can't be done. Ttenbergen 00:34, 2017 November 12 (CST)
** Discussed this with Pagasa. It would mean doing scanning during send time, and likely doing all fixes during pull time, so all checks could actually be done form CFE. Discussed also w Pagasaa that we would delete the error checks from TISS so there is no duplicates getting out of sync.
*** Do we want to make this change then, Pagasa? You would be the only one who would be affected, so mostly up to you. Maybe confirm with Trish.
}}


== background info ==
== background info ==
Line 103: Line 96:
'''2013-Jan-01'''
'''2013-Jan-01'''
*TISS28 data for the '''entire LOS''' is scanned and stored in new repository [[TISS28_Data.mdb]]. This form has 7 days per page.
*TISS28 data for the '''entire LOS''' is scanned and stored in new repository [[TISS28_Data.mdb]]. This form has 7 days per page.
===Stop Date===
'''2020-Dec-7''' 
*See: [[Change to collect TISS data in CCI Picklist]]


== Related articles ==
== Related articles ==
{{Related Articles}}
{{Related Articles}}


[[Category:Legacy Data Processing]]
[[Category:TISS28 Scanning Process | *]]
[[Category:TISS28 Scanning Process | *]]
[[Category: Teleform]]
[[Category:Teleform]]
[[Category: Data Processing]]
[[Category:Data Processing]]
[[Category: TISS Scanning]]
[[Category:TISS Scanning]]
[[Category: TISS28]]
[[Category:TISS28.accdb]]