In the HAPI JDBC mode, when resources are created with PUT, resource Id's mismatch between the original FHIR resource and the corresponding resource in the parquet file. about fhir-data-pipes HOT 4 CLOSED

Thanks @vbothe23 for filing this issue; are you using the FHIR-search mode or direct DB access when fetching resources? Is it possible that in the source FHIR server, there is also a Patient resource with id 82656? This behavior is unexpected and the IDs should be preserved.

from fhir-data-pipes.

Hi @bashir2,
I am using JDBC mode to fetch the resources.

In the HAPI FHIR server, resource IDs are automatically generated by the system, even if we explicitly specify an ID during resource creation. These auto-generated IDs are stored in the hfj_resource table, while explicitly specified IDs are stored in the hfj_forced_id table. However, the pipeline relies on the IDs from the hfj_resource table, leading to a discrepancy between the actual resource ID and the ID in the parquet file.

from fhir-data-pipes.

Thanks @vbothe23 for the clarification; yes this is a bug that we should fix. In the meantime you can use the FHIR search mode (i.e., avoid JDBC) and I believe that should return the original resource IDs.

from fhir-data-pipes.

This was fixed by #754 thanks @vbothe23.

from fhir-data-pipes.