Basic Audit Log Patterns (BALP)
1.1.4-current - ci-build International flag

Basic Audit Log Patterns (BALP), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.1.4-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.BasicAudit/ and changes regularly. See the Directory of published versions

ValueSet: RESTful objects role in the event

Official URL: https://profiles.ihe.net/ITI/BALP/ValueSet/RestObjectRoles Version: 1.1.4-current
Active as of 2024-02-15 Computable Name: RestObjectRoles

The role that the given Object played in the Audit Event recorded

References

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/object-role
    CodeDisplayDefinition
    4Domain ResourceA logical object related to a health record event. This is any healthcare specific resource (object) not restricted to FHIR defined Resources.
    3ReportThis 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.
    20JobAn order, task, work item, procedure step, or other description of work to be performed; e.g. a particular instance of an MPPS.

 

Expansion

Expansion based on codesystem AuditEventEntityRole v0.5.0 (CodeSystem)

This value set contains 3 concepts.

CodeSystemDisplayDefinition
  4http://terminology.hl7.org/CodeSystem/object-roleDomain Resource

A logical object related to a health record event. This is any healthcare specific resource (object) not restricted to FHIR defined Resources.

  3http://terminology.hl7.org/CodeSystem/object-roleReport

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.

  20http://terminology.hl7.org/CodeSystem/object-roleJob

An order, task, work item, procedure step, or other description of work to be performed; e.g. a particular instance of an MPPS.

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