FHIR Chat · Update and Create partial Records · implementers

Stream: implementers

Topic: Update and Create partial Records


view this post on Zulip Kenneth Chapple (May 04 2016 at 17:14):

Hi, can you provide a link to the documentation of the server-side behavior for updates and creates? For example, if I want to update just the name element on a Patient resource, so I send the "name" part only in an update request. The HAPI test server at fhirtest.unh.ca will update the name, but blank out the rest of the fields, rather than update the name and keep the rest of the fields as-is. Is this a bug, or is there a specific method for updating part of a record?

view this post on Zulip Grahame Grieve (May 04 2016 at 17:15):

Patch - something we're evaluating at the moment. See the patch track for this week's connectathon:

view this post on Zulip Grahame Grieve (May 04 2016 at 17:15):

http://wiki.hl7.org/index.php?title=FHIR_Connectathon_12

view this post on Zulip Kenneth Chapple (May 04 2016 at 17:42):

Great, thanks! I think I'll implement PATCH in our server and I'll track the progress on this, adjust our implementation accordingly as the standard matures.

view this post on Zulip James Agnew (May 04 2016 at 17:43):

I've been thinking I'd try and get PATCH done for this connectathon too. Don't suppose you're using HAPI and want to collaborate? :)

view this post on Zulip Kenneth Chapple (May 04 2016 at 17:46):

I would love to, but my job is to implement a FHIR interface to OpenEMR and we have chosen to use Laravel/PHP. I would be happy to collaborate in the sense of being a sounding-board for your ideas, and making suggestions, but wouldn't be able to contribute much in the way of development.

view this post on Zulip James Agnew (May 04 2016 at 17:50):

oooh interesting. sounds cool either way!

view this post on Zulip Richard Ettema (May 04 2016 at 18:22):

FYI - I have support for JSON Patch and corresponding tests deployed in our Touchstone testing platform - http://touchstone.com. I hope to have support for XML Patch in place for the Connectathon.

view this post on Zulip Grahame Grieve (May 04 2016 at 18:37):

have we said how we're going to do XML patch?

view this post on Zulip Richard Ettema (May 04 2016 at 18:41):

Based on email correspondence with Jenni early last week, she confirmed that she wanted to follow the RFC-5261 standard - http://tools.ietf.org/html/rfc5261.

view this post on Zulip Grahame Grieve (May 04 2016 at 18:41):

ok. so this is up on the wiki page?

view this post on Zulip Grahame Grieve (May 04 2016 at 18:41):

and do we have a set of test cases?

view this post on Zulip Richard Ettema (May 04 2016 at 18:42):

It's on the 201605_PATCH_Connectathon_Track_Proposal page.

view this post on Zulip Richard Ettema (May 04 2016 at 18:43):

Yes. I'm using what I created for the JSON Patch tests at Connectathon 11 and made XML Patch versions.

view this post on Zulip Richard Ettema (May 04 2016 at 18:44):

Here's an example of the XML Patch payload for updating a MedicationStatement.status value to 'completed':
<diff>
<replace sel="MedicationStatement/status/@value">completed</replace>
</diff>

view this post on Zulip Grahame Grieve (May 04 2016 at 18:45):

ok I'll look on the wiki, thanks

view this post on Zulip Richard Ettema (May 04 2016 at 18:47):

I also committed all the TestScripts and fixtures for both JSON and XML Patch to the FHIR trunk at http://gforge.hl7.org/svn/fhir/trunk/connectathons/MontrealMay2016/Connectathon12/Track-12-PATCH


Last updated: Apr 12 2022 at 19:14 UTC