Orphans in Centralized data.accdb: Difference between revisions

(11 intermediate revisions by the same user not shown)

Line 1:

An orphan in [[Centralized_data.~~mdb~~]] is a record with [[RecordStatus field]] = incomplete that was not sent with the latest batch from its location.

An orphan in [[Centralized_data.accdb]] is a record with [[RecordStatus field]] = incomplete that was not sent with the latest batch from its location.

Orphans can be found by ~~query~~ [[~~PL_1orphans~~]] in [[Centralized_data_front_end.accdb]].

Orphans can be found by [[Reconnect_check_orphans query]] in [[Centralized_data_front_end.accdb]].

Orphans can happen if a collector enters a patient, sends once while the patient is incomplete, and then deletes the patient or assigns a new location (since that is used to generate D_ID).

Orphans can happen if a collector enters a patient, sends once while the patient is incomplete, and then deletes the patient or assigns a new location (since that is used to generate [[D_ID]]). Assigning a new location used to be very common, but no longer is after [[PatientFollow Project]].

== Orphan definition ==

There should be no ''incomplete'' records in [[CCMDB.~~mdb~~]] on a laptop that are not included in the ''most recent send'' into centralized database on Regional server. All incomplete records for a given location, the sent date/time should be the same, and it should be the latest date/time sent to the [[~~Centralized data~~.~~mdb~~]] for that location.

There should be no ''incomplete'' or ''complete'' records in [[CCMDB.accdb]] on a laptop that are not included in the ''most recent send'' into centralized database on Regional server.

=== imcomplete orphans ===

All incomplete records for a given location, the sent date/time should be the same, and it should be the latest date/time sent to the [[Centralized_data.accdb]] for that location.

* [[RecordStatus field]] is incomplete

* the record doesn't have the same [[SentDtTm field]] as the newest SentDtTm for that location.

=== complete orphans ===

In the very rare circumstance that something goes wrong during the later stages of sending, a record may not get changed from [[RecordStatus]] "complete" to "sent" at the end of sending. Such a record would not show up as an orphan because it its sent date is the same as the max send date. Usually this record would just be sent again next time (since collectors would not delete an unsent record), and if that send goes through OK it will be set to "sent" then and all is good.

However, if (1) the collector changes or deletes the record between the two sends, or (2) we messed with [[Service/Location]] names between the sends, then the originally sent record would not be updated further in the next send. '''This record would show up as a "complete" orphan. '''

Fixing these would always need to be on a case-by-case basis.

== What to do with orphans ==

Line 21:

Line 31:

=== changed location ===

If there is a second record for the same patient (see eg names, [[~~Arrive DtTm~~]]) with the same Pat_ID and different [[Service/Location]], then the location was likely changed.

If there is a second record for the same patient (see eg names, first [[Service tmp entry]] ) with the same [[Pat_ID]] and different [[Service/Location]], then the location was likely changed.

Orphan can be deleted since the new record will take its place.

=== change Pat_ID ===

If there is a second record for the same patient (see eg names, [[~~Arrive DtTm~~]]) with the same [[Service/Location]] and different Pat_ID, then the Pat_ID was likely changed.

If there is a second record for the same patient (see eg names, first [[Service tmp entry]]) with the same [[Service/Location]] and different [[Pat_ID]], then the Pat_ID was likely changed.

Orphan can be deleted since the new record will take its place.

Line 47:

Line 57:

[[Category: Data Processing]]

[[Category:Data Processing]]

[[Category: PL queries]]

[[Category:PL queries]]

@@ Line 1: / Line 1: @@
-An orphan in [[Centralized_data.mdb]] is a record with [[RecordStatus field]] = incomplete that was not sent with the latest batch from its location.
+An orphan in [[Centralized_data.accdb]] is a record with [[RecordStatus field]] = incomplete that was not sent with the latest batch from its location.
-Orphans can be found by query [[PL_1orphans]] in [[Centralized_data_front_end.accdb]].
+Orphans can be found by [[Reconnect_check_orphans query]] in [[Centralized_data_front_end.accdb]].
-Orphans can happen if a collector enters a patient, sends once while the patient is incomplete, and then deletes the patient or assigns a new location (since that is used to generate D_ID).
+Orphans can happen if a collector enters a patient, sends once while the patient is incomplete, and then deletes the patient or assigns a new location (since that is used to generate [[D_ID]]). Assigning a new location used to be very common, but no longer is after [[PatientFollow Project]].
 == Orphan definition ==
-There should be no ''incomplete'' records in [[CCMDB.mdb]] on a laptop that are not included in the ''most recent send'' into centralized database on Regional server.  All incomplete records for a given location, the sent date/time should be the same, and it should be the latest date/time sent to the [[Centralized data.mdb]] for that location.
+There should be no ''incomplete'' or ''complete'' records in [[CCMDB.accdb]] on a laptop that are not included in the ''most recent send'' into centralized database on Regional server.
+=== imcomplete orphans ===
+All incomplete records for a given location, the sent date/time should be the same, and it should be the latest date/time sent to the [[Centralized_data.accdb]] for that location.
 * [[RecordStatus field]] is incomplete
 * the record doesn't have the same [[SentDtTm field]] as the newest SentDtTm for that location.
+=== complete orphans ===
+In the very rare circumstance that something goes wrong during the later stages of sending, a record may not get changed from [[RecordStatus]] "complete" to "sent" at the end of sending. Such a record would not show up as an orphan because it its sent date is the same as the max send date. Usually this record would just be sent again next time (since collectors would not delete an unsent record), and if that send goes through OK it will be set to "sent" then and all is good.
+However, if (1) the collector changes or deletes the record between the two sends, or (2) we messed with [[Service/Location]] names between the sends, then the originally sent record would not be updated further in the next send. '''This record would show up as a "complete" orphan. '''
+Fixing these would always need to be on a case-by-case basis.
 == What to do with orphans ==
@@ Line 21: / Line 31: @@
 === changed location ===
-If there is a second record for the same patient (see eg names, [[Arrive DtTm]]) with the same Pat_ID and different [[Service/Location]], then the location was likely changed.
+If there is a second record for the same patient (see eg names, first [[Service tmp entry]] ) with the same [[Pat_ID]] and different [[Service/Location]], then the location was likely changed.
 Orphan can be deleted since the new record will take its place.
 === change Pat_ID ===
-If there is a second record for the same patient (see eg names, [[Arrive DtTm]]) with the same [[Service/Location]] and different Pat_ID, then the Pat_ID was likely changed.
+If there is a second record for the same patient (see eg names, first [[Service tmp entry]]) with the same [[Service/Location]] and different [[Pat_ID]], then the Pat_ID was likely changed.
 Orphan can be deleted since the new record will take its place.
@@ Line 47: / Line 57: @@
 {{Related Articles}}
-[[Category: Data Processing]]
+[[Category:Data Processing]]
-[[Category: PL queries]]
+[[Category:PL queries]]