Import operation difference table added

Table added for differences between initial mode and incremental mode.

Author: EXPEkesheth

articles/healthcare-apis/fhir/import-data.md

@@ -40,6 +40,15 @@ The `import` operation supports two modes: initial mode and incremental mode. Ea
 >
 > Also, if multiple resources share the same resource ID, then only one of those resources is imported at random. An error is logged for the resources sharing the same resource ID.
 
+This table shows the difference between import modes
+|Areas|Initial mode  |Incremental mode  |
+|:------------- |:-------------|:-----|
+|Capability|Initial load of data into FHIR service|Continuous ingestion of data into FHIR service (Incremental / NRT)|
+|Concurrent API calls|Blocks concurrent write operations|Data can be ingested concurrently while executing API CRUD operations on the FHIR server|
+|Ingestion of versioned resources|Not supported|Enables ingestion of  multiple versions of FHIR resources in single batch while maintaining resource history|
+|Retain lastUpdated field value|Not supported|Retain the lastUpdated field value in FHIR resources during the ingestion process|
+|Billing| Does not incur any charge|Incurs charges based on successfully ingested resources. Charges are incurred per API pricing|
+
 ## Performance considerations
 
 To achieve the best performance with the `import` operation, consider these factors:
@@ -306,4 +315,4 @@ Here are the error messages that occur if the `import` operation fails, and reco
 
 [Copy data to Azure Synapse Analytics](copy-to-synapse.md)
 
-[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]