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
When both logical and literal references are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference, if they understand how to resolve the logical reference.
So this does make sense, but it would still be nice to have it preserved.
To Reproduce
Create a resource referencing a different resource with both (or just setting the Reference.identifer might do the trick), like in the example above
POST it to the Pathling Server to have it encoded
Observe that the encoded resource no longer contains the Reference.identifier
Expected behavior
Both the Reference.reference and Reference.identifier should be preserved when encoding.
This is definitely nothing critical, it's just a helpful extra-information we include in resources to make identification easier.
The text was updated successfully, but these errors were encountered:
Describe the bug
We create resources that set both
Reference.reference
andReference.identifier
for references toPatient
andEncounter
resources.For example:
However, while
Condition.subject.reference
is encoded correctly, theCondition.subject.identifier
is ignored. The following SQL:returns only:
The FHIR spec https://hl7.org/fhir/R4B/references.html#logical states:
So this does make sense, but it would still be nice to have it preserved.
To Reproduce
Reference.identifer
might do the trick), like in the example aboveReference.identifier
Expected behavior
Both the
Reference.reference
andReference.identifier
should be preserved when encoding.This is definitely nothing critical, it's just a helpful extra-information we include in resources to make identification easier.
The text was updated successfully, but these errors were encountered: