Processing errors in patient data: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
Line 14: Line 14:


==Contact the data collector for additional info==
==Contact the data collector for additional info==
If the previous step does not fix the problem, contact the data collector using the [["email collector about patient data" button]]. This will set the [[RecordStatus field]] to "questioned" and exempt it from [["Vet all sent" button | being vetted]].
If the previous step does not fix the problem:


{{Discuss | who=Pagasa | question =
* contact the data collector using the [["email collector about patient data" button]] or the [["copy patient demographics for questioning" button]] as works better for the problem at hand.
'''''Rest of section probably needs to go; if any entries in notes field remain from this do we need to clean them up?'''' Ttenbergen 13:49, 2015 August 17 (CDT) }}
** This will set the [[RecordStatus field]] to "questioned" for "sent" and exempt it from [["Vet all sent" button | being vetted]].


*As of Dec 9.14 - processor to put in beginning of NOTES" the following: Question:date sent: what question was asked.
{{DT | Automate the populating of notes so button just does it.  
*if question is resolved she removes the notes when she reset record status from Question, back to SENT.
* raise an input box for a summary, if gets content put data and content into Notes, else put nothing.}}
*record status is automatically set to '''question''' if Process uses the paste clipboard button.  Change of record status should only apply to SENT patients.
 
**'''
 
== when resolved ==
*When question is resolved [[Data processor]] removes the notes when she reset record status from Question, back to SENT.


== Editing Patient_ID, location or D_ID ==
== Editing Patient_ID, location or D_ID ==

Revision as of 11:40, 2019 February 7

  • SMW


  • Cargo


  • Categories

Errors or inconsistencies may be discovered during many of our #Quality control processes that might detect errors. This article describes how to process them.

When an error or inconsistency is found, #Correct error from available sources for the correct information where possible. If that does not provide the needed information, #Contact the data collector for additional info.

Process any false positive or uncorrectable records as Known data errors.

Correct error from available sources

If the required change is obvious, apply it. An example for this would be a switch of two digits in a field where several previous records are available for the same patient.

If there is no obvious fix, consult the EPR.

Contact the data collector for additional info

If the previous step does not fix the problem:


Automate the populating of notes so button just does it.

  • raise an input box for a summary, if gets content put data and content into Notes, else put nothing.
  • SMW


  • Cargo


  • Categories


when resolved

  • When question is resolved Data processor removes the notes when she reset record status from Question, back to SENT.

Editing Patient_ID, location or D_ID

Patient_ID and location are used to generate the D_ID. If one of these needs to be edited, make sure the corresponding edits are done in both L_Log table and L PHI table.

Incomplete patients

If errors are found in incomplete patients any fixes done to CFE will be overwritten the next time the data is sent. Because of this, make sure to ask the data collector to make the same changes to their record.

False Positives or known errors

If a query finds an error and review of the data shows that the data is correct then consider if this is a query that is can have false positives (e.g. visitAdmitDtTms that are really close together) or that should never have false positives (e.g. died and then re-admitted).

    • if can have false positives then treat as Known data errors
    • if cannot have false positives then discuss problem with Tina or Herman to correct the query; don't treat as Known data errors

Quality control processes that might detect errors

Related articles

Related articles: