Cross-Enterprise User Assertion (XUA) Profile

Introduction

This is a draft of the Cross-Enterprise User Assertion Profile supplement to the IT Infrastructure Technical Framework. This draft is a work in progress, not the official supplement or profile. Content for this profile have been vetted to be used to provide trustable user identity for the use in the XDS Stored Query and XDS Web Services Retrieve Transactions. The final content profile can only be determined after technical assessment by the full IT Infrastructure Technical Committee.

There are transactions defined by IHE that cross enterprise boundaries. The existing IHE mechanisms to provide an authenticated user identity (EUA) will not function in cross-enterprise transactions. Further in a cross-enterprise environment it is more likely that the transactions will be going between two enterprises that maintain their own independent user directories (PWP). This problem is the same focus of the OASIS-SAML standard. This standard has received much attention and support by the security and the platforms industry. This standard allows for centralized user directory, but also supports the more powerful federation of user directories. This standard supports many methods of user authentication (password, biometrics, smartcard) and can include details about the method(s) used.

The solution proposed is to leverage SAML and the various profiles from W3C, OASIS, and WS-I. In this way we will be able to take advantage of the vast experience of the communities outside of healthcare standards. This profile will be leveraging the experience of a few programs around the globe that have started work with SAML in healthcare. Most of these projects are applying SAML to XDS as we expect to be doing in the first year.

Discussion about the creation of this profile can be found at Cross-Enterprise User Assertion - Discussion

Profile Abstract

The Cross-Enterprise User Assertion (XUA) Profile provides a trustable user identity for transactions that cross enterprise boundaries. The user identities may be centrally managed, or distributed.

Glossary

XUA

Cross-Enterprise User Assertion (Formerly Cross-Enterprise User Authentication)

Issue Log

Open Issues

1. Issue 1

Systems

Typical systems involved:

• XDS Document Consumers
• XDS Registry
• XDS Repository

Data Standards

• SAML V2.0 Standards http://www.oasis-open.org/committees/security/.
  • SAMLTechOvw SAML V2.0 Technical Overview (a work in progress currently at revision 10)
  • SAML Tutorial presentation by Eve Maler of Sun Microsystems
  • SAMLCore SAML V2.0 Core standard
  • WSS Web Services Security V1.1 including errata
  • WSS SAML Web Services Security SAML Token Profile V1.1 including errata
  • SAML Metadata Version 2.0
• WS-I
  • WS-I Conformance Claim
  • WS-I Basic Security Profile Version 1.1 (Doesn't use SAML 2.0)
  • WS-I Basic Profile Version 1.2 (Doesn't use SOAP 1.2)
• W3C
  • WS-Policy Version 1.2
  • SOAP Version 1.2
• ISO
  • ISO/TS 21091 Health informatics — Directory services for security, communications and identification of professionals and patients
  • ISO 17090 Health informatics - Digital Certificates in Healthcare

Volume 1

Add the following bullet to the list of profiles

Dependencies

Add the following row(s) to the list of dependencies

Profile Name

Use Case

This profile will likely take two years to fully fill out. In the first year we will be focusing only on the consumption side of XDS, specifically the Registry Stored Query and Retrieve Document transactions. The motivator for this is that these are the most exposed transactions that IHE has defined; their use is expected to be from a wide variety of consuming applications and enterprises.

1. General practice doctor retrieving results of a test performed by an outpatient clinic.
2. Outpatient clinic retrieving request to perform a test and background information necessary.
3. Doctor in an emergency situation request to retrieve documents (that would under normal conditions would not be accessible)
   1. Where the privacy consent (BPPC) has restricted access
4. System, based on a scheduled procedure, pre-fetches the available documents so that it can determine a relevant few documents to offer to the doctor when the patient arrives.
5. Patient, using a PHR like application, accesses their own information in XDS.
6. Access of a document by an individual that can’t be identified because the SAML-IDP (X-Assertion Provider) is not accessible

Actors

• X-Assertion Provider – This is a SAML Identity Provider (IDP), and is not further specified by IHE.
• X-Service User – This is the system making a web-services request. In the first year this is the XDS-Document Consumer Actor.
• X-Service Provider – This is the system providing the web-service. In the first year this is the XDS-Document Registry and XDS-Document Repository Actors.