Basic Audit Log Patterns (BALP)
1.1.4 - Trial-Implementation
This page is part of the IHE Basic Audit Log Patterns (BALP) (v1.1.4: Publication) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: https://profiles.ihe.net/ITI/BALP/ValueSet/UserAgentTypesVS | Version: 1.1.4 | |||
| Active as of 2025-10-31 | Computable Name: UserAgentTypesVS | |||
AuditEvent.agent.type values holding OAuth/SAML identified user. Note that user is not just users, but representes the higest agent responsible for triggering the activity being recorded in the AuditEvent.
Often this agent also has a type coding that is more specific to the transaction and the direction of the transaction.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
This value set includes codes based on the following rules:
https://profiles.ihe.net/ITI/BALP/CodeSystem/UserAgentTypes version 📦1.1.4urn:ihe:iti:xca:2010 version Not Stated (use latest from terminology server)
| Code | Display |
| homeCommunityId | IHE homeCommunityId |
No Expansion for this valueset (not supported by Publication Tooling)
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |