RecordStatus field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (→‎Possible Values: documented how the "deleted" entry for RecordStatus works; it's an old entry now but I don't think I ever documented it before.)
Line 31: Line 31:
=== only in [[CCMDB.mdb]] ===
=== only in [[CCMDB.mdb]] ===
==== deleted ====
==== deleted ====
When the [["Delete Sent Patients" button]] is used, part of the record is actually retained for use by [[Cognos Report Integrator]] and [[EPR Reports Integrator]]. Records that are set to "deleted" don't show up in the [[Patient List]]. These records are deleted by the [["Delete Sent Patients" button]] when they are more than 90 days old.  
When the [["Delete Sent Patients" button]] is used, part of the record is actually retained for use by [[Cognos Report Integrator]] and [[EPR Reports Integrator]]. Records that are set to "deleted" don't show up in the [[Patient List]]. These records are deleted by the [["Delete Sent Patients" button]] when they are more than 90 days old. The entries of child tables are deleted at the time the record is set to "deleted", with the exception of the tmp projects, which are retained for access to [[Boarding Loc]], which is relevant for [[Cognos Report Integrator]].


=== only in [[Centralized data.mdb]] ===
=== only in [[Centralized data.mdb]] ===

Revision as of 11:02, 2020 June 3

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.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


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.accdb 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.accdb and Centralized_data.mdb. A record that is "sent" can no longer be edited or overwritten by CCMDB.accdb during sending. If a record needs to be re-sent, the data processor needs to change the setting to "incomplete" first. In CCMDB.accdb, the "Delete Sent Patients" button checks for this field to be set to "sent" to delete patients.

only in CCMDB.mdb

deleted

When the "Delete Sent Patients" button is used, part of the record is actually retained for use by Cognos Report Integrator and EPR Reports Integrator. Records that are set to "deleted" don't show up in the Patient List. These records are deleted by the "Delete Sent Patients" button when they are more than 90 days old. The entries of child tables are deleted at the time the record is set to "deleted", with the exception of the tmp projects, which are retained for access to Boarding Loc, which is relevant for Cognos Report Integrator.

only in Centralized data.mdb

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 Centralized data 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)

 AppStatus
Reconnect check orphans queryCentralized data front end.accdbimplemented
Reconnect check Completes queryCentralized data front end.accdbimplemented

Related articles

Related articles: