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
We need to abstract how references are stored in a database. Most implementations do pre-parse references and store resourceType and id separately (in our spec on the storage layer, we suggest using {type, sof_id} elements for that:
subject: {reference: 'Patient/pt-1'}// translated into
subject: {type: 'Patient',sof_id: 'pt-1'}
To support this abstraction, we need functions in fhirpath to get id and type:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We need to abstract how references are stored in a database. Most implementations do pre-parse references and store resourceType and id separately (in our spec on the storage layer, we suggest using
{type, sof_id}
elements for that:To support this abstraction, we need functions in fhirpath to get
id
andtype
:Beta Was this translation helpful? Give feedback.
All reactions