Databases Reference
In-Depth Information
Policy Table
Row
#
1
oid
eff-beg
eff-end
asr-beg
asr-end
epis-
beg
clinet
type
copay
row-crt
P861
P861
P861
P861
P861
P861
P861
P861
Nov11
Mar12
Nov11
9999
9999
Nov11
C882
HMO
$20
$50
$30
$40
$30
$30
$30
$55
Nov11
Mar12
2
<3>
4
<5>
<6>
<7>
<8>
Mar12
Apr12
Mar12
Nov11
Nov11
Nov11
Nov11
Nov11
Nov11
Nov11
C882
C882
C882
C882
C882
C882
C882
PPO
Apr12
Aug12
Apr12
Jan13
HMO
POS
Apr12
Aug12
Aug12
9999
Aug12
9999
9999
Apr12
May12
Jan13
HMO
HMO
HMO
HMO
Jan13
Jan13
Jan13
Jan13
May12
Jul12
Jan13
Jan90
Jul12
Aug12
Jan13
Jan90
9999
9999
May12
Jul12
Figure 12.4 Withdrawing a Current Assertion into Closed Assertion Time, and Superceding It.
preserving the assertion time continuity of this effective time
history of P861.
The next thing the AVF does is to make a copy of P861(r6),
apply the copay update to that copy, and give it an assertion time
period of [Jan 2090 - 12/31/9999]. This becomes P861(r8), the
row that
supercedes
row 6. This row is the deferred assertion.
The result is shown in
Figure 12.4
.
Note that this closed assertion is still current. It is currently
January 2013, and so Now() still falls between the assertion begin
and end dates of P861(r6), and will continue to do so until Janu-
ary 2090. So a closed assertion time period is one with a non-
12/31/9999 end date. Some closed assertion time periods are
past; they are no longer asserted. But others are current, like this
one. And yet others may be assertion time periods that lie
entirely in the future.
Note that this process is
almost
identical to the familiar pro-
cess of withdrawing a version into past assertion time and super-
ceding it with a row in current assertion time. The only
difference is that the withdrawn assertion is moved into closed
but still
current
assertion time, and the superceding assertion is
placed into
future
assertion time.
At this point, both P861(r3 & r6) are
locked
. The AVF will
never modify P861(r3) because it is already located in past asser-
tion time. But P861(r6) is also locked, even though it is still cur-
rently asserted. The AVF treats any row with a non-12/31/9999
assertion end date as locked. The reason all such rows are
locked, including those whose assertion time periods are not
yet past, is that the database contains a later assertion which
otherwise matches the locked assertion.
In this case, P861(r6) is locked because the Policy table now
contains a later assertion that was created from it. That later
assertion was supposedly written and submitted based on
