2.14.12 Search Response
entry.resource.id (line 27) - Note that in some bundles, the
entry.resource.id must be unique in the bundle
For a bundle with different types, it cannot guarantee that the native (local) id is unique across types: a Patient id might coincidentally be the same as a Visit id (although this is unlikely). Is this a real issue?