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

Default or server-side generated values #20

Open
ErikSundvall opened this issue Jul 3, 2016 · 2 comments
Open

Default or server-side generated values #20

ErikSundvall opened this issue Jul 3, 2016 · 2 comments
Milestone

Comments

@ErikSundvall
Copy link
Member

During https://openehr.atlassian.net/wiki/display/spec/2016-06-30+REST+API+Meeting+notes I believe that @bjornna mentioned that one of their implementations added values (for example time-stamps) on the server-side if a mandatory field was missing.

Another option is to throw an error if mandatory things are missing. But some things (for example some timestamps) can be good to have an option to add server-side...

Yet another option could be to have some values/flags (either as metadata in the call header or some other place or inlined at places in the body) to explicitly ask the server to generate missing mandatory (and even some optional) values. A value of @now could for example be replaced with the server's current time.

Let the discussion begin...

@ppazos
Copy link
Contributor

ppazos commented Oct 17, 2016

@ErikSundvall I should take a look to the code to have a full list of values injected by the server. One I remember is the composition uid, if that doesn't come from the client that commits the composition/version, the server generates and assigns an UUID to the composition.uid.

@bostjanl
Copy link
Contributor

bostjanl commented Nov 5, 2018

For the moment we only use canonical openEHR JSON format where the only value that is set by the server is UID (if not provided in the data).

@bostjanl bostjanl added this to the 1.1.0 milestone Nov 5, 2018
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

3 participants