Stream: Security and Privacy
Topic: AuditEvent.outcomeDesc
Alexander Zautke (Nov 27 2019 at 12:44):
Could someone elaborate on the reasoning behind the choice that AuditEvent.outcome and AuditEvent.outcomeDesc are two separate fields instead of making AuditEvent.outcome a CodeableConcept?
Grahame Grieve (Nov 27 2019 at 12:45):
legacy, as far as I know
Grahame Grieve (Nov 27 2019 at 12:46):
but I do not think there is any need for more than one code
Alexander Zautke (Nov 27 2019 at 12:49):
Ok, thanks. It wasn't about having multiple codes, but more about keeping the text and the code together.
Grahame Grieve (Nov 27 2019 at 12:49):
I understand. but CodeableConcept comes with multiple codes...
Alexander Zautke (Nov 27 2019 at 12:56):
Yeah, I see the issue. Though I must say that I really dislike the ValueSet here, it requires in most of my use cases to have some code to map HTTP Return Codes to this ValueSet
Grahame Grieve (Nov 27 2019 at 12:59):
I do the same. Maybe you could make a task to improve it, or publish standard mappings in a ConceptMap?
Alexander Zautke (Nov 27 2019 at 12:59):
So in most cases we map the the HTTP response to AuditEvent.outcome and store the original return code in AuditEvent.outcomeDescp
Alexander Zautke (Dec 09 2019 at 11:41):
Added https://jira.hl7.org/browse/FHIR-25287
Last updated: Apr 12 2022 at 19:14 UTC
