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
{{ message }}
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
FHIR References store a relative URL to the item they are referencing. This is often of the form Patient/<patient_id_here>. The downside to this is that the reference field cannot be used in simple equality-based joins, since the relative prefix (like "Patient/" or "Encounter/" is present in the reference string.
Therefore, the we should consider additional fields in the Reference structure -- perhaps "reference_id" and "reference_type" -- where the former can be used for equality-based joins and the later defines the type of resource being referenced.
The text was updated successfully, but these errors were encountered:
Something like {id: .., resourceType:.. } makes sense to me. I think we might need to make it {resourceId: .., resourceType:.. }, since the "id" field is reserved for the ancestor Element. [1]
If {resourceId: .., resourceType:.. } seems okay, I'll create a PR with that change.
FHIR References store a relative URL to the item they are referencing. This is often of the form Patient/<patient_id_here>. The downside to this is that the reference field cannot be used in simple equality-based joins, since the relative prefix (like "Patient/" or "Encounter/" is present in the reference string.
Therefore, the we should consider additional fields in the Reference structure -- perhaps "reference_id" and "reference_type" -- where the former can be used for equality-based joins and the later defines the type of resource being referenced.
The text was updated successfully, but these errors were encountered: