ITI XUA Extension: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
JohnMoehrke (talk | contribs)
JohnMoehrke (talk | contribs)
Line 4: Line 4:
==Detailed proposal==
==Detailed proposal==
[ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr8-2010-2011/Technical_Cmte/Detailed-Profile-Proposals/IHE_ITI_XUA_Option_Proposal_Detailed_FINAL_2009-2010_hornr.doc XUA Extension detailed proposal]
[ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr8-2010-2011/Technical_Cmte/Detailed-Profile-Proposals/IHE_ITI_XUA_Option_Proposal_Detailed_FINAL_2009-2010_hornr.doc XUA Extension detailed proposal]
==Use Cases==
# Role-Based-Access Control: Need to specify a fuller vocabulary of attributes needed for access control decisions. 
# Consent/Authorization: Need to carry an indicator of BPPC document that is relevant to the transaction
# Level Of Assurance for (a) the authentication event, and/or (b) the provisioning of the account
# Extended Audit Logging: Support descriptive identifiers to support environments where post-processing doesn’t have access to directory for id translation into description.
# Purpose-of-Use: Carry in the assertion purpose-of-use, including support for Break-Glass / Emergency-Mode-Access
# Relationship-to-Patient: Carry the indicator of the patient, relationship to patient, location of patient


==Supplement for Public Comment==
==Supplement for Public Comment==

Revision as of 17:52, 3 February 2010

History

Detailed proposal

XUA Extension detailed proposal

Use Cases

  1. Role-Based-Access Control: Need to specify a fuller vocabulary of attributes needed for access control decisions.
  2. Consent/Authorization: Need to carry an indicator of BPPC document that is relevant to the transaction
  3. Level Of Assurance for (a) the authentication event, and/or (b) the provisioning of the account
  4. Extended Audit Logging: Support descriptive identifiers to support environments where post-processing doesn’t have access to directory for id translation into description.
  5. Purpose-of-Use: Carry in the assertion purpose-of-use, including support for Break-Glass / Emergency-Mode-Access
  6. Relationship-to-Patient: Carry the indicator of the patient, relationship to patient, location of patient

Supplement for Public Comment

Security Assessment

Notes

FTP site for this project Return to ITI Technical Committee