Stream: implementers
Topic: PATCH strategies
Jens Villadsen (Mar 04 2019 at 12:34):
I'm looking for some input on PATCH strategies and best practices. My case for using PATCH is that I have some resources where some attributes should be editable by 3. party whereas some should not as some of the attributes should be considered readonly or governed by an authority. Is there any best practice for signaling that what is considered readonly or some best practices for building up whitelists or blacklists for what is editable through PATCH
Christiaan Knaap (Mar 04 2019 at 12:37):
My 2cts: Use FHIRPath PATCH with Parameters and state a profile for the Parameters.
Jens Villadsen (Mar 04 2019 at 12:39):
Hmmm ... that more or less looks like a custom operation
Last updated: Apr 12 2022 at 19:14 UTC
