Stream: implementers
Topic: Audit attributes like created by in a resource
Vijay Thangavelu (Sep 24 2018 at 21:08):
Team,
We have use-case to record and display the information of who created a resource and when it got created, also when the record was last updated and by which user?
basically, looking for below 4 attributes which usually performed in a relational model,
createdBy
createdDate
updatedBy
updatedDate -- meta._lastUpdated
The options what we have right now would be, to go for the history/1 to get the created date and for createdBy/updatedBy, we have get it from the Audit trail for each resource which will be very expensive and not efficient.
We are thinking, can this be part of the each resource itself in addition to _lastUpdated, we would like to here others thought and also would like to see, if we have any other suggestions to it.
Thanks,
Vijay
Abbie Watson (Sep 24 2018 at 21:11):
We've definitely considered bringing this up as an extension or change for the Meta resource. I suspect there is general widespread support, as long as it's properly scoped; things are optional, etc. (Some systems may simply not track all of that data.)
Grahame Grieve (Sep 24 2018 at 22:15):
4 attributes which usually performed in a relational model,
I do not believe that 'usually' is appropriate in that sentence. I've certainly seen that, but i've seen many variations
Grahame Grieve (Sep 24 2018 at 22:16):
A particular approach that meets your particular requirements would no doubt be more efficient for you, but I think that it would be less efficient for the general case
Grahame Grieve (Sep 24 2018 at 22:17):
though you always have extensions
Vijay Thangavelu (Sep 24 2018 at 22:39):
Thanks @Abigail Watson @Grahame Grieve , Yes we can go with extension for Meta which would be helpful, we thought this will be basic model for most of the implementations if not all.
@Radu Craioveanu - do you have any other thoughts/question on this context.
@Lloyd McKenzie
Lloyd McKenzie (Sep 24 2018 at 23:54):
I'm reluctant to add something as an extension which is clearly already covered by core - via the Provenance resource. The notion of "created" is a tricky one too. Are you interested in the creation of the business object or the creation of the record on that particular server? (The two aren't necessarily the same).
Vijay Thangavelu (Sep 25 2018 at 02:41):
primarily creation/updating of the record on that particular server.
We do use Provenance in one context when physician explicitly signing (approving an object) but not for every updates.
Brian Postlethwaite (Sep 25 2018 at 09:11):
We use auditevent
Last updated: Apr 12 2022 at 19:14 UTC
