Fix internal links adding.html extension

Author: jhutchison-nava

src/_pages/api-documentation.md

@@ -17,22 +17,22 @@ This documentation shows you how to connect to synthetic data in the <a href="ht
     <p class="usa-process-list__heading">Sign up for the DPC Sandbox</p>
     <ol style="margin-top: 1rem;">
       <li>Request access to the DPC Sandbox. </li>
-      <li>Follow the steps to get <a href="{{ '/api-documentation/get-sandbox-credentials' | relative_url }}">DPC Sandbox credentials</a></li>
+      <li>Follow the steps to get <a href="{{ '/api-documentation/get-sandbox-credentials.html' | relative_url }}">DPC Sandbox credentials</a></li>
     </ol>
   </li>
   <li class="usa-process-list__item docs-final-item">
     <p class="usa-process-list__heading">Use the sandbox</p>
     <div class="usa-alert usa-alert--info usa-alert--slim margin-top-2">
       <div class="usa-alert__body">
         <p class="usa-alert__text">
-          DPC also offers a <a href="{{ '/api-documentation/postman-collection' | relative_url }}">Postman collection</a> with sample requests to public endpoints.
+          DPC also offers a <a href="{{ '/api-documentation/postman-collection.html' | relative_url }}">Postman collection</a> with sample requests to public endpoints.
         </p>
       </div>
     </div>
     <ol style="margin-top: 1rem;">
-      <li>Get an <a href="{{ '/api-documentation/get-access-token' | relative_url }}">access token</a>.</li>
-      <li>Complete <a href="{{ '/api-documentation/attribution' | relative_url }}">attribution</a> by creating patient rosters.</li>
-      <li>Initiate a job to <a href="{{ '/api-documentation/export-data' | relative_url }}">export data</a>. </li>
+      <li>Get an <a href="{{ '/api-documentation/get-access-token.html' | relative_url }}">access token</a>.</li>
+      <li>Complete <a href="{{ '/api-documentation/attribution.html' | relative_url }}">attribution</a> by creating patient rosters.</li>
+      <li>Initiate a job to <a href="{{ '/api-documentation/export-data.html' | relative_url }}">export data</a>. </li>
     </ol>
   </li>
 </ol>

src/_pages/api-documentation/attribution.md

@@ -12,12 +12,12 @@ Before accessing patient data, DPC must establish that you have a valid patient-
 
 DPC provides you with a bundle of [sample practitioners](https://github.com/CMSgov/dpc-app/blob/main/dpc-web/public/practitioner_bundle.json){:target="_blank"} and [sample patients](https://github.com/CMSgov/dpc-app/blob/main/dpc-web/public/patient_bundle.json){:target="_blank"} to complete attribution in the DPC Sandbox.
 
-1. [Upload practitioners]({{ "/api-documentation/attribution/upload-practitioners" | relative_url }}) in your organization.  
-2. [Upload patients]({{ "/api-documentation/attribution/upload-patients" | relative_url }}) in your care.  
-3. Attribute patients to their practitioners by [creating a group]({{ "/api-documentation/attribution/attestation#create-a-patient-group-resource" | relative_url }}) in the Attestation stage.
+1. [Upload practitioners]({{ "/api-documentation/attribution/upload-practitioners.html" | relative_url }}) in your organization.  
+2. [Upload patients]({{ "/api-documentation/attribution/upload-patients.html" | relative_url }}) in your care.  
+3. Attribute patients to their practitioners by [creating a group]({{ "/api-documentation/attribution/attestation.html#create-a-patient-group-resource" | relative_url }}) in the Attestation stage.
 
 ## Attestation
 
-You'll need to submit an [Attestation]({{ "/api-documentation/attribution/attestation" | relative_url }}) each time you attribute a patient to a provider group. 
+You'll need to submit an [Attestation]({{ "/api-documentation/attribution/attestation.html" | relative_url }}) each time you attribute a patient to a provider group. 
 
 {% include alert.html variant="warning" text="The DPC sandbox does not preload any test data." classNames="measure-6" %}

src/_pages/api-documentation/attribution/attestation.md

@@ -74,7 +74,7 @@ Find your Practitioner ID by referencing the {id} variable in the resource objec
 
 ## Create a patient Group Resource 
 
-You'll need to create a Group Resource to link a list of registered [patients]({{ "/api-documentation/attribution/upload-patients" | relative_url }}) to a registered [practitioner]({{ "/api-documentation/attribution/upload-practitioners" | relative_url }}). 
+You'll need to create a Group Resource to link a list of registered [patients]({{ "/api-documentation/attribution/upload-patients.html" | relative_url }}) to a registered [practitioner]({{ "/api-documentation/attribution/upload-practitioners.html" | relative_url }}). 
 
 **Group Resource requirements**
 
@@ -404,7 +404,7 @@ You can only pull data for one practitioner’s patient group at a time. Do this
 
 The response will return a [Bundle](https://www.hl7.org/fhir/STU3/bundle.html) Resource which contains attribution Groups for the given practitioner. 
 
-You can use the Group ID value of the returned resources to [initiate an export job]({{ "/api-documentation/export-data#initiate-an-export-job" | relative_url }}). Find your Group ID by referencing the `id` variable in your group’s resource object.
+You can use the Group ID value of the returned resources to [initiate an export job]({{ "/api-documentation/export-data.html#initiate-an-export-job" | relative_url }}). Find your Group ID by referencing the `id` variable in your group’s resource object.
 
 ### Example Group Resource
 

src/_pages/api-documentation/export-data.md

@@ -10,11 +10,11 @@ in-page-nav: true
 
 ## The `/Group/$export` operation 
 
-The FHIR `/Group/$export` operation is the primary interaction with the DPC Sandbox API. It lets you export [Patient, Coverage, and Explanation of Benefit data]({{ "/dpc-data" | relative_url }}) asynchronously and in bulk. Details on the FHIR bulk data operations can be found in the [FHIR Bulk Data Specification](https://build.fhir.org/ig/HL7/bulk-data/OperationDefinition-group-export.html). 
+The FHIR `/Group/$export` operation is the primary interaction with the DPC Sandbox API. It lets you export [Patient, Coverage, and Explanation of Benefit data]({{ "/dpc-data.html" | relative_url }}) asynchronously and in bulk. Details on the FHIR bulk data operations can be found in the [FHIR Bulk Data Specification](https://build.fhir.org/ig/HL7/bulk-data/OperationDefinition-group-export.html). 
 
 ### Filtering data with `_type` and `_since`
 
-Use `_type` and `_since` to [filter your results]({{ "/api-documentation/export-data/how-to-filter" | relative_url }}) by content, time, and range.
+Use `_type` and `_since` to [filter your results]({{ "/api-documentation/export-data/how-to-filter.html" | relative_url }}) by content, time, and range.
 
 #### Filter by FHIR Resource type with `_type`
 Specify which of the FHIR resources to download using the `_type` query parameter (e.g., `?_type=Patient,Coverage`).
@@ -23,13 +23,13 @@ Specify which of the FHIR resources to download using the `_type` query paramete
 Choose to download data obtained after a certain date by adding the `_since` parameter (e.g., only show Patient data from January 7, 2025 to the present). 
 
 #### Get all of a patient’s data  
-Use [`/Patient/{PATIENT_ID}/$everything`]({{ "/api-documentation/export-data/patient-everything" | relative_url }}) for 7 years’ historical data including Patient, Coverage, and ExplanationOfBenefit Resources. 
+Use [`/Patient/{PATIENT_ID}/$everything`]({{ "/api-documentation/export-data/patient-everything.html" | relative_url }}) for 7 years’ historical data including Patient, Coverage, and ExplanationOfBenefit Resources. 
 
 ## Initiating an export job
 
 ### 1. Locate your Group ID
 
-In order to start a patient data export job, locate your [Group ID]({{ "/api-documentation/attribution/attestation#create-a-patient-group-resource" | relative_url }}) by referencing the `id` variable in the resource object of your group.
+In order to start a patient data export job, locate your [Group ID]({{ "/api-documentation/attribution/attestation.html#create-a-patient-group-resource" | relative_url }}) by referencing the `id` variable in the resource object of your group.
 
 **Example Group Resource**
 

src/_pages/api-documentation/export-data/how-to-filter.md

@@ -12,7 +12,7 @@ DPC uses `_type` and `_since` parameters to filter your results by content, time
 
 ## Filter claims data by FHIR Resource with `_type`
 
-The `_type` query parameter allows you to specify which FHIR Resources you wish to export. If you do not specify a `_type` parameter in your request, all three resources will be exported: [Explanation of Benefit, Patient, and Coverage]({{ "/dpc-data" | relative_url }}). You can specify these Resources individually or as a group using a comma delimited list and the syntax `?_type=ExplanationOfBenefit,Patient,Coverage`.
+The `_type` query parameter allows you to specify which FHIR Resources you wish to export. If you do not specify a `_type` parameter in your request, all three resources will be exported: [Explanation of Benefit, Patient, and Coverage]({{ "/dpc-data.html" | relative_url }}). You can specify these Resources individually or as a group using a comma delimited list and the syntax `?_type=ExplanationOfBenefit,Patient,Coverage`.
 
 The following request will export the Patient and Coverage Resources, but NOT the Explanation of Benefit Resource.
 
@@ -43,11 +43,11 @@ On subsequent calls you can begin retrieving incremental claims data for your be
 Two ways to use `_since`:
 
 1. Request the most recent data for all beneficiaries: [Use `_since` within the `/Group` endpoint](#request-data-using-_since-with-the-group-endpoint).  
-2. Request data synchronously for an individual patient: [Use `_since` within the `/Patient` endpoint]({{ "/api-documentation/export-data/patient-everything#requesting-data-using-_since-with-the-patient-endpoint" | relative_url }}).
+2. Request data synchronously for an individual patient: [Use `_since` within the `/Patient` endpoint]({{ "/api-documentation/export-data/patient-everything.html#requesting-data-using-_since-with-the-patient-endpoint" | relative_url }}).
 
 ### Steps to request filtered data
 
-1. Obtain an [access token]({{ "/api-documentation/get-access-token" | relative_url }}).  
+1. Obtain an [access token]({{ "/api-documentation/get-access-token.html" | relative_url }}).  
 2. Start a job to acquire data (you will input the `_since` parameter here. Omit `_since` to download all data).  
 3. Check the job status.  
 4. Download the data.
@@ -60,7 +60,7 @@ Datetimes submitted using `_since` must follow the [FHIR Instant format](https:/
 
 #### The value of the `_since` parameter must be URL encoded
 
-When using the [Postman Collection]({{ "/api-documentation/postman-collection" | relative_url }}), you'll need to manually encode the `_since` parameter when it contains a `+` since Postman does not automatically encode this character.
+When using the [Postman Collection]({{ "/api-documentation/postman-collection.html" | relative_url }}), you'll need to manually encode the `_since` parameter when it contains a `+` since Postman does not automatically encode this character.
 
 You can do this either by replacing the `+` with `%2B` (e.g., 2020-01-23T04:00:00.000%2B07:00 instead of 2020-01-23T04:00:00.000+07:00), or you can select the value and choose "EncodeURIComponent" from the context menu to have Postman encode the entire parameter automatically.
 

src/_pages/api-documentation/export-data/patient-everything.md

@@ -17,11 +17,11 @@ The `/Patient/{PATIENT_ID}/$everything` endpoint lets you retrieve all resources
 This is a synchronous download. `/Patient/{PATIENT_ID}/$everything` doesn't create a job that needs to be monitored or data files to download. The response body will contain the bundle. This is how it differs from a Group $export operation.
 
 
-**Note:** A Patient record must already exist in the DPC database to complete your request. However, the patient does not need to belong to [a group]({{ "/api-documentation/attribution/attestation#create-a-patient-group-resource" | relative_url }}).
+**Note:** A Patient record must already exist in the DPC database to complete your request. However, the patient does not need to belong to [a group]({{ "/api-documentation/attribution/attestation.html#create-a-patient-group-resource" | relative_url }}).
 
 ## Find a patient’s DPC ID
 
-If you only have the patient’s Medicare Beneficiary Identifier (MBI) you can retrieve the DPC internal ID by first [making a GET request for that specific patient]({{ "/api-documentation/attribution/upload-patients/add-view-list-patients#list-a-specific-patient" | relative_url }}). The UUID is returned in that response.
+If you only have the patient’s Medicare Beneficiary Identifier (MBI) you can retrieve the DPC internal ID by first [making a GET request for that specific patient]({{ "/api-documentation/attribution/upload-patients/add-view-list-patients.html#list-a-specific-patient" | relative_url }}). The UUID is returned in that response.
 
 Learn more about the HL7 FHIR Specification for:
 

src/_pages/api-documentation/get-access-token.md

@@ -16,9 +16,9 @@ DPC uses OAuth 2.0 to authorize API access. All API requests require an access t
 
 Use the following tool to create a JSON Web Token (JWT). A JWT authenticates your organization with DPC. You'll need: 
 
-- Your Private Key ([Create Public/Private Keys]({{ "/api-documentation/get-sandbox-credentials#3-create-a-public-key" | relative_url }}))
-- A registered Client Token ([Generate a client token]({{ "/api-documentation/get-sandbox-credentials#2-generate-a-client-token-in-the-sandbox-site" | relative_url }}))
-- Your Public Key ID ([Get a specific public key]({{ "/api-documentation/get-access-token/manage-credentials#get-a-specific-public-key" | relative_url }}))
+- Your Private Key ([Create Public/Private Keys]({{ "/api-documentation/get-sandbox-credentials.html#3-create-a-public-key" | relative_url }}))
+- A registered Client Token ([Generate a client token]({{ "/api-documentation/get-sandbox-credentials.html#2-generate-a-client-token-in-the-sandbox-site" | relative_url }}))
+- Your Public Key ID ([Get a specific public key]({{ "/api-documentation/get-access-token/manage-credentials.html#get-a-specific-public-key" | relative_url }}))
 
 <a class="usa-button" href="{{ "/jwt-tool.html" | relative_url }}" target="_blank">JWT Creation Tool</a>
 

src/_pages/api-documentation/get-access-token/create-jwt-manually.md

@@ -26,7 +26,7 @@ Review these steps if you’d prefer to create a JWT manually without using the
 
 **Example decoded payload**
 
-The `PUBLIC_KEY_ID` shown in the example is the one you generated while setting up DPC sandbox credentials. See [Create a public key]({{ "/api-documentation/get-sandbox-credentials#3-create-a-public-key" | relative_url }}).
+The `PUBLIC_KEY_ID` shown in the example is the one you generated while setting up DPC sandbox credentials. See [Create a public key]({{ "/api-documentation/get-sandbox-credentials.html#3-create-a-public-key" | relative_url }}).
 
 {% capture snippet %}
 {

src/_pages/api-documentation/get-access-token/manage-credentials.md

@@ -19,7 +19,7 @@ The expiration will appear as `"expiresAt": "2020-11-04T11:49:55.095-05:00"` in
 ## Create additional client tokens
 Client tokens expire after one year. We recommend you generate a new client token via the API as part of your ongoing maintenance.
 
-1. Use [the access token method]({{ "/api-documentation/get-access-token#2-create-an-access-token" | relative_url }}).
+1. Use [the access token method]({{ "/api-documentation/get-access-token.html#2-create-an-access-token" | relative_url }}).
 2. Make a `POST` request to the `/Token` endpoint.
 
 The `/Token` endpoint accepts two (optional) query parameters: 

src/_pages/api-documentation/get-an-access-token/manage-credentials.md

@@ -20,7 +20,7 @@ The expiration will appear as `"expiresAt": "2020-11-04T11:49:55.095-05:00"` in
 
 Client tokens expire after one year. We recommend you generate a new client token via the API as part of your ongoing maintenance.
 
-1. Use [the access token method]({{ "/api-documentation/get-access-token#2-create-an-access-token" | relative_url }}).
+1. Use [the access token method]({{ "/api-documentation/get-access-token.html#2-create-an-access-token" | relative_url }}).
 2. Make a `POST` request to the `/Token` endpoint.
 
 The `/Token` endpoint accepts two (optional) query parameters: