Stream: implementers
Topic: Connectathon Patient Stream
David Hay (May 07 2016 at 10:34):
Welcome to the stream to support the patient track at Connectathon 12
Cooper Thompson (May 07 2016 at 15:25):
When a server receives a Patient Create interaction, and determines that the POSTed payload matches an existing patient - if the server opts to interpret the create as an update (i.e. sort of like a server-side conditional create), should the server return 200-success (as is appropriate for an update) or 201-created (as appropriate for a create).
Grahame Grieve (May 07 2016 at 16:55):
is there any circumstance under which the difference matters to a client?
David Hay (May 07 2016 at 17:15):
Hard to imagine why it would...
Cooper Thompson (May 07 2016 at 17:23):
I suppose it might matter if the client knows that the two patients are "known non-duplicates" (i.e. twins with similar names). In that case, a 200 would indicate that the server may have not been smart enough to recognize a known non-duplicate. Though instead of addressing that via HTTP status codes, the solution to that problem may be allowing clients to indicate known non-dups via an included reference
Grahame Grieve (May 07 2016 at 17:24):
once you've got to this point, you need to stop thinking about the RESTful operations and start thinking about choreography and the $match operation
David Hay (May 07 2016 at 21:25):
Hi guys - didn't hear too much from you so assume all went well! Would be great to have a quick update on progress (perhaps just a comment on this chat) - and is there anyone who would like to present tomorrow? We'll have time for one only I'm afraid...
David Hay (May 08 2016 at 13:48):
Does anyone have anything they particularly want to present? Given that these are relatively simple use cases, I'm thinking that we let some of the other tracks have the time...
David Hay (May 08 2016 at 13:49):
And does anyone have anything in particular that they wish me to talk about in my Track Lead preso?
Last updated: Apr 12 2022 at 19:14 UTC
