CH ATC (R4), published by eHealth Suisse. This guide is not an authorized publication; it is the continuous build for version 3.3.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/ehealthsuisse/ch-atc/ and changes regularly. See the Directory of published versions

Volume 1 - Integration Profiles

Overview

This profile defines the audit trail consumption requirements a community has to provide for a patient’s audit trail.

The profile CH:ATC defines and precises the actors and Retrieve Audit Event [ITI-81] of the IHE ITI Supplement Add RESTful Query to ATNA and defines the content of the Audit Messages. The different types of the Audit Messages are based on the requirements for Document and Access Policy management as well as the entry of healthcare professionals into a group in order to achieve the Swiss regulation needs on the audit trail access by patients. These Audit Event types differ from the Audit Events which have also to be logged according to the ATNA requirements.

Figure 1: CH:ATC Overview within the Swiss EPR circle of trust

Each community shall provide one endpoint to a Patient Audit Record Repository which can be queried according to the Retrieve Audit Event [ITI-81] RESTful Query transaction. A reference community shall implement a Patient Audit Consumer which will query all Patient Audit Record Repositories, aggregate the results and provide it to the patient.

How the Patient Audit Record Repository generates or collects the specified Audit Events within the community is outside the scope of this profile.

Actors, Transactions and Content Modules

Figure 2 shows the actors directly involved in the CH:ATC Profile and the relevant transactions between them. If needed for context, other actors that may be indirectly involved due to their participation in other related profiles are shown in dotted lines.

Figure 2: CH:ATC Actor diagram

Table 1 lists the transactions for each actor directly involved in the CH:ATC Profile. To claim compliance with this Profile, an actor shall support all required transactions (labeled “R”) and may support the optional transactions (labeled “O”).

Actors	Transactions	Initiator or Responder	Opt	Reference
Patient Audit Consumer	Retrieve Audit Event [ITI-81]	Initiator	R	Patient Audit Consumer
Patient Audit Record Repository	Retrieve Audit Event [ITI-81]	Responder	R	Patient Audit Record Repository

Table 1: CH:ATC Profile - Actors and Transactions

Actor Descriptions and Actor Profile Requirements

The actors defined in this profile are based on the IHE ITI TF-2 and the IHE ITI Supplement Add RESTful Query to ATNA actors. This section documents any additional requirements on the profile’s actors required in the Swiss EPR context.

Patient Audit Record Repository

For the actor Patient Audit Record Repository the actor Audit Record Repository in IHE ITI Supplement Add RESTful Query to ATNA is relevant.

The Patient Audit Record Repository shall support the Retrieve Audit Message Option from the Audit Record Repository (TODO leere section IHE ITI TF-1, chapter 9.2.3) with the search capabilities as defined in IHE ITI TF-2, chapter 3.81 and the Audit Message Formats defined in Volume 3 - Content Profiles.

Patient Audit Consumer

For the actor Patient Audit Consumer the actor Audit Consumer in IHE ITI Supplement Add RESTful Query to ATNA is relevant.

The Patient Audit Consumer queries a Patient Audit Record Repository for Audit Events defined by this profile. The Patient Audit Consumer shall support the Retrieve Audit Message Option from the Audit Consumer (TODO leere section IHE ITI TF-1, chapter 9.2.3).

The Patient Audit Consumer should filter duplicate AuditEvents for display (e.g. Document Retrieval Audit Event for the same document access are in multiple Patient Audit Record Repositories, because the requesting and responding community need to make the AuditEvent available).

Subsequent processing like translation of the coded elements into the users preferred language and display of the query result is not defined in this profile.

Integration Profile Options

CH:ATC Actor	Option name
Patient Audit Consumer	Aggregate Audit Message Option
Patient Audit Record Repository	-

Table 2: Actors and Options

The aggregate Audit Message Options allows the Patient Audit Consumer to aggregate results from multiple Patient Audit Record Repositories. A reference community shall support at least one Patient Audit Consumer with this Option. If a Patient Audit Record Repository does not respond, an OperationOutcome with a severity warning shall be added to the aggregated results indicating the Patient Audit Record Repository of the community that does not respond.

Actor Groupings

An actor from this profile (Column 1) shall implement all of the required transactions and/or content modules in this profile in addition to all of the requirements for the grouped actor.

CH:ATC Actor	Grouping Condition	Actor to be grouped with	Reference
Patient Audit Consumer	Required	ATNA - Secure Node	Amendment 1 of Annex 5 EPRO-FDHA
	Required	CT - Time Client	IHE ITI TF-1
	Required	IUA - Authorization Client	IHE ITI Suppl IUA
	Optional	CH:CPI - CPI Consumer	Amendment 2.3 of Annex 5 EPRO-FDHA
Patient Audit Record Repository	Required	ATNA - Secure Node	Amendment 1 of Annex 5 EPRO-FDHA
	Required	CT - Time Client	IHE ITI TF-1
	Required	CH:ADR - Authorization Decision Consumer	Amendment 2.1 of Annex 5 EPRO-FDHA
	Required	IUA - Resource Server	IHE ITI Suppl IUA

Table 3: Actor Grouping

Section Security Considerations describes the groupings required for security considerations.

Overview - Use Cases

Activities related to the EPR are audited for specific document and access policy management events as well as entry events of healthcare professionals into a group and stored in the communities.

This profile supports the following Use Cases:

1. A patient can request protocols of the activities related to his EPR.
2. A patient representative can request a protocol of the activities related to the patients delegated EPR.

Security Considerations

The transaction is used to exchange sensitive information and requires authentication and authorization. This profile requires all actors to be grouped with Secure Node or Secure Application implementing the “STX: TLS 1.2 floor using BCP195 Option” defined in the IHE ITI TF-2, chapter 3.19.6.2.3.

Access control shall be implemented by grouping the CH:ATC Audit Consumer and Audit Record Repository with the Authorization Client and Resource Server from the IUA trial implementation profile using the SAML Token option (see IHE ITI Supplement IUA, chapter 3.72.4.3.2). As defined therein, the CH:ATC Audit Consumer and Audit Record Repository shall implement the Incorporate Authorization Token [ITI-72] transaction to convey the XUA token.

The CH:ATC Patient Audit Record Repository shall be grouped with CH:ADR, i.e. the CH:ATC Patient Audit Record Repository shall use the CH:ADR Authorization Decision Request transaction to authorize the transaction and enforce the authorization decision retrieved from CH:ADR Authorization Decision Response.