Merge pull request #287891 from KendalBond007/FHIRbestPracticesRedux_Oct24

FHIRbestPracticesReduxOct24

Author: v-regandowner

articles/healthcare-apis/fhir/fhir-best-practices.md

@@ -23,10 +23,10 @@ This document provides guidance on best practices with the Azure Health Data Ser
 
 Azure FHIR service supports data ingestion through the import operation, which offers two modes: initial mode, and incremental mode. For detailed guidance, refer to the [Importing data into the FHIR service](import-data.md) documentation.
 
-* **Consider** using the import operation over HTTP API requests to ingest the data into FHIR service. The import operation provides a high throughput and is a scalable method for loading data.
 To achieve optimal performance with the import operation, consider the following best practices.
 
 * **Do** use large files while ingesting data. The optimal DNJSON file size for import is 50 MB or larger (or 20,000 resources or more, with no upper limit). Combining smaller files into larger ones can enhance performance.
+* **Consider** using the import operation over HTTP API requests to ingest the data into FHIR service. The import operation provides a high throughput and is a scalable method for loading data.
 * **Consider** importing all FHIR resource files in a single import operation for optimal performance. Aim for a total file size of 100 GB or more (or 100 million resources, no upper limit) in one operation. Maximizing an import in this way helps reduce the overhead associated with managing multiple import jobs.
 * **Consider** running multiple concurrent imports only if necessary, but limit parallel import jobs. A single large import is designed to consume all available system resources, and processing throughput doesn't increase with concurrent import jobs.
 
@@ -73,4 +73,4 @@ For more information on export operations, see [Export your FHIR data](export-da
 
 By applying these best practices you can enhance the performance and efficiency of data ingestion, bundle processing, query execution, and data extraction in Azure FHIR service.
 
-[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/fhir/toc.yml

@@ -16,7 +16,7 @@ items:
       href: migration-strategies.md
     - name: SMART on FHIR
       href: smart-on-fhir.md
-    - name: FHIR best practices
+    - name: Best practices
       href: fhir-best-practices.md
 - name: Quickstarts
   expanded: true