Resolve findings (#160)

Co-authored-by: Ian Sawyer <isawyer@fearless.tech>

_includes/build/access_token.html

@@ -2,18 +2,18 @@
 	Currently, access tokens expire after twenty minutes. To illustrate this cycle, we’ll use the published open sandbox credentials for Extra-Small Model Entities.
 </p>
 
-<pre><code><b>Example Client ID (Extra-Small Model Entities):</b>
+<pre><code><strong>Example Client ID (Extra-Small Model Entities):</strong>
 3841c594-a8c0-41e5-98cc-38bb45360d3c
 
-<b>Example Client Secret (Extra-Small Model Entities):</b>
+<strong>Example Client Secret (Extra-Small Model Entities):</strong>
 d89810016460e6924a1c62583e5f51d1cbf911366c6bc6f040ff9f620a944efbf2b7264afe071609
 </code></pre>
 
 <div class="ds-c-alert ds-c-alert--hide-icon">
     <div class="ds-c-alert__body">
       <h3 class="ds-c-alert__heading">These credentials do not work in production.</h3>
       <p class="ds-c-alert__text">
-	The sample credentials above will <b>not</b> work in the production environment. For production data, follow along using the credentials your model entity was issued.
+	The sample credentials above will <strong>not</strong> work in the production environment. For production data, follow along using the credentials your model entity was issued.
 	</div>
   </div>
 

_includes/build/bcda_v2.html

@@ -12,7 +12,7 @@ <h2>
 </p>
 <p>
     <div style="overflow-x:auto;">
-        <table>
+        <table aria-label="Example Curl commands">
             <tr>
                 <th>Sample cURL Command in BCDA V1:</th>
                 <th>Sample cURL Command in BCDA V2:</th>

_includes/build/requesting_data_all_three.html

@@ -146,9 +146,9 @@ <h4>cURL Command to download the data</h4>
 <h4>Response Example</h4>
 	<p>
 	<ol>
-	    <li><b><a href="https://bcda.cms.gov/assets/data/ExplanationOfBenefit.ndjson" target="_blank" rel="noopener" class="in-text__link"> Explanation of Benefit</a></b></li>
-	    <li><b><a href="https://bcda.cms.gov/assets/data/Patient.ndjson" target="_blank" rel="noopener" class="in-text__link"> Patient</a></b></li>
-	    <li><b><a href="https://bcda.cms.gov/assets/data/Coverage.ndjson" target="_blank" rel="noopener" class="in-text__link"> Coverage</a></b></li>
+	    <li><strong><a href="https://bcda.cms.gov/assets/data/ExplanationOfBenefit.ndjson" target="_blank" rel="noopener" class="in-text__link"> Explanation of Benefit</a></strong></li>
+	    <li><strong><a href="https://bcda.cms.gov/assets/data/Patient.ndjson" target="_blank" rel="noopener" class="in-text__link"> Patient</a></strong></li>
+	    <li><strong><a href="https://bcda.cms.gov/assets/data/Coverage.ndjson" target="_blank" rel="noopener" class="in-text__link"> Coverage</a></strong></li>
 	  </ol>
 	</p>
 

_includes/data/bcda_v2_data.html

@@ -19,7 +19,7 @@ <h3>
     The following table summarizes changes to the EOB resource due to changes between versions 3 (STU3) and 4 (R4) of the FHIR specification.
 </p>
 <p>
-    For details, see the <a href="http://www.hl7.org/fhir/explanationofbenefit.html#resource" target="_blank" class="in-text__link">FHIR Explanation of Benefit resource</a> page, and select the <b>R3 Diff</b> tab under section <b>13.10.4 Resource Content</b>
+    For details, see the <a href="http://www.hl7.org/fhir/explanationofbenefit.html#resource" target="_blank" class="in-text__link">FHIR Explanation of Benefit resource</a> page, and select the <strong>R3 Diff</strong> tab under section <strong>13.10.4 Resource Content</strong>
 </p>
 <table style="width:100%" aria-describedby="EoB">
     <tr>
@@ -81,7 +81,7 @@ <h3>
     The following table summarizes changes to the Patient Resource due to changes between versions 3 (STU3) and 4 (R4) of the FHIR specification.  The Patient Resource is normative, with a maturity level of 5.  In other words, because this resource has been in a mature state for quite some time, the amount of change to this resource in R4 is minimal.
 </p>
 <p>
-    For details, see the <a href="http://hl7.org/fhir/R4/patient.html#resource" target="_blank" class="in-text__link">FHIR Patient resource</a> page, and select the <b>R3 Diff</b> tab under section <b>8.1.2 Resource Content</b>
+    For details, see the <a href="http://hl7.org/fhir/R4/patient.html#resource" target="_blank" class="in-text__link">FHIR Patient resource</a> page, and select the <strong>R3 Diff</strong> tab under section <strong>8.1.2 Resource Content</strong>
 </p>
 <table style="width:100%" aria-describedby="Patient">
     <tr>
@@ -117,7 +117,7 @@ <h3>
     The following table summarizes changes to the Coverage Resource due to changes between versions 3 (STU3) and 4 (R4) of the FHIR specification. 
 </p>
 <p>
-    For details, see the <a href="http://hl7.org/fhir/R4/coverage.html#resource" target="_blank" class="in-text__link">FHIR Coverage resource</a> page, and select the <b>R3 Diff</b> tab under section <b>13.1.3 Resource Content</b>
+    For details, see the <a href="http://hl7.org/fhir/R4/coverage.html#resource" target="_blank" class="in-text__link">FHIR Coverage resource</a> page, and select the <strong>R3 Diff</strong> tab under section <strong>13.1.3 Resource Content</strong>
 </p>
 <table style="width:100%" aria-describedby="Coverage">
     <tr>

_includes/data/data_dictionary.html

@@ -3,7 +3,7 @@
     BCDA provides <a href="/assets/data/BCDA_Data_Dictionary_2022_01_31.xlsx" target="blank" class="in-text__link">CCLF to BCDA Data Dictionary</a> to customers to facilitate their data mapping process.
   </p>
   <p>
-    <b> The Data Dictionary was last updated in January 2022. </b>
+    <strong> The Data Dictionary was last updated in January 2022. </strong>
   </p>
   <p>
     Because BCDA delivers data in the FHIR format, data field names will be different from data fields delivered through CCLF files. In this spreadsheet, BCDA has provided a crosswalk between all CCLF data fields and their new locations within BCDA claims files. The BCDA Data Dictionary also provides supplementary context for each of the CCLF/BCDA data fields, including:

_includes/data/how_to_use_bcda_data.html

@@ -4,16 +4,16 @@
   <p>BCDA serves data according to the bulk FHIR specification using three FHIR resources: ExplanationOfBenefit (EOB), Patient, and Coverage. This means that your claims data will be delivered through three FHIR resource types rather than 12 CCLF files.
   </p>
   <ul>
-    <li> The <b>ExplanationOfBenefit (EOB)</b> resource type provides similar information to what is provided in CCLF files 1-7. The EOB files contain lines within an episode of care, including where and when the service was performed, the diagnosis codes, the provider who performed the service, and the cost of care.</li>
-    <li>The <b>Patient</b> resource type provides similar information to what is provided in CCLF files 8 and 9. This is where you get your information about who your beneficiaries are, their demographic information, and updates to their patient identifiers.</li>
-    <li>The <b>Coverage</b> resource type provides information about beneficiaries’ insurance coverage, including information about dual coverage.</li>
+    <li> The <strong>ExplanationOfBenefit (EOB)</strong> resource type provides similar information to what is provided in CCLF files 1-7. The EOB files contain lines within an episode of care, including where and when the service was performed, the diagnosis codes, the provider who performed the service, and the cost of care.</li>
+    <li>The <strong>Patient</strong> resource type provides similar information to what is provided in CCLF files 8 and 9. This is where you get your information about who your beneficiaries are, their demographic information, and updates to their patient identifiers.</li>
+    <li>The <strong>Coverage</strong> resource type provides information about beneficiaries’ insurance coverage, including information about dual coverage.</li>
   </ul>
   <div class="ds-c-alert ds-c-alert--hide-icon">
     <div class="ds-c-alert__body">
       <h2 class="ds-c-alert__heading">Confidentiality and Medical Data Sharing</h2>
       <p class="ds-c-alert__text">
-        In accordance with applicable law, including HIPAA and the regulations in 42 CFR Part 2, a beneficiary’s substance use disorder records are confidential. For example, claims data related to alcohol and drug abuse treatment are <b>not</b> shared.</p>
-        <p class="ds-c-alert__text">In addition, BCDA will not share <b>any</b> data of beneficiaries who have opted out of data sharing.</p>  
+        In accordance with applicable law, including HIPAA and the regulations in 42 CFR Part 2, a beneficiary’s substance use disorder records are confidential. For example, claims data related to alcohol and drug abuse treatment are <strong>not</strong> shared.</p>
+        <p class="ds-c-alert__text">In addition, BCDA will not share <strong>any</strong> data of beneficiaries who have opted out of data sharing.</p>  
 
     </div>
   </div>

_includes/data/sample_files.html

@@ -1,6 +1,6 @@
 <p>In order to aid in customers' understanding of BCDA file data and structure, BCDA provides sample ExplanationOfBenefit, Patient, and Coverage FHIR Resource files to download. These files contain synthetic data, but the structure and contents of the files are similar to the actual files you will be pulling and downloading from the BCDA Production Environment. These files contain data for 100 synthetic beneficiaries. Please visit the <a href="/guide.html" class="in-text__link">Getting Started</a> page for a more in-depth look at the synthetic data options available to you through the BCDA Sandbox Environment.</p>
   <ol>
-    <li><b><a href="https://bcda.cms.gov/assets/data/ExplanationOfBenefit.ndjson" target="_blank" rel="noopener" class="in-text__link">Explanation of Benefit</a></b></li>
-    <li><b><a href="https://bcda.cms.gov/assets/data/Patient.ndjson" target="_blank" rel="noopener" class="in-text__link">Patient</a></b></li>
-    <li><b><a href="https://bcda.cms.gov/assets/data/Coverage.ndjson" target="_blank" rel="noopener" class="in-text__link">Coverage</a></b></li>
+    <li><strong><a href="https://bcda.cms.gov/assets/data/ExplanationOfBenefit.ndjson" target="_blank" rel="noopener" class="in-text__link">Explanation of Benefit</a></strong></li>
+    <li><strong><a href="https://bcda.cms.gov/assets/data/Patient.ndjson" target="_blank" rel="noopener" class="in-text__link">Patient</a></strong></li>
+    <li><strong><a href="https://bcda.cms.gov/assets/data/Coverage.ndjson" target="_blank" rel="noopener" class="in-text__link">Coverage</a></strong></li>
   </ol>

_includes/guide/bcda_v2.html

@@ -13,7 +13,7 @@ <h2>
 </p>
 <p>
 <div style="overflow-x:auto;">    
-    <table>
+    <table aria-label="Example Curl commands">
         <tr>
             <th>Sample cURL Command in BCDA V1:</th>
             <th>Sample cURL Command in BCDA V2:</th>

_includes/guide/sandbox_environment.html

@@ -1,5 +1,5 @@
 <p>
-	In the sandbox environment, we provide generic credentials for you to use. We have provided five sets of synthetic credentials for use in the sandbox, corresponding to various amounts of synthetic beneficiaries. These will <b>not</b> work in the production environment. We suggest testing with the credentials that most closely align with the size of your  model entity, so that you can experiment working with a similar amount of synthetic data to that which you’ll receive in production.
+	In the sandbox environment, we provide generic credentials for you to use. We have provided five sets of synthetic credentials for use in the sandbox, corresponding to various amounts of synthetic beneficiaries. These will <strong>not</strong> work in the production environment. We suggest testing with the credentials that most closely align with the size of your  model entity, so that you can experiment working with a similar amount of synthetic data to that which you’ll receive in production.
 </p>
 
 <p>

_includes/guide/try_the_api.html

@@ -188,9 +188,9 @@ <h4>
 </h4>
 <p>
 	<ol>
-		<li><b><a href="https://bcda.cms.gov/assets/data/ExplanationOfBenefit.ndjson" target="_blank" rel="noopener" class="in-text__link"> Explanation of Benefit</a></b></li>
-		<li><b><a href="https://bcda.cms.gov/assets/data/Patient.ndjson" target="_blank" rel="noopener" class="in-text__link"> Patient</a></b></li>
-		<li><b><a href="https://bcda.cms.gov/assets/data/Coverage.ndjson" target="_blank" rel="noopener" class="in-text__link"> Coverage</a></b></li>
+		<li><strong><a href="https://bcda.cms.gov/assets/data/ExplanationOfBenefit.ndjson" target="_blank" rel="noopener" class="in-text__link"> Explanation of Benefit</a></strong></li>
+		<li><strong><a href="https://bcda.cms.gov/assets/data/Patient.ndjson" target="_blank" rel="noopener" class="in-text__link"> Patient</a></strong></li>
+		<li><strong><a href="https://bcda.cms.gov/assets/data/Coverage.ndjson" target="_blank" rel="noopener" class="in-text__link"> Coverage</a></strong></li>
 	</ol>
 </p>
 

_updates/2020-12-29.html

@@ -18,7 +18,7 @@
       Between December and January, ACOs go through a change in their participant lists and related beneficiary assignment as part of the transition between performance years. BCDA has a delay in receiving the updated beneficiary list in January, so BCDA has been working to ensure that we only return appropriate claims data. Last year, BCDA had to be turned off to address this delay; this year, BCDA is releasing new capabilities to maintain its uptime year-round.
     </p>
     <p>
-      BCDA is introducing a new identifier in the /Group endpoint, called `runout`. Between December 2020 and mid-January 2021, this identifier will only return claims with a service date before December 31, 2020. <b>Until BCDA receives January 2021 attribution information, the only way to retrieve claims is to use the group ID `runout` with the /Group endpoint; requests to /Patient or /Group with other group IDs will fail.</b> After BCDA receives January 2021 attribution information, this same `runout` identifier will also be available for ACOs to receive claims runout information from 2020.
+      BCDA is introducing a new identifier in the /Group endpoint, called `runout`. Between December 2020 and mid-January 2021, this identifier will only return claims with a service date before December 31, 2020. <strong>Until BCDA receives January 2021 attribution information, the only way to retrieve claims is to use the group ID `runout` with the /Group endpoint; requests to /Patient or /Group with other group IDs will fail.</strong> After BCDA receives January 2021 attribution information, this same `runout` identifier will also be available for ACOs to receive claims runout information from 2020.
    </p>
    <p>
      Full details about how to implement these changes are available in the <a href="/build.html#requesting-data-EOY" class="in-text__link">End of Year Requests section on the Building Your API page</a>.