-
Type:
Change Request
-
Resolution: Unresolved
-
FHIR Core (FHIR)
-
R4
-
AuditEvent
-
Correction
It's not clear why a sub-type is necessary. Multiple codings at different levels of granularity can be sent as codings within AuditEvent.type, so generally speaking, there's no need for a sub-type. We have a pattern where there's a code that specifieds the detail of what's happening and then a separate 'category' element thtat categorizes the type of action in a variety of possibly orhogonal ways - but that's not what's happening here.
(Comment 2 - imported by: Ron G. Parker)
- is voted on by
-
BALLOT-17477 Negative - Ron G. Parker : 2021-May-FHIR R5 Comment
- Balloted
-
BALLOT-18322 Negative - Joel Francis : 2021-May-FHIR R5 Comment
- Balloted
-
BALLOT-18544 Negative - Cindy Jiang : 2021-May-FHIR R5 Comment
- Balloted