As per comments on AuditEvent.type, this value set is not appropriate for an 'extensible' binding. It's in even worse shape than the 'type' binding because it's even larger, making it that much harder for implementers to map to these codes. Every implementer code needs to map to exactly one of these concepts, which is not possible given the overlap in meaning between the concepts. In general, "detail" codes should never have required or extensible bindings in FHIR. This must be replaced with an example binding to a small value set of selected codes showing the range of the element, given that no intensional binding would have appropriate scope.

(Comment 3 - imported by: Ron G. Parker)