RubyGems - onc_certification_g10_test_kit - Versions diffs - 7.2.4 → 7.2.6 - Mend

onc_certification_g10_test_kit 7.2.4 → 7.2.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (10) hide show

data/lib/onc_certification_g10_test_kit/requirements/onc_certification_g10_test_kit_requirements.csv CHANGED Viewed

@@ -1,44 +1,98 @@
 Req Set,ID,URL,Requirement,Conformance,Actors,Sub-Requirement(s),Conditionality,Not Tested Reason,Not Tested Details
-170.315(g)(10)-test-procedure,APP-REG-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the Health IT Module supports application registration with an authorization server for the purposes of Electronic Health Information (EHI) access for single patients, including support for application registration functions to enable authentication and authorization in § 170.315(g)(10)(v) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.315#p-170.315(g)(10)(v)))].",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,APP-REG-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,The health IT developer demonstrates the Health IT Module supports application registration with an authorization server for the purposes of EHI access for multiple patients including support for application registration functions to enable authentication and authorization in § 170.315(g)(10)(v) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.315#p-170.315(g)(10)(v)))].,SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,SEC-CNN-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"For all transmissions between the Health IT Module and the application, the health IT developer demonstrates the use of a secure and trusted connection in accordance with the implementation specifications adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))] and § 170.215(c) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)))], including:
+170.315(g)(10)-test-procedure,APP-REG-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the Health IT Module supports
+application registration with an authorization server for the purposes
+of Electronic Health Information (EHI) access for single patients,
+including support for application registration functions to enable
+authentication and authorization in § 170.315(g)(10)(v).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,APP-REG-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the Health IT Module supports
+application registration with an authorization server for the purposes
+of EHI access for multiple patients including support for application
+registration functions to enable authentication and authorization in §
+170.315(g)(10)(v).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,SEC-CNN-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"For all transmissions between the Health IT Module and the
+application, the health IT developer demonstrates the use of a secure
+and trusted connection in accordance with the implementation
+specifications adopted in § 170.215(b)(1) and § 170.215(c),
+including:
 * Using TLS version 1.2 or higher; and
-* Conformance to FHIR® Communications Security requirements.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT Module to support the following for “EHR-Launch,” “Standalone-Launch,” and “Both” (“EHR-Launch” and “Standalone-Launch”) as specified in the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))].",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[EHR-Launch] The health IT developer demonstrates the ability of the Health IT Module to initiate a “launch sequence” using the “launch-ehr"" “SMART on FHIR® Core Capability” SMART EHR Launch mode detailed in the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))], including:
+* Conformance to FHIR® Communications Security requirements.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
+Module to support the following for “EHR-Launch,” “Standalone-Launch,”
+and “Both” (“EHR-Launch” and “Standalone-Launch”) as specified in the
+implementation specification adopted in § 170.215(c)(1).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[EHR-Launch] The health IT developer demonstrates the ability of the
+Health IT Module to initiate a “launch sequence” using the
+“launch-ehr"" “SMART on FHIR® Core Capability” SMART EHR Launch mode
+detailed in the implementation specification adopted in §
+170.215(c)(1), including:
 * Launching the registered launch URL of the application; and
-* Passing the parameters: “iss” and “launch”.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-3,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Standalone-Launch] The health IT developer demonstrates the ability of the Health IT Module to launch using the “launch-standalone"" “SMART on FHIR® Core Capability” SMART Standalone Launch mode detailed in the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))].",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-4,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,[Standalone-Launch] The health IT developer demonstrates the ability of the Health IT Module to support SMART’s public client profile.,SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-5,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to support the following as detailed in the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))] and standard adopted in § 170.215(a)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(a)(1)))]:
+* Passing the parameters: “iss” and “launch”.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-3,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Standalone-Launch] The health IT developer demonstrates the ability
+of the Health IT Module to launch using the “launch-standalone"" “SMART
+on FHIR® Core Capability” SMART Standalone Launch mode detailed in the
+implementation specification adopted in § 170.215(c)(1).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-4,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Standalone-Launch] The health IT developer demonstrates the ability
+of the Health IT Module to support SMART’s public client profile.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-5,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to support the following as detailed in the implementation
+specification adopted in § 170.215(c)(1) and standard adopted in §
+170.215(a)(1):
 * The “.well-known/smart-configuration” path; and
-* A FHIR® “CapabilityStatement”.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-24,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,[Both] The health IT developer demonstrates the ability of the Health IT Module to support a “.well-known/smart-configuration” path as detailed in the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))] and standard adopted in § 170.215(a)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(a)(1)))].,SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-6,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the “.well-known/smart-configuration” path to support at least the following as detailed in the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))]:
+* A FHIR® “CapabilityStatement”.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-24,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to support a “.well-known/smart-configuration” path as
+detailed in the implementation specification adopted in §
+170.215(c)(2) and standard adopted in § 170.215(a)(1).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-6,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the
+“.well-known/smart-configuration” path to support at least the
+following as detailed in the implementation specification adopted in §
+170.215(c)(1):
 * “authorization_endpoint”;
 * “token_endpoint”; and
-* “capabilities” (including support for all the “SMART on FHIR® Core Capabilities”).",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-25,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the “.well-known/smart-configuration” path to support at least the following as detailed in the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))]:
+* “capabilities” (including support for all the “SMART on FHIR® Core
+  Capabilities”).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-25,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the
+“.well-known/smart-configuration” path to support at least the
+following as detailed in the implementation specification adopted in §
+170.215(c)(2):
 * “authorization_endpoint”;
 * “token_endpoint”;
-* “capabilities” including support for “launch-ehr"",  “launch-standalone”, “authorize-post”, “client-public”, “client-confidential-symmetric”, “client-confidential-asymmetric”, “sso-openid-connect"", “context-banner”, “context-style”, “context-ehr-patient"", “context-standalone-patient"", “permission-offline”, “permission-patient”, “permission-user”, “authorize-post”, “permission-v1”, “permission-v2”;
-* “grant_types_supported” with support for “authorization_code” and “client_credentials”; and
-* “code_challenge_methods_supported” with support for “S256” and shall not include support for “plain”
+* “capabilities” including support for “launch-ehr"",
+  “launch-standalone”, “authorize-post”, “client-public”,
+  “client-confidential-symmetric”, “client-confidential-asymmetric”,
+  “sso-openid-connect"", “context-banner”, “context-style”,
+  “context-ehr-patient"", “context-standalone-patient"",
+  “permission-offline”, “permission-patient”, “permission-user”,
+  “authorize-post”, “permission-v1”, “permission-v2”;
+* “grant_types_supported” with support for “authorization_code” and
+  “client_credentials”; and
+* “code_challenge_methods_supported” with support for “S256” and shall
+  not include support for “plain”
-Additionally, the following “capabilities” must be supported if using US Core 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] or 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))]:
-* ""context-ehr-encounter""",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-7,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the FHIR® “CapabilityStatement” to support at least the following components as detailed in the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))] and standard adopted in § 170.215(a)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(a)(1)))], including:
+Additionally, the following “capabilities” must be supported if using
+US Core 6.1.0 or 7.0.0:
+* ""context-ehr-encounter""",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-7,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the FHIR®
+“CapabilityStatement” to support at least the following components as
+detailed in the implementation specification adopted in §
+170.215(c)(1) and standard adopted in § 170.215(a)(1), including:
 * “authorize”; and
-* “token”.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-8,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to receive an authorization request according to the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))], including support for the following parameters:
+* “token”.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-8,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to receive an authorization request according to the
+implementation specification adopted in § 170.215(c)(1), including
+support for the following parameters:
 * “response_type”;
 * “client_id”;
 * “redirect_uri”;
 * “launch” (for EHR-Launch mode only);
 * “scope”;
 * “state”; and
-* “aud”.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-26,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to receive an authorization request according to the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))], including support for the following parameters:
+* “aud”.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-26,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to receive an authorization request according to the
+implementation specification adopted in § 170.215(c)(2), including
+support for the following parameters:
 * “response_type”;
 * “client_id”;
 * “redirect_uri”;
@@ -47,33 +101,75 @@ Additionally, the following “capabilities” must be supported if using US Cor
 * “state”;
 * “aud”;
 * “code_challenge”; and
-* “code_challenge_method”",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-27,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,[Both] The health IT developer demonstrates the ability of the Health IT Module’s Authorization Server to support the use of the HTTP GET and POST methods at the Authorization Endpoint as detailed in the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))].,SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-9,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to support the receipt of the following scopes and capabilities according to the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))] and standard adopted in § 170.215(e)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(e)(1)))]:
-* “openid” (to support “sso-openid-connect” “SMART on FHIR® Core Capability”);
-* “fhirUser” (to support “sso-openid-connect” “SMART on FHIR® Core Capability”);
-* “need_patient_banner” (to support “context-banner” “SMART on FHIR® Core Capability” for EHR-Launch mode only);
-* “smart_style_url” (to support “context-style” “SMART on FHIR® Core Capability” for EHR-Launch mode only);
-* “launch/patient” (to support “context-standalone-patient” “SMART on FHIR® Core Capability” for Standalone-Launch mode only);
+* “code_challenge_method”",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-27,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module’s Authorization Server to support the use of the HTTP GET
+and POST methods at the Authorization Endpoint as detailed in the
+implementation specification adopted in § 170.215(c)(2).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-9,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to support the receipt of the following scopes and
+capabilities according to the implementation specification adopted in
+§ 170.215(c)(1) and standard adopted in § 170.215(e)(1):
+* “openid” (to support “sso-openid-connect” “SMART on FHIR® Core
+  Capability”);
+* “fhirUser” (to support “sso-openid-connect” “SMART on FHIR® Core
+  Capability”);
+* “need_patient_banner” (to support “context-banner” “SMART on FHIR®
+  Core Capability” for EHR-Launch mode only);
+* “smart_style_url” (to support “context-style” “SMART on FHIR® Core
+  Capability” for EHR-Launch mode only);
+* “launch/patient” (to support “context-standalone-patient” “SMART on
+  FHIR® Core Capability” for Standalone-Launch mode only);
 * “launch” (for EHR-Launch mode only);
-* “offline_access” (to support “permission-offline” “SMART on FHIR® Core Capability”);
-* Patient-level scopes (to support “permission-patient” “SMART on FHIR® Core Capability”); and
-* User-level scopes (to support “permission-user” “SMART on FHIR® Core Capability”).",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-28,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to support the receipt of the following scopes and capabilities according to the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))] and standard adopted in § 170.215(e)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(e)(1)))]:
-* “openid” (to support “sso-openid-connect” “SMART on FHIR® Capability”);
-* “fhirUser” (to support “sso-openid-connect” “SMART on FHIR® Capability”);
-* “need_patient_banner” (to support “context-banner” “SMART on FHIR® Capability” for EHR-Launch mode only);
-* “smart_style_url” (to support “context-style” “SMART on FHIR® Capability” for EHR-Launch mode only);
-* “launch/patient” (to support “context-standalone-patient” “SMART on FHIR® Capability” for Standalone-Launch mode only);
+* “offline_access” (to support “permission-offline” “SMART on FHIR®
+  Core Capability”);
+* Patient-level scopes (to support “permission-patient” “SMART on
+  FHIR® Core Capability”); and
+* User-level scopes (to support “permission-user” “SMART on FHIR® Core
+  Capability”).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-28,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to support the receipt of the following scopes and
+capabilities according to the implementation specification adopted in
+§ 170.215(c)(2) and standard adopted in § 170.215(e)(1):
+* “openid” (to support “sso-openid-connect” “SMART on FHIR®
+  Capability”);
+* “fhirUser” (to support “sso-openid-connect” “SMART on FHIR®
+  Capability”);
+* “need_patient_banner” (to support “context-banner” “SMART on FHIR®
+  Capability” for EHR-Launch mode only);
+* “smart_style_url” (to support “context-style” “SMART on FHIR®
+  Capability” for EHR-Launch mode only);
+* “launch/patient” (to support “context-standalone-patient” “SMART on
+  FHIR® Capability” for Standalone-Launch mode only);
 * “launch” (for EHR-Launch mode only);
-* “offline_access” (to support “permission-offline” “SMART on FHIR® Capability”);
-* Patient-level scopes (to support “permission-patient” and “SMART on FHIR® Capability”);
-* User-level scopes (to support “permission-user” “SMART on FHIR® Capability”); and
-* SMART v1 scope syntax for patient-level and user-level scopes to support the “permission-v1” “SMART on FHIR® Capability”
-* SMART v2 scope syntax for patient-level and user-level scopes to support the “permission-v2” “SMART on FHIR® Capability”. If using US Core 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] or 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))], this includes support for finer-grained resource constraints using search parameters according to section 3.0.2.3 of the implementation specification at § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))] for the “category” parameter for the following resources: (1) Condition resource with Condition sub-resources Encounter Diagnosis, Problem List, and Health Concern; and (2) Observation resource with Observation sub-resources Clinical Test, Laboratory, Social History, SDOH, Survey, and Vital Signs",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-10,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to evaluate the authorization request and request end-user input, if applicable (required for patient-facing applications), including the ability for the end-user to authorize an application to receive EHI based on FHIR® resource-level scopes for all of the FHIR® resources associated with the profiles specified in a standard adopted in § 170.213 [([link](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-D/part-170/subpart-B/section-170.213))] and the corresponding implementation specification adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].
+* “offline_access” (to support “permission-offline” “SMART on FHIR®
+  Capability”);
+* Patient-level scopes (to support “permission-patient” and “SMART on
+  FHIR® Capability”);
+* User-level scopes (to support “permission-user” “SMART on FHIR®
+  Capability”); and
+* SMART v1 scope syntax for patient-level and user-level scopes to
+  support the “permission-v1” “SMART on FHIR® Capability”
+* SMART v2 scope syntax for patient-level and user-level scopes to
+  support the “permission-v2” “SMART on FHIR® Capability”. If using
+  US Core 6.1.0 or 7.0.0, this includes support for finer-grained
+  resource constraints using search parameters according to section
+  3.0.2.3 of the implementation specification at § 170.215(c)(2) for
+  the “category” parameter for the following resources: (1) Condition
+  resource with Condition sub-resources Encounter Diagnosis, Problem
+  List, and Health Concern; and (2) Observation resource with
+  Observation sub-resources Clinical Test, Laboratory, Social History,
+  SDOH, Survey, and Vital Signs",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-10,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to evaluate the authorization request and request end-user
+input, if applicable (required for patient-facing applications),
+including the ability for the end-user to authorize an application to
+receive EHI based on FHIR® resource-level scopes for all of the FHIR®
+resources associated with the profiles specified in a standard adopted
+in § 170.213 and the corresponding implementation specification
+adopted in § 170.215(b)(1).
-If using US Core 3.1.1 [([link](https://hl7.org/fhir/us/core/STU3.1.1/index.html))], 4.0.0 [([link](https://hl7.org/fhir/us/core/STU4/index.html))], or 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] these resources include:
+If using US Core 3.1.1, 4.0.0, or 6.1.0 these resources include:
 * “AllergyIntolerance”;
 * “CarePlan”;
@@ -91,16 +187,23 @@ If using US Core 3.1.1 [([link](https://hl7.org/fhir/us/core/STU3.1.1/index.html
 * “Procedure”; and
 * “Provenance”.
-The following resources must also be supported if using US Core 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))]:
+The following resources must also be supported if using US Core 6.1.0:
 * ""Encounter""
 * ""Coverage""
 * ""Specimen""
 * ""MedicationDispense""
 * ""RelatedPerson""; and
-* ""ServiceRequest""",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-33,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to evaluate the authorization request and request end-user input, if applicable (required for patient-facing applications), including the ability for the end-user to authorize an application to receive EHI based on FHIR® resource-level scopes for all of the FHIR® resources associated with the profiles specified in a standard adopted in § 170.213 [([link](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-D/part-170/subpart-B/section-170.213))] and the corresponding implementation specification adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].
+* ""ServiceRequest""",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-33,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to evaluate the authorization request and request end-user
+input, if applicable (required for patient-facing applications),
+including the ability for the end-user to authorize an application to
+receive EHI based on FHIR® resource-level scopes for all of the FHIR®
+resources associated with the profiles specified in a standard adopted
+in § 170.213 and the corresponding implementation specification
+adopted in § 170.215(b)(1).
-If using US Core 3.1.1 [([link](https://hl7.org/fhir/us/core/STU3.1.1/index.html))], 4.0.0 [([link](https://hl7.org/fhir/us/core/STU4/index.html))], 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))], or 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))] these resources include:
+If using US Core 3.1.1, 4.0.0, 6.1.0, or 7.0.0 these resources include:
 * “AllergyIntolerance”;
 * “CarePlan”;
@@ -118,7 +221,7 @@ If using US Core 3.1.1 [([link](https://hl7.org/fhir/us/core/STU3.1.1/index.html
 * “Procedure”; and
 * “Provenance”.
-The following resources must also be supported if using US Core 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] or 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))]:
+The following resources must also be supported if using US Core 6.1.0 or 7.0.0:
 * ""Encounter""
 * ""Coverage""
 * ""Specimen""
@@ -126,122 +229,186 @@ The following resources must also be supported if using US Core 6.1.0 [([link](h
 * ""RelatedPerson""; and
 * ""ServiceRequest""
-The following resources must also be supported if using US Core 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))]:
-* ""Location""",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-11,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to evaluate the authorization request and request end-user input, if applicable (required for patient-facing applications), including either the ability for the end-user to explicitly enable / disable the “offline_access” scope or information communicating the application’s request for the “offline_access” scope.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-12,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to deny an application’s authorization request according to a patient’s preferences selected in AUT-PAT-10, and AUT-PAT-11, of this section in accordance with the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))].",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-34,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to deny an application’s authorization request according to a patient’s preferences selected in AUT-PAT-33, and AUT-PAT-11, of this section in accordance with the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))].",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-29,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,[EHR-Launch] The health IT developer demonstrates the ability of the Health IT Module to establish a patient in context if an application requests a clinical scope which is restricted to a single patient as detailed in the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))].,SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-13,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to return an error response if the ""aud"" parameter provided by an application to the Health IT Module in AUT-PAT-8, is not a valid FHIR® resource server associated with the Health IT Module's authorization server.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-37,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to return an error response if the ""aud"" parameter provided by an application to the Health IT Module in AUT-PAT-26, is not a valid FHIR® resource server associated with the Health IT Module's authorization server.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-14,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to grant an application access to EHI by returning an authorization code to the application according to the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))], including the following parameters:
+The following resources must also be supported if using US Core 7.0.0:
+* ""Location""",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-11,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to evaluate the authorization request and request end-user
+input, if applicable (required for patient-facing applications),
+including either the ability for the end-user to explicitly enable /
+disable the “offline_access” scope or information communicating the
+application’s request for the “offline_access” scope.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-12,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to deny an application’s authorization request according to
+a patient’s preferences selected in AUT-PAT-10, and AUT-PAT-11, of
+this section in accordance with the implementation specification
+adopted in § 170.215(c)(1).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-34,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to deny an application’s authorization request according to
+a patient’s preferences selected in AUT-PAT-33, and AUT-PAT-11, of
+this section in accordance with the implementation specification
+adopted in § 170.215(c)(1).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-29,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[EHR-Launch] The health IT developer demonstrates the ability of the
+Health IT Module to establish a patient in context if an application
+requests a clinical scope which is restricted to a single patient as
+detailed in the implementation specification adopted in §
+170.215(c)(2).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-13,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to return an error response if the ""aud"" parameter provided
+by an application to the Health IT Module in AUT-PAT-8, is not a valid
+FHIR® resource server associated with the Health IT Module's
+authorization server.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-37,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to return an error response if the ""aud"" parameter provided
+by an application to the Health IT Module in AUT-PAT-26, is not a valid
+FHIR® resource server associated with the Health IT Module's
+authorization server.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-14,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to grant an application access to EHI by returning an
+authorization code to the application according to the implementation
+specification adopted in § 170.215(c)(1), including the following
+parameters:
 * “code”; and
-* “state”.",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-15,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to receive the following parameters from an application according to the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))]:
+* “state”.",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-15,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to receive the following parameters from an application
+according to the implementation specification adopted in §
+170.215(c)(1):
 * “grant_type”;
 * “code”;
 * “redirect_uri”;
-* “client_id” (to support “client-public” “SMART on FHIR® Capability”); and
-* Authorization header including “client_id” and “client_secret” (to support “client-confidential-symmetric” “SMART on FHIR® Capability”).",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-30,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to receive the following access token request parameters from an application according to the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))]:
+* “client_id” (to support “client-public” “SMART on FHIR®
+  Capability”); and
+* Authorization header including “client_id” and “client_secret” (to
+  support “client-confidential-symmetric” “SMART on FHIR®
+  Capability”).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-30,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to receive the following access token request parameters
+from an application according to the implementation specification
+adopted in § 170.215(c)(2):
 * “grant_type”;
 * “code”;
 * “redirect_uri”;
 * “code_verifier”;
-* “client_id” (to support “client-public” “SMART on FHIR® Capability”);
-* Authorization header including “client_id” and “client_secret” (to support “client-confidential-symmetric” “SMART on FHIR® Capability”); and
-* Authentication JSON Web Token (to support “client-confidential-asymmetric” “SMART on FHIR® Capability”)",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-31,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,[Both] The health IT developer demonstrates the ability of the Health IT Module to return an error response if an invalid “code_verifier” value is supplied with an access token request according to the implementation specification adopted in § 170.215(c)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(2)))].,SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-16,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to return a JSON object to applications according to the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))] and standard adopted in § 170.215(e)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(e)(1)))], including the following:
+* “client_id” (to support “client-public” “SMART on FHIR®
+  Capability”);
+* Authorization header including “client_id” and “client_secret” (to
+  support “client-confidential-symmetric” “SMART on FHIR®
+  Capability”); and
+* Authentication JSON Web Token (to support
+  “client-confidential-asymmetric” “SMART on FHIR® Capability”)",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-31,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to return an error response if an invalid “code_verifier”
+value is supplied with an access token request according to the
+implementation specification adopted in § 170.215(c)(2).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-16,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to return a JSON object to applications according to the
+implementation specification adopted in § 170.215(c)(1) and standard
+adopted in § 170.215(e)(1), including the following:
 * “access_token”;
 * “token_type”;
 * “scope”;
 * “id_token”;
-* “refresh_token” (valid for a period of no shorter than three months);
-* HTTP “Cache-Control” response header field with a value of “no-store”;
+* “refresh_token” (valid for a period of no shorter than three
+  months);
+* HTTP “Cache-Control” response header field with a value of
+  “no-store”;
 * HTTP “Pragma” response header field with a value of “no-cache”;
-* “patient” (to support “context-ehr-patient” and “context-standalone-patient” “SMART on FHIR® Core Capabilities”);
-* “need_patient_banner” (to support “context-banner” “SMART on FHIR® Core Capability” for EHR-Launch mode only); and
-* “smart_style_url” (to support “context-style” “SMART on FHIR® Core Capability” for EHR-Launch mode only).
+* “patient” (to support “context-ehr-patient” and
+  “context-standalone-patient” “SMART on FHIR® Core Capabilities”);
+* “need_patient_banner” (to support “context-banner” “SMART on FHIR®
+  Core Capability” for EHR-Launch mode only); and
+* “smart_style_url” (to support “context-style” “SMART on FHIR® Core
+  Capability” for EHR-Launch mode only).
-Additionally, the following must be supported if using US Core 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))]:
-* “encounter” (to support ""context-ehr-encounter"" “SMART on FHIR® Capability”)",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-35,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health IT Module to return a JSON object to applications according to the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))] and standard adopted in § 170.215(e)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(e)(1)))], including the following:
+Additionally, the following must be supported if using US Core 6.1.0:
+* “encounter” (to support ""context-ehr-encounter"" “SMART on FHIR®
+  Capability”)",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-35,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
+IT Module to return a JSON object to applications according to the
+implementation specification adopted in § 170.215(c)(1) and standard
+adopted in § 170.215(e)(1), including the following:
 * “access_token”;
 * “token_type”;
 * “scope”;
 * “id_token”;
-* “refresh_token” (valid for a period of no shorter than three months);
-* HTTP “Cache-Control” response header field with a value of “no-store”;
+* “refresh_token” (valid for a period of no shorter than three
+  months);
+* HTTP “Cache-Control” response header field with a value of
+  “no-store”;
 * HTTP “Pragma” response header field with a value of “no-cache”;
-* “patient” (to support “context-ehr-patient” and “context-standalone-patient” “SMART on FHIR® Core Capabilities”);
-* “need_patient_banner” (to support “context-banner” “SMART on FHIR® Core Capability” for EHR-Launch mode only); and
-* “smart_style_url” (to support “context-style” “SMART on FHIR® Core Capability” for EHR-Launch mode only).
+* “patient” (to support “context-ehr-patient” and
+  “context-standalone-patient” “SMART on FHIR® Core Capabilities”);
+* “need_patient_banner” (to support “context-banner” “SMART on FHIR®
+  Core Capability” for EHR-Launch mode only); and
+* “smart_style_url” (to support “context-style” “SMART on FHIR® Core
+  Capability” for EHR-Launch mode only).
-Additionally, the following must be supported if using US Core 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] or 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))]:
-* “encounter” (to support ""context-ehr-encounter"" “SMART on FHIR® Capability”)",SHALL,Server,,false,,
+Additionally, the following must be supported if using US Core 6.1.0 or
+7.0.0:
+* “encounter” (to support ""context-ehr-encounter"" “SMART on FHIR®
+  Capability”)",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-17,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
 IT Module to provide an OpenID Connect well-known URI in accordance
-with the implementation specification adopted in § 170.215(e)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(e)(1)))],
+with the implementation specification adopted in § 170.215(e)(1),
 including:
 * All required fields populated according to implementation
-  specification adopted in § 170.215(e)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(e)(1)))]; and
+  specification adopted in § 170.215(e)(1); and
 * Valid JWKS populated according to implementation specification can
-  be retrieved via JWKS URI.",SHALL,Server,,false,,
+  be retrieved via JWKS URI.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-18,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
 IT Module to deny an application’s authorization request in accordance
-with the implementation specification adopted in § 170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))].",SHALL,Server,,false,,
+with the implementation specification adopted in § 170.215(c)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-19,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
 IT Module to return a “Patient” FHIR® resource that matches the
 patient context provided in step AUT-PAT-16 of this section according
-to an implementation specification adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].",SHALL,Server,,false,,
+to an implementation specification adopted in § 170.215(b)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-36,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
 IT Module to return a “Patient” FHIR® resource that matches the
 patient context provided in step AUT-PAT-35 of this section according
-to an implementation specification adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].",SHALL,Server,,false,,
-170.315(g)(10)-test-procedure,AUT-PAT-32,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[EHR-Launch] The following must be supported if using US Core 6.1.0 [([link](https://hl7.org/fhir/us/core/STU6.1/index.html))] or 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))]:
+to an implementation specification adopted in § 170.215(b)(1).",SHALL,Server,,FALSE,,
+170.315(g)(10)-test-procedure,AUT-PAT-32,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[EHR-Launch] The following must be supported if using US Core 6.1.0 or 7.0.0:
 The health IT developer demonstrates the ability of the Health IT
 Module to return an “Encounter” FHIR® resource that matches the
 encounter context provided in step AUT-PAT-35 of this section
 according to an implementation specification adopted in §
-170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].",SHALL,Server,,false,,
+170.215(b)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-20,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
 IT Module to grant an access token when a refresh token is supplied
 according to an implementation specification adopted in §
-170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].",SHALL,Server,,false,,
+170.215(b)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-21,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"[Both] The health IT developer demonstrates the ability of the Health
 IT Module to grant a refresh token valid for a period of no less than
 three months to native applications capable of securing a refresh
-token.",SHALL,Server,,false,,
+token.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-22,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to issue a refresh token valid for a new period of no shorter
 than three months without requiring re-authentication and
 re-authorization when a valid refresh token is supplied by the
 application according to the implementation specification adopted in §
-170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))].",SHALL,Server,,false,,
+170.215(c)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-PAT-23,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to return an error response when supplied an invalid refresh
 token as specified in the implementation specification adopted in §
-170.215(c)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)(1)))].",SHALL,Server,,false,,
+170.215(c)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,PAR-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to revoke access to an authorized application at a patient’s
 direction, including a demonstration of the inability of the
-application with revoked access to receive patient EHI.",SHALL,Server,,false,,
+application with revoked access to receive patient EHI.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support OAuth 2.0 client credentials grant flow in
 accordance with an implementation specification adopted in §
-170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support the following parameters according to an
-implementation specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))]:
+implementation specification adopted in § 170.215(d):
 * “scope”;
 * “grant_type”;
 * “client_assertion_type”; and
-* “client_assertion”.",SHALL,Server,,false,,
+* “client_assertion”.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-3,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support the following JSON Web Token (JWT) Headers and
 Claims according to an implementation specification adopted in §
-170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))]:
+170.215(d):
 * “alg” header;
 * “kid” header;
 * “typ” header;
@@ -249,83 +416,83 @@ Claims according to an implementation specification adopted in §
 * “sub” claim;
 * “aud” claim;
 * “exp” claim; and
-* “jti” claim.",SHALL,Server,,false,,
+* “jti” claim.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-4,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to receive and process the JSON Web Key (JWK) Set via a
 TLS-protected URL to support authorization for system scopes in §
-[([link](https://www.ecfr.gov/current/title-45/part-170/section-170.315#p-170.315(g)(10)(v)(B)))].",SHALL,Server,,false,,
+170.315(g)(10)(v)(B).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-5,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates that the Health IT Module does
 not cache a JWK Set received via a TLS-protected URL for longer than
-the “cache-control” header sent by an application indicates.",SHALL,Server,,false,,
+the “cache-control” header sent by an application indicates.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-6,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to validate an application’s JWT, including its JSON Web
 Signatures, according to an implementation specification adopted in §
-170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-7,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to respond with an “invalid_client” error for errors
 encountered during the authentication process according to an
-implementation specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+implementation specification adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-8,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to assure the scope granted based on the scope requested by an
 application is no greater than the pre-authorized scope for multiple
 patients according to an implementation specification adopted in §
-170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-9,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to issue an access token to an application as a JSON object in
 accordance with an implementation specification adopted in §
-170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))], including the following property names:
+170.215(d), including the following property names:
 * “access_token”;
 * “token_type”;
 * “expires_in”; and
-* “scope”.",SHALL,Server,,false,,
+* “scope”.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,AUT-SYS-10,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to respond to errors using the appropriate error messages as
-specified in an implementation specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+specified in an implementation specification adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,TOK-INTRO-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to receive and validate a token it has issued in accordance
-with an implementation specification in § 170.215(c) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(c)))].",SHALL,Server,,false,,
+with an implementation specification in § 170.215(c).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,SH-PAT-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support the “capabilities” interaction as specified in the
-standard adopted in § 170.215(a)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(a)(1)))], including support for a
+standard adopted in § 170.215(a)(1), including support for a
 “CapabilityStatement” as specified in the standard adopted in §
-170.215(a)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(a)(1)))] and an implementation specification adopted in §
-170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].",SHALL,Server,,false,,
+170.215(a)(1) and an implementation specification adopted in §
+170.215(b)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,SH-PAT-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to respond to requests for a single patient’s data consistent
 with the search criteria detailed in the “US Core Server
 CapabilityStatement” section of an implementation specification
-adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))], including demonstrating search support for
+adopted in § 170.215(b)(1), including demonstrating search support for
 “SHALL” operations and parameters for all the data included in the
-corresponding standard adopted in § 170.213 [([link](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-D/part-170/subpart-B/section-170.213))].",SHALL,Server,,false,,
+corresponding standard adopted in § 170.213.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,SH-PAT-3,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a resource search for the provenance target
 “(_revIncludes: Provenance:target)” for all the FHIR® resources
-included in a standard adopted in § 170.213 [([link](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-D/part-170/subpart-B/section-170.213))] and the corresponding
-implementation specification adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))] according to
+included in a standard adopted in § 170.213 and the corresponding
+implementation specification adopted in § 170.215(b)(1) according to
 the “Basic Provenance Guidance” section of an implementation
-specification adopted in § 170.215(b)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)))].",SHALL,Server,,false,,
+specification adopted in § 170.215(b)(1).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,SH-PAT-4,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support the “capabilities” interaction as specified in the
-standard adopted in § 170.215(a)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(a)(1)))], including support for a
+standard adopted in § 170.215(a)(1), including support for a
 “CapabilityStatement” as specified in the standard adopted in §
-170.215(a)(1) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(a)(1)))] and an implementation specification adopted in §
-170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+170.215(a)(1) and an implementation specification adopted in §
+170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,SH-PAT-5,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support requests for multiple patients’ data as a group
 using the “group-export” operation as detailed in an implementation
-specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+specification adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"For responses to data for single and multiple patients as described in
 steps DAT-PAT-7, and DAT-PAT-8, of this section respectively, the
 health IT developer demonstrates the ability of the Health IT Module
 to respond to requests for data according to the implementation
-specification adopted in § 170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))], including the following
-steps.",SHALL,Server,,false,,
+specification adopted in § 170.215(b)(1)(i), including the following
+steps.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-18,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"For responses to data for single and multiple patients as described in
 steps DAT-PAT-7, and DAT-PAT-17, of this section respectively, the
 health IT developer demonstrates the ability of the Health IT Module
 to respond to requests for data according to the implementation
-specification adopted in § 170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))], including the following
-steps.",SHALL,Server,,false,,
+specification adopted in § 170.215(b)(1)(i), including the following
+steps.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to respond with data that meet the following conditions:
 * All data elements indicated with a cardinality of one or greater and
@@ -337,42 +504,42 @@ Module to respond with data that meet the following conditions:
 * All information is accurate and without omission; and
 * All references within the resources can be resolved and validated,
   as applicable, according to steps DAT-PAT-2, DAT-PAT-3, DAT-PAT-4,
-  DAT-PAT-5, and DAT-PAT-6, of this section.",SHALL,Server,,false,,
+  DAT-PAT-5, and DAT-PAT-6, of this section.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-3,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a “Provenance” FHIR® resource for all the FHIR®
-resources included in the standard adopted in § 170.213(a) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.213#p-170.213(a)))] and
-implementation specification adopted in § 170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))] according
+resources included in the standard adopted in § 170.213(a) and
+implementation specification adopted in § 170.215(b)(1)(i) according
 to the “Basic Provenance Guidance” section of the implementation
-specification adopted in § 170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))].",SHALL,Server,,false,,
+specification adopted in § 170.215(b)(1)(i).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-4,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a “DocumentReference” and/or “DiagnosticReport”
 FHIR® resource for each of the “Clinical Notes” and “Diagnostic
 Reports” included in and according to the “Clinical Notes Guidance”
 section of the implementation specification adopted in §
-170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))].",SHALL,Server,,false,,
+170.215(b)(1)(i).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-5,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"If supported, and for responses to data for a single patient only, the
 health IT developer demonstrates the ability of the Health IT Module
 to support a “Medication” FHIR® resource according to the “Medication
 List Guidance” section of the implementation specification adopted in
-§ 170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))].",SHALL,Server,,false,,
+§ 170.215(b)(1)(i).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-6,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support “Missing Data” according to the implementation
 specification adopted in § 170. 215(b)(1)(i), including:
 * For non-coded data elements; and
 * For coded data elements, including support for the
-  “DataAbsentReason” Code System.",SHALL,Server,,false,,
+  “DataAbsentReason” Code System.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-7,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to return all of the data associated with requests for a single
 patient’s data according to the “US Core Server CapabilityStatement”
 section of the implementation specification adopted in §
-170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))] for all the data included in the standard adopted in
-§ 170.213(a) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.213#p-170.213(a)))].",SHALL,Server,,false,,
+170.215(b)(1)(i) for all the data included in the standard adopted in
+§ 170.213(a).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-8,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to respond to requests for multiple patients’ data according to
-an implementation specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))] for all of the
+an implementation specification adopted in § 170.215(d) for all of the
 FHIR® resources associated with the profiles and Data Elements
-specified in and according to the standard adopted in § 170.213(a) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.213#p-170.213(a)))] and
-implementation specification adopted in § 170.215(b)(1)(i) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(i)))]:
+specified in and according to the standard adopted in § 170.213(a) and
+implementation specification adopted in § 170.215(b)(1)(i):
 * “AllergyIntolerance”;
 * “CarePlan”;
 * “CareTeam”;
@@ -391,13 +558,13 @@ implementation specification adopted in § 170.215(b)(1)(i) [([link](https://w
 * “Patient”;
 * “Practitioner”
 * “Procedure”; and
-* “Provenance”.",SHALL,Server,,false,,
+* “Provenance”.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-17,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to respond to requests for multiple patients’ data according to
-an implementation specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))] for all of the
+an implementation specification adopted in § 170.215(d) for all of the
 FHIR® resources associated with the profiles and Data Elements
-specified in and according to the standard adopted in § 170.213(b) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.213#p-170.213(b)))] and
-implementation specification adopted in § 170.215(b)(1)(ii) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(b)(1)(ii)))].
+specified in and according to the standard adopted in § 170.213(b) and
+implementation specification adopted in § 170.215(b)(1)(ii).
 * “AllergyIntolerance”;
 * “CarePlan”;
 * “CareTeam”;
@@ -409,7 +576,7 @@ implementation specification adopted in § 170.215(b)(1)(ii) [([link](https://
 * “Encounter”;
 * “Goal”;
 * “Immunization”;
-* “Location” (if supported or using US Core 7.0.0 [([link](https://hl7.org/fhir/us/core/STU7/index.html))]);
+* “Location” (if supported or using US Core 7.0.0);
 * “Medication” (if supported);
 * “MedicationDispense”
 * “MedicationRequest”;
@@ -423,30 +590,30 @@ implementation specification adopted in § 170.215(b)(1)(ii) [([link](https://
 * “QuestionnaireReponse” (if supported);
 * “RelatedPerson”;
 * “Specimen”; and
-* “ServiceRequest”",SHALL,Server,,false,,
+* “ServiceRequest”",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-9,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to limit the data returned to only those FHIR® resources for
 which the client is authorized according to an implementation
-specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+specification adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-10,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a successful data response according to an
-implementation adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+implementation adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-11,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a data response error according to an implementation
-adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-12,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a bulk data delete request according to an
-implementation specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+implementation specification adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-13,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a bulk data status request according to an
-implementation specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))].",SHALL,Server,,false,,
+implementation specification adopted in § 170.215(d).",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-14,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates the ability of the Health IT
 Module to support a file request according to an implementation
-specification adopted in § 170.215(d) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.215#p-170.215(d)))], including support for the
-“ndjson” format for files provided.",SHALL,Server,,false,,
+specification adopted in § 170.215(d), including support for the
+“ndjson” format for files provided.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,DAT-PAT-15,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates that the information provided as
 part of this data response includes data for patients in the group
-identifier provided during the “group-export” request.",SHALL,Server,,false,,
+identifier provided during the “group-export” request.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,API-DOC-1,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer supplies documentation describing the API(s)
 of the Health IT Module and includes at a minimum:
 * API syntax;
@@ -457,12 +624,12 @@ of the Health IT Module and includes at a minimum:
 * Mandatory software components;
 * Mandatory software configurations; and
 * All technical requirements and attributes necessary for
-  registration.",SHALL,Server,,false,,
+  registration.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,API-DOC-2,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"The health IT developer demonstrates that the documentation described
 in step API-DOC-1, of this section is available via a publicly
 accessible hyperlink that does not require preconditions or additional
-steps to access.",SHALL,Server,,false,,
+steps to access.",SHALL,Server,,FALSE,,
 170.315(g)(10)-test-procedure,API-DOC-3,https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#test_procedure,"To fulfill the API Maintenance of Certification requirement at §
-170.404(b)(2) [([link](https://www.ecfr.gov/current/title-45/part-170/section-170.404#p-170.404(b)(2)))], the health IT developer demonstrates the public
+170.404(b)(2), the health IT developer demonstrates the public
 location of its certified API technology service base URLs and related
-organization details.",SHALL,Server,,false,,
+organization details.",SHALL,Server,,FALSE,,