How to fix Azure FHIR service bulk import failure

Harsha Gopu 0

FHIR service Postman Bulk import failed with the below error message. I made sure my Patient data is properly formatted in ndjson. Would you please help how to troubleshoot this issue?

    "resourceType": "OperationOutcome",
    "id": "766c5e38019c0a1686b41338d3add8b7",
    "meta": {
        "lastUpdated": "2024-02-19T15:29:01.6430253+00:00"
    },
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "diagnostics": "import operation failed for reason: Input string was not in a correct format."
        }
    ]
}

SnehaAgrawal-MSFT 18,366 Reputation points

2024-02-20T12:58:00.3566667+00:00
@Harsha Gopu Thanks for reaching here! The error message you are seeing indicates that the bulk import operation for your Azure FHIR service failed-

"import operation failed for reason: Input string was not in a correct format."

Could you please verify below points:

Check the format of your input data to ensure that it is correctly formatted in ndjson. Make sure that each line of the ndjson file contains a valid FHIR resource in JSON format.

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.

All the resources in a file must be the same type. You can have multiple files per resource type.

The data must be in the same tenant as the FHIR service.

The maximum number of files allowed per import operation is 10,000.

Reference- Import FHIR data

Please let us know if issue remains.
Harsha Gopu 0 Reputation points

2024-02-23T14:41:51.8433333+00:00

Hi Sneha, Yes, I made sure that I followed all the above mentioned guidelines but still I am getting the same error.
SnehaAgrawal-MSFT 18,366 Reputation points

2024-02-26T10:00:16.36+00:00

@Harsha Gopu Sure, could you also on confirm, each record is on a separate line, and the entire file should be valid JSON. Also verify that there are no syntax errors, missing commas, or other issues in your data. If still facing issue, suggest you send email, reached you internally.