Closed theGOTOguy closed 1 month ago
This is related to the https://github.com/hapifhir/hapi-fhir project - not this project.
@jamesagnew you might wan't to have a look at this
I've just experienced this as well when my Observation had valueInteger: 29
I changed it to valueString: "29"
and it worked.
This issue is stale because it has been open 730 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
I cannot reproduce this error in the https://hapi.fhir.org server, but it is straightforward to reproduce from the DockerHub images. It appears that a valueBoolean from an Observation triggers an error when updating a DiagnosticReport in a batch bundle even though these two updates should be independent.
Specifically, the error that appears in the server is:
This example uses STU3, but the error also reproduces in R4.
To reproduce, start by booting up a local server:
First create a Patient:
This will become
Patient/1
for the sake of what follows.Next, create a DiagnosticReport:
This will become
DiagnosticReport/2
.Next, create an Observation:
This will become
Observation/3
.Now we will create a file
batch_update_test.json
where we will update the Observation to have a valueBoolean and the DiagnosticReport to refer to the Observation.Posting this bundle,
We get:
Strangely, while the error occurs on the DiagnosticReport, it is somehow related to the Observation! If you go back and change the
valueBoolean: true
tovalueString: "true"
in the update, then your batch bundle works just fine.This error does occur if you use a transaction instead of a batch as well, and as obscure as this issue seems it is preventing our ETL from running on HAPI as we are trying to migrate away from Azure API for FHIR. For now, we are able to work around this by setting
hapi.fhir.narrative_enabled: false
.