Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension of the Profile “Security Retrieve” #177

Open
JohnMoehrke opened this issue Feb 15, 2022 · 1 comment
Open

Extension of the Profile “Security Retrieve” #177

JohnMoehrke opened this issue Feb 15, 2022 · 1 comment
Assignees
Labels
Dev-M Development effort is Medium Review-M Committee Review effort is Medium Testing-M Testing Plan Development is Medium

Comments

@JohnMoehrke
Copy link
Contributor

JohnMoehrke commented Feb 15, 2022

  1. Proposed Work Item: Extension of the Profile “Security Retrieve”

Proposal Editor: Martin Smock, eHealth Suisse
Work Item Editor: Martin Smock, eHealth Suisse
Date: 9-Feb-2022
Version: 1.0
Domain: IHE ITI

  1. The Problem

As mentioned in the IHE Access Control Whitepaper, IHE provides profiles for most of the actors and transctions required for access control:

  • EUA for Kerberos based User Authentication;
  • XUA for Authorization Assertions based on SAML 2.0
  • BPPC for implementing Policy Administration Points based on XDS.b infrastructure;

In the years after publication of the Access Control Whitepaper, additional supplements were published focusing on some additional aspects of access control:

  • HPD my be used as Policy Information Point by the Policy Decision Point;
  • APPC for implementing Policy Administration Points in XDS.b infrastructure based on the XACML 2.0 standard;
  • IUA for Authorization Assertions based on OAuth and JWT;
  • SeR for implementing Policy Enforcement and Policy Decision Points in XDS.b for XDS.b repositories.

While most of the profiles and supplements are generic and applicable for access control for many use cases, the Secure Retrieve (SeR) supplement is not. The messages defined in the supplement were designed for policy enforcement of an XDS.b repostory and the application of the profile is therefore limited to the document retrieval use case only. Currently the profile cannot be aplied to policy enforcement in other use cases (e.g. PIX) and other components of an affinity domain or in cross enterprise scenario.

The intention of the work item is to rework the SeR supplement to support other use cases and increase its applicability for policy enforcement as part of the access control infrastructure. The goal is to rework the SeR supplement to be extensible (i.e. definition of additional use cases and national extensions), preserving backward compatibility, so that no changes will be required in current SeR implementations.

  1. Key Use Case

The key use cases to be adressed by the work item are:

  • Policy enforcement for access control in retrieving patient personal identifiable information (PDQ, PDQm, etc.);
  • Policy enforcement for access control in retrieval of document metadata (Registry Stored Query, MHD, etc.);
  • Policy enforcement for access control in retrieval in other IHE or non IHE Actors of an affinity domain or in cross community scenarios.
  1. Standards & Systems

The extension of SeR shall not introduce new standards. The work item extends the current version of the SeR supplement using the XACML 2.0 standard, the current version is based upon.

  1. Discussion

Remark (M. Smock):

  • The work item is motivated by requirements of the swiss national EPR, where the legal regulations require policy enforcement for access control not only for document retrieval. The current implementation of the Swiss EPR uses a proprietary specification (ordinance), which has much in common with the SeR supplement, but applies to more use cases. The work item on the one hand would allow us to switch to a swiss national extension, on the other hand we expect the international community could benefit from the swiss experience with policy enforcement.

  • We expect the work item to be a low hanging fruit, since:
    o eHealth Suisse already mandated a specialist to perfom the gap analysis and to propose the chnages required for the work item (see attached word document with tracked changes).
    o eHealth Suisse reserved budget in 2022 for a specialist to participate in the ITI TC meetings for the work item and to finalize the update of the SeR supplement.

@JohnMoehrke JohnMoehrke created this issue from a note in ITI Project Planning (Under assessment by planning) Feb 15, 2022
@JohnMoehrke JohnMoehrke changed the title SeR advance Extension of the Profile “Security Retrieve” Feb 15, 2022
@JohnMoehrke
Copy link
Contributor Author

@JohnMoehrke JohnMoehrke added Review-M Committee Review effort is Medium Dev-M Development effort is Medium Testing-M Testing Plan Development is Medium labels Mar 15, 2022
@JohnMoehrke JohnMoehrke moved this from Under assessment by planning to Planning Assessed Work Items in ITI Project Planning Mar 15, 2022
@JohnMoehrke JohnMoehrke moved this from Planning Assessed Work Items to In development by Tech in ITI Project Planning Apr 28, 2022
@JohnMoehrke JohnMoehrke moved this from In development by Tech to Planning Assessed Work Items in ITI Project Planning Apr 28, 2022
@JohnMoehrke JohnMoehrke moved this from Planning Assessed Work Items to In development by Tech in ITI Project Planning Apr 28, 2022
@JohnMoehrke JohnMoehrke moved this from In development by Tech to Public Comment in ITI Project Planning Jul 22, 2022
@JohnMoehrke JohnMoehrke moved this from Public Comment to In Trial Implementation in ITI Project Planning Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dev-M Development effort is Medium Review-M Committee Review effort is Medium Testing-M Testing Plan Development is Medium
Projects
Status: Published (e.g. Trial Implementation)
ITI Project Planning
  
Published (e.g. Trial Implementation)
Development

No branches or pull requests

2 participants