Questioning data back to collectors: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "'''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 u..."
 
m Text replacement - "[[Category: " to "[[Category:"
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''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 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]].
This article describes the process of the [[data collector]] requesting corrections from [[data collector]]s.
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 [[Record Status 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.


== 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 [[Record Status 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.  
{{TT | z
*Possible future scenario: 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.  


[[Category: 2013 data upgrades]]
We keep discussing this, talked about it again today. Ttenbergen 17:44, 2016 December 1 (CST)}}
 
== Related articles ==
{{Related Articles}}
 
 
[[Category:Data Processing]]

Latest revision as of 10:55, 30 July 2025

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

z

  • Possible future scenario: 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.

We keep discussing this, talked about it again today. Ttenbergen 17:44, 2016 December 1 (CST)

  • added: no added date
  • action: no action date
  • Cargo


  • Categories

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Questioning_data_back_to_collectors&oldid=166485"