RecordStatus field: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 36: | Line 36: | ||
At the end of the vetting process the data processor will press the "Vet all sent" button. At this time, any sent records that have not been flagged as "questioned" should be clean, so the button will set all "sent" to "vetted". | At the end of the vetting process the data processor will press the "Vet all sent" button. At this time, any sent records that have not been flagged as "questioned" should be clean, so the button will set all "sent" to "vetted". | ||
== | == Data Integrity Checks == | ||
[[ | A lot of [[Data Integrity Checks]] are triggered when this field is set to complete. | ||
=== Data checks that actually check validity of data in this field === | |||
{{Data Integrity Check List}} | |||
== Related articles == | |||
{{Related Articles}} | |||
[[Category: 2013 data upgrades]] | [[Category: 2013 data upgrades]] |
Revision as of 01:59, 2018 October 27
if you are looking for the field collectors can use for their own custom designations, see Record field
Data Element (edit) | |
Field Name: | RecordStatus |
CCMDB Label: | Status |
CCMDB tab: | Top Row |
Table: | L_Log table |
Data type: | string |
Length: | 20 |
Program: | Med and CC |
Created/Raw: | Raw |
Start Date: | 2013-04-24 |
End Date: | 2300-01-01 |
Sort Index: | 80 |
status of the data in the record. Possible values are complete, sent, questioned and vetted.
The field can be seen on the Patient Viewer and the Patient List. The setting of the field will affect processing as follows.
Possible Values
incomplete
A patient is automatically set to incomplete when a new record is created.
complete
Once a patient's record is complete and all checkboxes in the Patient Viewer are set, the collector will try to set the patient to "complete". This changes triggers the CCMDB Data Integrity Checks that are set to run on completion; if any problems are found, the record is set back to "incomplete". Records that are set to complete will be treated differently during the next sending. Ideally the collector will set the field to "complete" as soon as you have entered the last data for a patient, while they still have the chart to be able to fix errors without having to get the chart again. Also, it saves time during sending.
sent
At sending, records that were set to "complete" will be changed to "sent" in both CCMDB.mdb and Centralized_data.mdb. A record that is "sent" can no longer be edited or overwritten by CCMDB.mdb during sending. If a record needs to be re-sent, the data processor needs to change the setting to "incomplete" first. In CCMDB.mdb, the Delete Sent Patients button checks for this field to be set to "sent" to delete patients.
questioned
As part of the Centralized data Vetting Process the data processor runs queries to ensure data is valid. If any "sent" record has problems, she sets the recordstatus to "questioned". In the future a questioned record may be copied back to the collectors laptop automatically at the next send time to facilitate validation; likely the data processor would put an entry into the Notes field to tell the data collector what is wrong. See Questioning data back to collectors.
vetted
At the end of the vetting process the data processor will press the "Vet all sent" button. At this time, any sent records that have not been flagged as "questioned" should be clean, so the button will set all "sent" to "vetted".
Data Integrity Checks
A lot of Data Integrity Checks are triggered when this field is set to complete.
Data checks that actually check validity of data in this field
Data Integrity Checks (automatic list)
App | Status | |
---|---|---|
Reconnect check orphans query | Centralized data front end.accdb | implemented |
Reconnect check Completes query | Centralized data front end.accdb | implemented |