Skip to content

Commit f74e467

Browse files
authored
Update import-data.md
Adding limitations of import job
1 parent 7df698a commit f74e467

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -70,11 +70,8 @@ To achieve the best performance with the `import` operation, consider these fact
7070

7171
- Configure the FHIR server. The FHIR data must be stored in resource-specific files in FHIR NDJSON format on the Azure blob store. For more information, see [Configure import settings](configure-import-data.md).
7272

73-
- All the resources in a file must be the same type. You can have multiple files for each resource type.
74-
7573
- The data must be in the same tenant as the FHIR service.
7674

77-
- The maximum number of files allowed for each `import` operation is 10,000.
7875

7976
### Make a call
8077

@@ -313,6 +310,10 @@ Here are the error messages that occur if the `import` operation fails, along wi
313310

314311
**Solution:** Reduce the size of your data or consider Azure API for FHIR, which has a higher storage limit.
315312

313+
## Limitations
314+
- The maximum number of files allowed for each `import` operation is 10,000.
315+
- The number of files ingested in the FHIR server with same lastUpdated field value upto milliseconds, cannot exceed beyond 10,000.
316+
316317
## Next steps
317318

318319
[Convert your data to FHIR](convert-data.md)

0 commit comments

Comments
 (0)