Stream: implementers
Topic: fhirpatch
nicola (RIO/SS) (Oct 19 2018 at 09:49):
@Grahame Grieve who is working on fhirpatch. I do not think Parameter resource is a good way to do it :/ Why not specialised resource?
Lloyd McKenzie (Oct 19 2018 at 14:59):
Is the concern verbosity? Something else?
nicola (RIO/SS) (Oct 19 2018 at 15:02):
I think, patch is a quite important operation to have dedicated resource type :)
Lloyd McKenzie (Oct 19 2018 at 15:03):
Dedicated resources aren't created on the basis of importance, they're created on the basis of implementer need - can you explain why you feel a specialized resource would be desirable?
nicola (RIO/SS) (Oct 19 2018 at 15:04):
Because patch has a structure and we need to validate it - to properly apply patch
nicola (RIO/SS) (Oct 19 2018 at 15:06):
I think we can express any FHIR resource as a Parameter :) and it's very easy to abuse it
Lloyd McKenzie (Oct 19 2018 at 15:08):
Parameters get validated against their operation. You can certainly express anything using Parameters, but for custom operations, there's no real choice. We can't define custom resources on the fly because the schemas, reference implementations, etc. won't be able to handle them.
Grahame Grieve (Oct 19 2018 at 20:37):
we can define them in the spec. I'm not sure that it's worth it... but discussion moved to here: https://chat.fhir.org/#narrow/stream/4-implementers/subject/FHIRPath.20Patch
Glory Kim (Dec 05 2019 at 23:52):
for fhirpatch is the path parameter required? I see that it is used for all of the types add, insert, delete, replace, and move - but am not seeing whether it is strictly required or can be optional
Grahame Grieve (Dec 05 2019 at 23:57):
I don't see how it could have any meaning with out a path
Glory Kim (Dec 05 2019 at 23:58):
is it safe to assume that path should be required and not optional?
Grahame Grieve (Dec 05 2019 at 23:59):
I think so. you could make a task for us to clarify this in the next version
Last updated: Apr 12 2022 at 19:14 UTC
