From be4ddba3cd9fc94e39ccd9844910dbb235416b7f Mon Sep 17 00:00:00 2001 From: Joaquin Date: Sat, 28 Sep 2024 05:59:59 -0700 Subject: [PATCH] Editorial updates to ChargePeriodStart --- specification/columns/chargeperiodstart.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/specification/columns/chargeperiodstart.md b/specification/columns/chargeperiodstart.md index fe701b161..67c63c45a 100644 --- a/specification/columns/chargeperiodstart.md +++ b/specification/columns/chargeperiodstart.md @@ -2,7 +2,10 @@ Charge Period Start represents the [*inclusive*](#glossary:inclusivebound) start date and time within a [*charge period*](#glossary:chargeperiod). For example, a time period where ChargePeriodStart is '2024-01-01T00:00:00Z' and [ChargePeriodEnd](#chargeperiodend) is '2024-01-02T00:00:00Z' includes charges for January 1, since ChargePeriodStart is *inclusive*, but does not include charges for January 2 since ChargePeriodEnd is [*exclusive*](#glossary:exclusivebound). -ChargePeriodStart MUST be present in a FOCUS dataset, MUST be of type Date/Time, MUST be an *inclusive* value, and MUST NOT contain null values. ChargePeriodStart MUST match the beginning date and time boundary of the effective period of the charge. +The ChargePeriodStart column adheres to the following requirements: + +* ChargePeriodStart MUST be present in a FOCUS dataset, MUST be of type Date/Time, MUST be an *inclusive* value, and MUST NOT contain null values. +* ChargePeriodStart MUST match the beginning date and time boundary of the effective period of the charge. ## Column ID