Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

References #4

Open
niquola opened this issue Jun 16, 2017 · 0 comments
Open

References #4

niquola opened this issue Jun 16, 2017 · 0 comments

Comments

@niquola
Copy link
Member

niquola commented Jun 16, 2017

Problem

All implementers parse strings to work with references.
There is no clear distinction between local & external refs.
It would be nice to have refs more structured:

// for local refs
{
   "subject": {"resourceType": "Patient", "id": "pt-1"}
}
// for external

{
   "subject": {"uri": "http://otherserver/Patient/pt-1"}
}

This apprach also play well with inlining resolved references:

{ "subject": {"resourceType": "Patient", "id": "pt-1"} }

// after inline

{ "subject": {"resourceType": "Patient", "id": "pt-1", "name": [{....}], ....} }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant