Stream: cds hooks
Topic: uuid
Lloyd McKenzie (Aug 13 2018 at 04:39):
Why is there a uuid on Suggestion but not on the base Card? Advice/statements provided just in Card.summary or Card.detail or even Card.link can be just as important for logging purposes as that provided in Card.summary
Robert Sax (Aug 13 2018 at 10:40):
Are you suggesting something that basically says the Card was seen? If so, I agree it would be useful.
Lloyd McKenzie (Aug 13 2018 at 14:14):
I hadn't been suggesting that, though that's not a bad idea either. All I was looking for was a mechanism to be able to correlate logs for the same hook event.
Isaac Vetter (Aug 13 2018 at 15:52):
Morning, Lloyd, the original reason is that uuid was specifically added to support the "analytics" functionality that we took out of the 1.0 spec -- in which the EHR pings the CDS service when a suggestion has been taken.
Whle a unique card id would be useful for logging, it seems like a useful and optional feature.
Lloyd McKenzie (Aug 13 2018 at 16:12):
I'm fine with it being optional - IGs or partner agreements can make it required if need-be. Should I submit a github item?
Brian Postlethwaite (Aug 13 2018 at 23:14):
Should we be using the same values as suggested here?
http://build.fhir.org/http.html#custom
Kevin Shekleton (Aug 15 2018 at 13:35):
@Lloyd McKenzie - You (or anyone else) is always more than welcome to submit a GitHub issue :smile:
Lloyd McKenzie (Aug 15 2018 at 14:36):
https://github.com/cds-hooks/docs/issues/403
Isaac Vetter (Aug 16 2018 at 04:00):
Hey Lloyd, it seems like simple native auditing ought not to require interop spec changes.
Although, a card-level guid/uuid would no doubt simply auditing, it doesn't seem to be a necessary field. Do you agree?
Last updated: Apr 12 2022 at 19:14 UTC
