Questioning data back to collectors: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m lnk
m m
Line 4: Line 4:
The purpose of the process is to make the data corrections as little work as possible for all involved, and to integrate any necessary tracking into the process without requiring any external check lists or other paperwork.
The purpose of the process is to make the data corrections as little work as possible for all involved, and to integrate any necessary tracking into the process without requiring any external check lists or other paperwork.


== Option 1 - Facilitated emails ==
== Current state: Facilitated emails ==
The [[data processor]] puts the concern into the [[Notes field]] and presses a button. That button will generate an email to the "regular" collector for the record's location. The email will be auto-populated with enough data to identify the patient, and with the contents of the [[Notes field]] to tell the collector what is wrong. The button will also set the [[RecordStatus field]] to "questioned".
[["email collector about patient data" button]]
When a response from the collector arrives the data processor will update the record and set it to "sent" again, re-validate it with the next round of sends, and set it to vetted as appropriate.
* Trish sent Tina several example emails, they are in Tina's mailbox
** This is not quite what we implemented, but there were some interesting early ideas in this. Pagasa, do you think any of this would work better for you than what we have set up? Ttenbergen 20:27, 2014 September 29 (CDT) {{discussion}}


== Option 2 - Sending back the record ==
== Possibly in future: Sending back the record ==
The [[data processor]] puts the concern into the [[Notes field]] and sets the [[RecordStatus field]] to "questioned". Next time the collector sends, the record is returned to the laptop by a series of queries. The collector updates the record, sets it to "complete" and sends it in with the next round of sends, at which time it will be processed like any other record.  
The [[data processor]] puts the concern into the [[Notes field]] and sets the [[RecordStatus field]] to "questioned". Next time the collector sends, the record is returned to the laptop by a series of queries. The collector updates the record, sets it to "complete" and sends it in with the next round of sends, at which time it will be processed like any other record.  
This process is more automated and would need to be validated before we could implement. It would be the least work for all involved, though, I think.  
This process is more automated and would need to be validated before we could implement. It would be the least work for all involved, though, I think.  
{{Potential Change}}
We keep discussing this, talked about it again today. Ttenbergen 17:44, 2016 December 1 (CST)


[[Category: 2013 data upgrades]]
[[Category: Data Processing]]
[[Category: Data Processing]]

Revision as of 17:44, 1 December 2016

This is an article about a future state, not present state! Collectors, don't start doing the things mentioned in here, but if you see a hole in the process, please speak up.

This article describes the process of the data collector requesting corrections from data collectors. The purpose of the process is to make the data corrections as little work as possible for all involved, and to integrate any necessary tracking into the process without requiring any external check lists or other paperwork.

Current state: Facilitated emails

"email collector about patient data" button

Possibly in future: Sending back the record

The data processor puts the concern into the Notes field and sets the RecordStatus field to "questioned". Next time the collector sends, the record is returned to the laptop by a series of queries. The collector updates the record, sets it to "complete" and sends it in with the next round of sends, at which time it will be processed like any other record. This process is more automated and would need to be validated before we could implement. It would be the least work for all involved, though, I think. Template:Potential Change We keep discussing this, talked about it again today. Ttenbergen 17:44, 2016 December 1 (CST)