Implementation Guide
ePA Basisfunktionalitäten
Version 1.3.2 - release

## ValueSet: EPA AuditEvent Agent Type User

Official URL: https://gematik.de/fhir/epa/ValueSet/epa-audit-event-agent-type-user-vs | Version: 1.2.0
Active as of 2025-09-12 | Computable Name: EPAAuditEventAgentTypeUserVS
Copyright/Legal: gematik GmbH / Dieses Artefakt ist lizenziert unter Apache License, Version 2.0.

EPA agent type (user) for AuditEvent

References

- EPA AuditEvent

### Logical Definition (CLD)

This value set includes codes based on the following rules:

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/v3-RoleClass` version 📦5.0.0

  Code | Display | Definition
  PROV | healthcare provider | An Entity (player) that is authorized to provide health care services by some authorizing agency (scoper).
  PAT | patient | A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper). *Usage Note:* Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship.
  PAYOR | invoice payor | The role of an organization that undertakes to accept claims invoices, assess the coverage or payments due for those invoices and pay to the designated payees for those invoices. This role may be either the underwriter or a third-party organization authorized by the underwriter. The scoping entity is the organization that underwrites the claimed coverage.

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/v3-ParticipationType` version 📦6.0.0

  Code | Display | Definition
  CST | custodian | An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.).

- Include these codes as defined in `https://gematik.de/fhir/epa/CodeSystem/epa-auditevent-agent-type-client-cs` version 📦1.2.0

  Code | Display
  OMBUDSOFFICE | Ombuds Office

### Expansion

This value set expansion contains 5 concepts.

System | Code | Display | Definition | JSON | XML
`http://terminology.hl7.org/CodeSystem/v3-RoleClass` | PROV | healthcare provider | An Entity (player) that is authorized to provide health care services by some authorizing agency (scoper). |  |
`http://terminology.hl7.org/CodeSystem/v3-ParticipationType` | CST | custodian | An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.). |  |
`http://terminology.hl7.org/CodeSystem/v3-RoleClass` | PAT | patient | A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper). Usage Note: Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship. |  |
`http://terminology.hl7.org/CodeSystem/v3-RoleClass` | PAYOR | invoice payor | The role of an organization that undertakes to accept claims invoices, assess the coverage or payments due for those invoices and pay to the designated payees for those invoices. This role may be either the underwriter or a third-party organization authorized by the underwriter. The scoping entity is the organization that underwrites the claimed coverage. |  |
`https://gematik.de/fhir/epa/CodeSystem/epa-auditevent-agent-type-client-cs` | OMBUDSOFFICE | Ombuds Office |  |  |

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