Databases Reference
In-Depth Information
description of what that object is like, beginning on that date. As
we have pointed out before, these columns which implement
Asserted Versioning are all shown as date columns in this topic,
but they could as well be timestamps.
Also note that although this column heading is
eff-beg
,all
SQL statements or predicates which reference this column will
refer to it as
eff_beg_dt
. We use hyphens in these column
headings because underscores do not stand out as well, particu-
larly when a column heading is underlined, as it is for all pri-
mary key columns. When these columns names are used in the
text, they will be italicized, although usually we will replace them
with their full spelling equivalents. For example, when referring,
in the text, to the column heading
eff-beg
, we will either use
eff_beg_dt
or the full name, as for example, in saying that the
effective begin date is the temporal delimiter of the start of an
effective time period.
Eff-end. Effective end date
. The date on which the business
data in a row is no longer in effect. In other words, the date
which is one clock tick past the last date on which the business
data in a row is in effect.
Asr-beg. Assertion begin date
. The date on which the business
data in a row is first asserted as being a true and/or actionable
description of what that object is like, during its effective time
period.
Asr-end. Assertion end date
. The date on which the business
data in a row is no longer asserted to be a true and/or actionable
statement of what that object is like, during its effective time
period. In other words, the date which is one clock tick past
the last date on which that assertion is made.
Epis-beg. Episode begin date
. The date on which the episode
which contains the version begins. The begin date of an episode
is always the same as the effective begin date of the first version
in the episode.
Temporal Foreign Key: Client
. The object identifier of the cli-
ent who owns the policy, functioning as a temporal foreign key
to an asserted version Client table.
Business data: Type
. The type of the insurance policy. Types
used in these examples are: HMO (Health Maintenance Organi-
zation); PPO (Preferred Provider Organization); and POS (point
of service).
Business data: Copay
. The copay amount that the policy
holder is obligated to pay for each covered healthcare product
or service.
Row-crt. Row creation date
. The date on which the row is
physically inserted into the table.
