Sl/sq fixes (#133)

* Various updates to pass SQ and compliance
CMSgov · Jul 21, 2021 · 82b82f2 · 82b82f2
1 parent 05e375e
commit 82b82f2
Show file tree

Hide file tree

Showing 6 changed files with 50 additions and 45 deletions.
diff --git a/_includes/build/bcda_v2.html b/_includes/build/bcda_v2.html
@@ -11,14 +11,14 @@ <h2>
     BCDA V2 supports the same functionality as V1 API endpoints in both the Sandbox and Production API environments. All V2 API endpoints should work as described in existing BCDA documentation. If you wish to transition your implementation to utilize BCDA V2 endpoints instead of V1, users simply need to replace ‘v1’ in API call URLs with ‘v2’. Here is an example:
 </p>
 <h3>
-    Obtaining an API Access Token in BCDA V1:
+    Sample cURL Command in BCDA V1:
 </h3>
 <pre><code>curl -X GET 'https://api.bcda.cms.gov/api/v1/Patient/$export' \
 -H "accept: application/fhir+json" \
 -H "Prefer: respond-async" \
 -H "Authorization: Bearer {access_token}"</code></pre>
 <h3>
-    Obtaining an API Access Token in BCDA V2:
+    Sample cURL Command in BCDA V2:
 </h3>
 <pre><code>curl -X GET 'https://api.bcda.cms.gov/api/v2/Patient/$export' \
 -H "accept: application/fhir+json" \

diff --git a/_includes/build/request_metadata.html b/_includes/build/request_metadata.html
@@ -4,6 +4,10 @@
 	Metadata about the Beneficiary Claims Data API is available as a FHIR CapabilityStatement resource. A token is not required to access this information.
 </p>
 
+<h2>
+  Metadata Examples
+</h2>
+
 <h3>
 	Metadata Request
 </h3>

diff --git a/_includes/data/bcda_v2_data.html b/_includes/data/bcda_v2_data.html
@@ -20,26 +20,26 @@ <h3>
 <p>
     For details, see the <a href="http://www.hl7.org/fhir/explanationofbenefit.html#resource" class="in-text__link">FHIR Explanation of Benefit resource</a> page, and select the "R3 Diff" tab under section 13.10.3 "Resource Content"
 </p>
-<table style="width:100%">
+<table style="width:100%" aria-describedby="EoB">
     <tr>
-        <th>Change Type</th>
-        <th>Description</th>
-        <th>Examples</th>
+        <th scope="col">Change Type</th>
+        <th scope="col">Description</th>
+        <th scope="col">Examples</th>
     </tr>
     <tr>
-        <td valign=top>Consolidated/Removed Elements</td>
-        <td valign=top>Some elements were consolidated and/or removed. For instance, in STU3 there were two elements (Eob.Organization and Eob.Provider) that could represent the party responsible for the claim.  In R4, this has been consolidated into one element (Eob.provider)</td>
-        <td class="cex" valign=top>
+        <td>Consolidated/Removed Elements</td>
+        <td>Some elements were consolidated and/or removed. For instance, in STU3 there were two elements (Eob.Organization and Eob.Provider) that could represent the party responsible for the claim.  In R4, this has been consolidated into one element (Eob.provider)</td>
+        <td class="cex">
             <ul>
                 <li>Eob.provider</li>
                 <li>Eob.hospitalization</li>
             </ul>
         </td>
     </tr>
     <tr>
-        <td valign=top>Added Constraints</td>
-        <td valign=top>Fifteen fields were changed from optional to mandatory.  Changing the optionality in this context generally has no impact on users consuming this data.   A few other minor constraints were added or modified (such as valueset bindings and reference targets)</td>
-        <td class="cex" valign=top>
+        <td>Added Constraints</td>
+        <td>Fifteen fields were changed from optional to mandatory.  Changing the optionality in this context generally has no impact on users consuming this data.   A few other minor constraints were added or modified (such as valueset bindings and reference targets)</td>
+        <td class="cex">
             <ul>
                 <li>Eob.use</li>
                 <li>Eob.patient</li>
@@ -49,9 +49,9 @@ <h3>
         </td>
     </tr>
     <tr>
-        <td valign=top>New Elements</td>
-        <td valign=top>Approximately 35 new elements were added to the EOB resource.  About 65% of these new elements are child elements of the .addItem property which is not supplied by the BCDA api.  Of the remaining 35%, very few, if any, of these elements are populated by BCDA.</td>
-        <td class="cex" valign=top>
+        <td>New Elements</td>
+        <td>Approximately 35 new elements were added to the EOB resource.  About 65% of these new elements are child elements of the .addItem property which is not supplied by the BCDA api.  Of the remaining 35%, very few, if any, of these elements are populated by BCDA.</td>
+        <td class="cex">
             <ul>
                 <li>Eob.priority</li>
                 <li>Eob.preAuthRef</li>
@@ -61,9 +61,9 @@ <h3>
         </td>
     </tr>
     <tr>
-        <td valign=top>Renamed Elements</td>
-        <td valign=top>A handful of elements were renamed.  For users converting from V1 (STU3) to V2 (R4), it is likely that existing parsing/handling logic must be adjusted.</td>
-        <td class="cex" valign=top>
+        <td>Renamed Elements</td>
+        <td>A handful of elements were renamed.  For users converting from V1 (STU3) to V2 (R4), it is likely that existing parsing/handling logic must be adjusted.</td>
+        <td class="cex">
             <ul>
                 <li>Eob.information → Eob.SupportingInfo</li>
                 <li>Eob.careTeamLinkId → Eob.careTeamSequence</li>
@@ -82,25 +82,25 @@ <h3>
 <p>
     For details, see the <a href="http://hl7.org/fhir/R4/patient.html#resource" class="in-text__link">FHIR Patient resource</a> page, and select the "R3 Diff" tab under section 8.1.2 "Resource Content"
 </p>
-<table style="width:100%">
+<table style="width:100%" aria-describedby="Patient">
     <tr>
-        <th>Change Type</th>
-        <th>Description</th>
-        <th>Examples</th>
+        <th scope="col">Change Type</th>
+        <th scope="col">Description</th>
+        <th scope="col">Examples</th>
     </tr>
     <tr>
-        <td valign=top>Consolidated/Removed Elements</td>
-        <td valign=top>Only one element was removed (Patient.animal) which has no effect on the BCDA api.</td>
-        <td class="cex" valign=top>
+        <td>Consolidated/Removed Elements</td>
+        <td>Only one element was removed (Patient.animal) which has no effect on the BCDA api.</td>
+        <td class="cex">
             <ul>
                 <li>Patient.animal</li>
             </ul>
         </td>
     </tr>
     <tr>
-        <td valign=top>Constraints</td>
-        <td valign=top>A handful of fields are bound to different valuesets.  Other minor changes to default value and reference target.</td>
-        <td class="cex" valign=top>
+        <td>Constraints</td>
+        <td>A handful of fields are bound to different valuesets.  Other minor changes to default value and reference target.</td>
+        <td class="cex">
             <ul>
                 <li>Patient.active</li>
                 <li>Patient.gender</li>
@@ -118,16 +118,16 @@ <h3>
 <p>
     For details, see the <a href="http://hl7.org/fhir/R4/coverage.html#resource" class="in-text__link">FHIR Coverage resource</a> page, and select the "R3 Diff" tab under section 13.10.3 "Resource Content"
 </p>
-<table style="width:100%">
+<table style="width:100%" aria-describedby="Coverage">
     <tr>
-        <th>Change Type</th>
-        <th>Description</th>
-        <th>Examples</th>
+        <th scope="col">Change Type</th>
+        <th scope="col">Description</th>
+        <th scope="col">Examples</th>
     </tr>
     <tr>
-        <td valign=top>New Elements</td>
-        <td valign=top>Six new elements were added to the Coverage resource.  Most of the new elements relate to costToBeneficiary and will not be supplied in BCDA.</td>
-        <td class="cex" valign=top>
+        <td>New Elements</td>
+        <td>Six new elements were added to the Coverage resource.  Most of the new elements relate to costToBeneficiary and will not be supplied in BCDA.</td>
+        <td class="cex">
             <ul>
                 <li>Coverage.class.name</li>
                 <li>Coverage.costToBeneficiary</li>
@@ -136,18 +136,18 @@ <h3>
         </td>
     </tr>
     <tr>
-        <td valign=top>Consolidated/Removed Elements</td>
-        <td valign=top>The Coverage.grouping element was removed.  The equivalent element in R4 is Coverage.class.  This element is provided in the API, so any user converting from V1 to V2 will be required to make minor changes to their parsing/handling logic.</td>
-        <td class="cex" valign=top>
+        <td>Consolidated/Removed Elements</td>
+        <td>The Coverage.grouping element was removed.  The equivalent element in R4 is Coverage.class.  This element is provided in the API, so any user converting from V1 to V2 will be required to make minor changes to their parsing/handling logic.</td>
+        <td class="cex">
             <ul>
                 <li>Coverage.grouping</li>
             </ul>
         </td>
     </tr>
     <tr>
-        <td valign=top>Added Constraints</td>
-        <td valign=top>A few changes to make certain elements mandatory.  Generally this has little or no impact to any users consuming this data.</td>
-        <td class="cex" valign=top>
+        <td>Added Constraints</td>
+        <td>A few changes to make certain elements mandatory.  Generally this has little or no impact to any users consuming this data.</td>
+        <td class="cex">
             <ul>
                 <li>Coverage.beneficiary</li>
                 <li>Coverage.payor</li>

diff --git a/_includes/guide/bcda_v2.html b/_includes/guide/bcda_v2.html
@@ -12,14 +12,14 @@ <h2>
     BCDA V2 supports the same functionality as V1 API endpoints in both the Sandbox and Production API environments. All V2 API endpoints should work as described in existing BCDA documentation. If you wish to transition your implementation to utilize BCDA V2 endpoints instead of V1, users simply need to replace ‘v1’ in API call URLs with ‘v2’. Here is an example:
 </p>
 <h3>
-    Obtaining an API Access Token in BCDA V1:
+    Sample cURL Command in BCDA V1:
 </h3>
 <pre><code>curl -X GET 'https://sandbox.bcda.cms.gov/api/v1/Patient/$export' \
 -H "accept: application/fhir+json" \
 -H "Prefer: respond-async" \
 -H "Authorization: Bearer {access_token}"</code></pre>
 <h3>
-    Obtaining an API Access Token in BCDA V2:
+    Sample cURL Command in BCDA V2:
 </h3>
 <pre><code>curl -X GET 'https://sandbox.bcda.cms.gov/api/v2/Patient/$export' \
 -H "accept: application/fhir+json" \

diff --git a/assets/css/static-main.scss b/assets/css/static-main.scss
@@ -272,6 +272,7 @@ table, th, td {
 th, td {
     padding: 15px;
     text-align: left;
+    vertical-align: top;
 }
 
 th { background-color: #D3D3D3; }

diff --git a/build.html b/build.html
@@ -145,9 +145,9 @@ <h1>
           </div>
         </div>
         <div id="request-metadata">
-          <h2>
+          <h1>
             Request Metadata
-          </h2>
+          </h1>
           <div class="ds-u-font-size--base">
             {% include build/request_metadata.html %}
           </div>