You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While validating a search response that uses _include / _revinclude to pull back different resource types with the same id, the searchset bundle fails base FHIR validation.
Validation of response body against profile 'http://hl7.org/fhir/StructureDefinition/Bundle' by FHIR specification's Validation Engine produced the following results:ERROR: Duplicate id value 'zpxDuEwss146'. Location: Bundle.entry[1] (line 68, col 28).ERROR: Duplicate id value 'zpxDuEwss146'. Location: Bundle.entry[2] (line 106, col 28).ERROR: Duplicate id value 'zpxDuEwss146'. Location: Bundle.entry[3] (line 134, col 28).
Environment
main
To Reproduce
Steps to reproduce the behavior:
create two resources with the same id (PUT) and ensure one references the other
perform a search for the one and _include the other
run the response through fhir validation
Expected behavior
a valid response bundle
Additional context
The problem is that we're using the non-unique resource ids to set Element.id for each Entry element. This is not typical and I'm not sure why we're doing that. If we're doing that for a reason, we could make it unique by using resource-type/id instead of just id.
The text was updated successfully, but these errors were encountered:
Describe the bug
While validating a search response that uses
_include
/_revinclude
to pull back different resource types with the same id, the searchset bundle fails base FHIR validation.Example response:
Which leads to this validation error:
Environment
main
To Reproduce
Steps to reproduce the behavior:
Expected behavior
a valid response bundle
Additional context
The problem is that we're using the non-unique resource ids to set Element.id for each Entry element. This is not typical and I'm not sure why we're doing that. If we're doing that for a reason, we could make it unique by using
resource-type/id
instead of just id.The text was updated successfully, but these errors were encountered: