Hi Bert, Thank you for proposing an interesting discussion whether http response status should be included to API result or not. I found this similar discussion on stackoverflow. http://stackoverflow.com/questions/942951/rest-api-error-return-good-practices
I think using response 404 code is simple and easy to implement API. But I partially agree with you that 404 error is not preferred because we have to distinguish "NO episode has been recorded" and "the record shows no episode in his/her life" in EHR as you mentioned. IMO the former should be 404 response and the latter should be 200 response with null flavor message. Shinji KOBAYASHI 2015-01-19 20:38 GMT+09:00 Bert Verhees <bert.verhees at rosa.nl>: > On 19-01-15 11:31, Birger Haarbrandt wrote: > > The medrecord openEHR server is also based on REST and worth looking at. > There was a lot to learn from for me as the API is pretty neat. > > > I will check that too, thanks for the links > > Bert > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
