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/RestObjectRoles | Version: 1.1.4 | |||
| Active as of 2025-10-31 | Computable Name: RestObjectRoles | |||
The role that the given Object played in the Audit Event recorded
References
http://terminology.hl7.org/CodeSystem/object-role version 📦1.1.0| Code | Display | Definition |
| 4 | Domain Resource | A logical object related to a health record event. This is any healthcare specific resource (object) not restricted to FHIR defined Resources. |
| 3 | Report | This object is any kind of persistent document created as a result of the event. This could be a paper report, film, electronic report, DICOM Study, etc. Issues related to medical records life cycle management are conveyed elsewhere. |
| 20 | Job | An order, task, work item, procedure step, or other description of work to be performed; e.g. a particular instance of an MPPS. |
Expansion performed internally based on codesystem AuditEventEntityRole v1.1.0 (CodeSystem)
This value set contains 3 concepts
| System | Code | Display (en) | JSON | XML |
http://terminology.hl7.org/CodeSystem/object-role | 4 | Domain Resource | ||
http://terminology.hl7.org/CodeSystem/object-role | 3 | Report | ||
http://terminology.hl7.org/CodeSystem/object-role | 20 | Job |
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 |