fix footer and earliest date to jan 1, 2020

CMSgov · Feb 19, 2025 · 39e2706 · 39e2706
1 parent b939ffb
commit 39e2706
Show file tree

Hide file tree

Showing 6 changed files with 32 additions and 32 deletions.
diff --git a/_data/footer-links.yml b/_data/footer-links.yml
@@ -1,10 +1,10 @@
 - heading: Getting Started
   links:
 
-    - text: Access sandbox data
+    - text: Access Sandbox Data
       url: /access-sandbox-data
 
-    - text: Access production claims data
+    - text: Access Production Claims Data
       url: /access-production-claims-data
 
 - heading: AB2D Data
@@ -18,7 +18,7 @@
       url: /assets/downloads/ab2d-data-dictionary.xlsx
       icon: file_download
 
-    - text: Claims data details
+    - text: Claims Data Details
       url: /claims-data-details
 
     - text: FHIR specification
@@ -30,7 +30,7 @@
     - text: Permitted uses
       url: /about
 
-    - text: Use cases
+    - text: Use Cases
       url: /use-cases
 
 - heading: Support

diff --git a/_pages/claims-data-details.md b/_pages/claims-data-details.md
@@ -436,7 +436,7 @@ In the example, a single claim will be tracked through several evolutions:
           </tr>
           <tr>
               <td data-label="Claim update">Update 3</td>
-              <td data-label="Details">An update to Claim 99995 (removal of claim line item) is received by AB2D on March 20, 2020.</td>
+              <td data-label="Details">An update to Claim 99995 (removal of claim line item) is received by AB2D on March 31, 2020.</td>
           </tr>
       </tbody>
   </table>
@@ -458,7 +458,7 @@ In the example, 4 exports are run using the <a href="{{ '/query-parameters-v2' |
           <tr>
               <td data-label="Export">Export 1</td>
               <td data-label="Run On">January 31, 2020</td>
-              <td data-label="Since">December 31, 2019</td>
+              <td data-label="Since">January 1, 2020</td>
               <td data-label="Description">Provide all claims information and updates received in January</td>
           </tr>
           <tr>
@@ -483,13 +483,13 @@ In the example, 4 exports are run using the <a href="{{ '/query-parameters-v2' |
   </table>
 </div>
 
-The dates used in this example are just random dates. Organizations cannot pull data before February 13, 2020 or their date of attestation (whichever is later).
+The dates used in this example are just random dates. Organizations cannot pull data before January 1, 2020 or their date of attestation (whichever is later).
 
 ### Updated claims scenario - export details
 
-#### Export 1 12/31/2019 - 01/31/2020
+#### Export 1 01/01/2020 - 01/31/2020
 
-On January 31, 2020, organization XYZ runs its first export. The export uses a _since parameter date of December 31, 2019. The _since date tells AB2D to report all claims information received between December 31, 2019 and January 31, 2020.
+On January 31, 2020, organization XYZ runs its first export. The export uses a _since parameter date of January 1, 2020. The _since date tells AB2D to report all claims information received between January 1, 2020 and January 31, 2020.
 
 The export pulls a claim version with Claim Group ID 99995. At this time, the only version of the claim available to AB2D is 12987987. This version (claim update 1) is the latest claim version available as it is marked active.
 
@@ -772,7 +772,7 @@ In the example, a single claim will be tracked through several evolutions:
           </tr>
           <tr>
               <td data-label="Claim update">Update 2</td>
-              <td data-label="Details">An update to Claim 99995 is received by AB2D on February 28, 2020.</td>
+              <td data-label="Details">An update to Claim 99995 is received by AB2D on February 10, 2020.</td>
           </tr>
       </tbody>
   </table>
@@ -792,7 +792,7 @@ In the example, a single claim will be tracked through several evolutions:
           <tr>
               <td data-label="Export">Export 1</td>
               <td data-label="Run On">January 31, 2020</td>
-              <td data-label="Since">December 31, 2019</td>
+              <td data-label="Since">January 1, 2020</td>
               <td data-label="Description">Provide all claims information and updates received in January</td>
           </tr>
           <tr>
@@ -805,13 +805,13 @@ In the example, a single claim will be tracked through several evolutions:
   </table>
 </div>
 
-The dates used in this example are just random dates. Organizations cannot pull data before February 13, 2020 or their date of attestation (whichever is later).
+The dates used in this example are just random dates. Organizations cannot pull data before January 1, 2020 or their date of attestation (whichever is later).
 
 ### Canceled claims scenario - export details
 
-#### Export 1 12/31/2019 - 01/31/2020
+#### Export 1 01/01/2020 - 01/31/2020
 
-On January 31, 2020, organization XYZ runs its first export. The export uses a _since parameter date of December 31, 2019. The _since date tells AB2D to report all claims information received between December 31, 2019 and January 31, 2020.
+On January 31, 2020, organization XYZ runs its first export. The export uses a _since parameter date of January 1, 2020. The _since date tells AB2D to report all claims information received between January 1, 2020 and January 31, 2020.
 
 The export pulls a claim version with Claim Group ID 99995. At this time, the only version of the claim available to AB2D is 12987987. This version (claim update 1) is the latest claim version available as it is marked active.
 
@@ -989,26 +989,26 @@ In the example, 2 exports are run using the _since parameter. These exports are
           <tr>
               <td data-label="Export">Export 1</td>
               <td data-label="Run On">January 31, 2020</td>
-              <td data-label="Since">December 31, 2019</td>
+              <td data-label="Since">January 1, 2020</td>
               <td data-label="Description">Provide all claims information and updates received in January</td>
           </tr>
           <tr>
               <td data-label="Export">Export 2</td>
               <td data-label="Run On">February 28, 2020</td>
-              <td data-label="Since">December 31, 2019</td>
+              <td data-label="Since">January 1, 2020</td>
               <td data-label="Description">Provide all claims information and updates received in January and February</td>
           </tr>
       </tbody>
   </table>
 </div>
 
-The dates used in this example are just random dates. Organizations cannot pull data before February 13, 2020 or their date of attestation (whichever is later).
+The dates used in this example are just random dates. Organizations cannot pull data before January 1, 2020 or their date of attestation (whichever is later).
 
 ### Duplicate claims scenario - export details
 
-#### Export 1 12/31/2019 - 01/31/2020
+#### Export 1 01/01/2020 - 01/31/2020
 
-On January 31, 2020, organization XYZ runs its first export. The export uses a _since parameter date of December 31, 2019. The _since date tells AB2D to report all claims information received between December 31, 2019 and January 31, 2020.
+On January 31, 2020, organization XYZ runs its first export. The export uses a _since parameter date of January 1, 2020. The _since date tells AB2D to report all claims information received between January 1, 2020 and January 31, 2020.
 
 The export pulls a claim version with Claim Group ID 99995. At this time the only version of the claim available to AB2D is 12987987. This version is the latest claim version available as it is marked active.
 
@@ -1057,9 +1057,9 @@ The export pulls a claim version with Claim Group ID 99995. At this time the onl
   </table>
 </div>
 
-#### Export 2 12/31/2019 - 02/28/2020
+#### Export 2 01/01/2020 - 02/28/2020
 
-On February 28, 2020, organization XYZ runs an export with a _since parameter date of December 31, 2019. The _since date tells AB2D to report all claims information received between December 31, 2019 and February 28, 2020.
+On February 28, 2020, organization XYZ runs an export with a _since parameter date of January 1, 2020. The _since date tells AB2D to report all claims information received between January 1, 2020 and February 28, 2020.
 
 The export pulls a duplicate of the claim from export 1 as it has the same Claim Group ID (99995), Claim ID (12987987), and Last Updated date (01/01/2020). 
 

diff --git a/_pages/filter-claims-data-v1.md b/_pages/filter-claims-data-v1.md
@@ -32,7 +32,7 @@ Learn how to access [sandbox data]({{ '/access-sandbox-data' | relative_url }})
 
 <p> The _since parameter allows users to filter claims data returned by date, which reduces duplication and speeds up job times. It follows the <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank" rel="noopener">ISO datetime format</a> (yyyy-mm-dd'T'hh:mm:ss[+|-]hh:mm). The time zone must be specified using + or - followed by hh:mm.</p>
 
-The \_since parameter allows users to pull data that has been last updated since a specified date. The earliest possible date is February 13, 2020 (2020-02-13T00:00:00-05:00) or your organization's attestation date, whichever is later. If no \_since date is specified, it will default to your earliest possible date. It is highly recommended and considered best practice to use the \_since parameter on V1 API calls.
+The \_since parameter allows users to pull data that has been last updated since a specified date. The earliest possible date is January 1, 2020 (2020-01-01T00:00:00-05:00) or your organization's attestation date, whichever is later. If no \_since date is specified, it will default to your earliest possible date. It is highly recommended and considered best practice to use the \_since parameter on V1 API calls.
 
 The \_until parameter filters for claims data last updated after a specified date. This parameter is only available with V2 [(FHIR R4)](https://api.ab2d.cms.gov/api/v2/fhir), the current and recommended version of the API.
 
@@ -48,9 +48,9 @@ The \_until parameter filters for claims data last updated after a specified dat
     </thead>
     <tbody>
         <tr>
-            <td data-label="_since">2020-02-01T00:00:00.000+00:00</td>
+            <td data-label="_since">2019-12-30T00:00:00.000+00:00</td>
             <td data-label="Is it valid?">No</td>
-            <td data-label="Why?">The datetime is before February 13, 2020. The job will still run, but the value will be replaced with your earliest possible date.</td>
+            <td data-label="Why?">The datetime is before January 1, 2020. The job will still run, but the value will be replaced with your earliest possible date.</td>
         </tr>
         <tr>
             <td data-label="_since">2020-10-10T00:00:00.000</td>
@@ -60,12 +60,12 @@ The \_until parameter filters for claims data last updated after a specified dat
         <tr>
             <td data-label="_since">2020-10-10T16:00:00.000+10:00</td>
             <td data-label="Is it valid?">Yes</td>
-            <td data-label="Why?">The datetime is after February 13, 2020 and follows the ISO format.</td>
+            <td data-label="Why?">The datetime is after January 1, 2020 and follows the ISO format.</td>
         </tr>
         <tr>
             <td data-label="_since">2020-10-10T16:00:00.000-10:00</td>
             <td data-label="Is it valid?">Yes</td>
-            <td data-label="Why?">The datetime is after February 13, 2020 and follows the ISO format.</td>
+            <td data-label="Why?">The datetime is after January 1, 2020 and follows the ISO format.</td>
         </tr>
     </tbody>
 </table>

diff --git a/_pages/production-access.md b/_pages/production-access.md
@@ -112,7 +112,7 @@ Only active, stand-alone Prescription Drug Plan (PDP) sponsors can access enroll
     <span>and</span>
     <span class="usa-tag">Completed by AB2D Data Ops Specialist</span>
     <p>
-      The Attestor will receive an email with production credentials to share with their ADOS.  Production credentials are Personally Identifiable Information (PII) that allow the ADOS to <a href="{{ '/get-a-bearer-token' | relative_url }}">get a bearer token</a> and <a href="{{ '/access-production-claims-data' | relative_url }}">access production claims data</a>.
+      The Attestor will receive an email with details on production credentials to share with their ADOS.  Production credentials are Personally Identifiable Information (PII) that allow the ADOS to <a href="{{ '/get-a-bearer-token' | relative_url }}">get a bearer token</a> and <a href="{{ '/access-production-claims-data' | relative_url }}">access production claims data</a>.
     </p>
     <p>
       If you have questions or need help, visit <a href="{{ '/support' | relative_url }}">Support</a> or contact the AB2D team at <a href="mailto:[email protected]">[email protected]</a>.

diff --git a/_pages/query-parameters-v2.md b/_pages/query-parameters-v2.md
@@ -36,7 +36,7 @@ Separately, these parameters allow you to pull data that was last updated since
 
 ### For _since
 
-The earliest possible date is February 13, 2020 (2020-02-13T00:00:00-05:00) or your organization's attestation date, whichever is later. If no _since date is specified, it will default to the datetime of your organization’s last successful export. If this is your first job, it will default to your earliest possible date. 
+The earliest possible date is January 1, 2020 (2020-01-01T00:00:00-05:00) or your organization's attestation date, whichever is later. If no _since date is specified, it will default to the datetime of your organization’s last successful export. If this is your first job, it will default to your earliest possible date. 
 
 ### For _until
 
@@ -94,10 +94,10 @@ Together, the _since and _until parameters allow you to pull data that was last
             <td data-label="Why?">A time zone must be provided with the datetime.</td>
         </tr>
         <tr>
-            <td data-label="_since datetime">2020-02-01T00:00:00+00:00</td>
-            <td data-label="_until datetime">2020-02-28T00:00:00+00:00</td>
+            <td data-label="_since datetime">2019-12-30T00:00:00+00:00</td>
+            <td data-label="_until datetime">2020-01-14T00:00:00+00:00</td>
             <td data-label="Is it valid?">No</td>
-            <td data-label="Why?">The _since datetime is before February 13, 2020. The job will still run, but the datetime will be replaced with the default.</td>
+            <td data-label="Why?">The _since datetime is before January 1, 2020. The job will still run, but the datetime will be replaced with the default.</td>
         </tr>
         <tr>
             <td data-label="_since datetime">2020-10-10T16:00:00+00:00</td>

diff --git a/_pages/troubleshooting-guide.md b/_pages/troubleshooting-guide.md
@@ -216,7 +216,7 @@ If the system is correct, check with your IT team to make sure you have a static
   The default value for the _since parameter changes between versions. The _until parameter is also only available with V2.
 </p>
 <p>
-  In V1, a date must be specified to use _since. If no _since value is specified, it will default to February 13, 2020 or your organization's attestation date, whichever is later. In V2, if no _since value is specified, it will default to the date of your last successful export. If this is your first job, it will default to the same date as V1. <a href="{{ '/query-parameters-V2' | relative_url }}">Learn how to use parameters</a>.
+  In V1, a date must be specified to use _since. If no _since value is specified, it will default to January 1, 2020 or your organization's attestation date, whichever is later. In V2, if no _since value is specified, it will default to the date of your last successful export. If this is your first job, it will default to the same date as V1. <a href="{{ '/query-parameters-V2' | relative_url }}">Learn how to use parameters</a>.
 </p>
 {% endcapture %}