Stream: implementers
Topic: OperationOutcome with timestamp
RB Johnson (Nov 02 2021 at 18:13):
Has anyone else had to include timestamps in an operation outcome?
I'm working on the best place to put one since their isn't a field explicitly for it. Currently I'm going with adding it as the value for meta.lastUpdated.
What are people's thoughts on the best place to put this value?
Grahame Grieve (Nov 03 2021 at 00:23):
well. meta.lastUpdated or in the http headers
Lloyd McKenzie (Nov 03 2021 at 02:34):
Or an extension. What is your objective?
RB Johnson (Nov 03 2021 at 21:49):
The objective is to have a timestamp connected to errors generated in the implementation so that it is easier to connect to other logs and events when debugging. I considered an extension, but wanted something that would be easier for a consumer to use.
Grahame Grieve (Nov 03 2021 at 21:53):
a few of us a using a request identifier in the response log for that - if people ask for help, they have to quote the id we put in the response as part of their question.
Grahame Grieve (Nov 03 2021 at 21:53):
Cerner and Epic both do, I think, as does test.fhir.org
Last updated: Apr 12 2022 at 19:14 UTC
