FHIR Chat · Resource to represent a change request · implementers

Stream: implementers

Topic: Resource to represent a change request


view this post on Zulip Rik Smithies (Jun 05 2018 at 00:20):

I have a use case where a change request is submitted about some FHIR data. An example would be to propose the addition of a new contraindication for a medicine (with a named proposer, supporting evidence etc). The idea being that these changes are manually governed. The proposed changes are reviewed (by a human) and the changes may be approved or rejected. What resource (or operation etc) could represent a request to change data?

view this post on Zulip Grahame Grieve (Jun 05 2018 at 01:07):

so a long time ago, I wrote this:

view this post on Zulip Grahame Grieve (Jun 05 2018 at 01:08):

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

view this post on Zulip Grahame Grieve (Jun 05 2018 at 01:08):

but now I read it, I see it's a slightly different

view this post on Zulip Grahame Grieve (Jun 05 2018 at 01:09):

so there's a the ability to have a patch resource that describes changes to a resource.

view this post on Zulip Grahame Grieve (Jun 05 2018 at 01:09):

and the standard tools can generate the patch for a user

view this post on Zulip Lloyd McKenzie (Jun 05 2018 at 02:05):

The resource to request state changes is Task. It would presumably make sense to use it for updates too, though there's no mechanism to easily convey what changes are desired.

view this post on Zulip Rik Smithies (Jun 05 2018 at 10:24):

Thanks Grahame, that does look a lot like our use case actually. I think in that case the Questionnaire would say "What do you want to change", "how do you want to change it" and "why is it necessary" etc. We would need more than just a list of deltas, because we need things like rationale for change, and some sort of status (review steps completed) etc. The process itself wants to be trackable, which points to having a resource rather than just something throwaway like a patch structure. Questionnaire is long lived, being a resource, but has the disadvantage of being very open, and not structured around change/review processes as such. OTOH patch is very specific to changes but it not process oriented.

Perhaps we need Questionnaire, or patch, but with another resource to track the process. So I am now wondering about Task or perhaps ProcessRequest.

[as I sent this I noticed I had not seen your reply Lloyd, seems to be along similar lines]


Last updated: Apr 12 2022 at 19:14 UTC