Search results

• Distributed Attributes for a Resilient Identity Ecosystem
  # Relying Parties can get the level of assurance that they need for authentication the user's identifiers. ...be able to provision one. See his evolving work with the emergency contact use case at http://controls.azurewebsites.net
  3 KB (507 words) - 00:20, 26 May 2019
• Patient uses Trusted Third Party to authenticate and move EHR
  ==Full Title of Use Case== # Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient alwa
  5 KB (842 words) - 03:00, 21 May 2019
• Patient Registration with Distributed Attributes
  ==Full Title of Use Case== ...ately address patient data or other providers, like lab services, that may use the same or different EHRs.
  10 KB (1,662 words) - 19:21, 27 April 2020
• Emergency Contact Information Use Case
  ==Full Title of Use Case== * This use can can easily be extended to other sources of user-provided information, b
  8 KB (1,248 words) - 20:08, 4 December 2019
• Patient with Lab and Referral Use Case
  ==Full Title of Use Case== # Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient alwa
  5 KB (825 words) - 17:21, 3 May 2019
• Health Care Profile
  # Creation of a profile for the use of the [[UXC NSTIC Principles]] in the US Healthcare community. ...it has been tried. (It has only worked where some enterprise required its use.)
  18 KB (2,580 words) - 18:52, 7 December 2020
• Financial Profile
  ...rity assurance as well as a paradigm of federated frameworks that we could use in our framework design. *In all cases that are known in 2018, a natural person is required to take responsibility
  5 KB (813 words) - 15:47, 26 November 2018
• Trustworthy Healthcare Ecosystem
  ...online and be able to download it and and share it with others. In those cases trust must be established and shared within the ecosystem by digital means. ...ment and software may need to be checked for compliance and trust prior to use by the patient. For the purposes of this document, all hardware and softwar
  28 KB (4,415 words) - 17:28, 21 March 2021
• User recovery and redress
  ...and correction procedures based on user's providing more than one means of authentication to their account. There are a variety of use cases that most of us experience on a steady basis that need to establish as user
  12 KB (2,064 words) - 19:21, 28 May 2020
• User Intent Pattern
  In some ways this is similar to existing use case that discuss privacy enhancing technology, but the purpose is quite di ==When to use this Pattern (Context)==
  9 KB (1,467 words) - 20:46, 9 September 2018
• User Consent
  # The user gets to select which of their identifiers they wish to use with the web site. ...tions at that point in time. The current state of the web is recognized as use case 6, Contract of Adhesion.
  13 KB (2,151 words) - 00:14, 30 October 2020
• User Choice Pattern
  In some ways this is similar to the existing use case that discusses privacy enhancing technology, but the purpose of the pa ===When to use this Pattern (Context)===
  17 KB (2,712 words) - 19:20, 28 November 2021
• Patient Consent
  ...{ This just provides access to ALL DATA, which should not be needed in all cases. Note that patient's do not actually have access to ALL DATA. Expemptions ...f research might be considered. (In any case we should avoid any alternate use of the term "scope".)
  10 KB (1,599 words) - 22:38, 20 March 2021
• Being Digital
  ...fact that many people do. We have seen many cases, and one of the symbolic cases is the death of a 23-year-old reality TV actress who was stormed by a mob o ...emble them with the claims that it is authoritative, for example, the user authentication result, and signs them and provides it to D. To make this possible, the use
  31 KB (5,332 words) - 04:35, 27 November 2023
• Mobile Driver's License Criteria
  ...[Mobile Driver's License Criteria]] for a high level of [[Identity]] and [[Authentication]] [[Level of Assurance|Assurance]]. ...uding the purpose and scope of data requested, to the mDL holder and never use blanket terms and conditions in lieu of informed consent.</blockquote>
  30 KB (4,866 words) - 16:56, 9 June 2021
• Patient Journey as seen by the Browser
  # User selects to use a federated sign in process. (Note that this process may be a related hospi # The user continues onto the authentication steps.
  4 KB (726 words) - 15:03, 7 April 2021
• Trustworthy Healthcare Application
  ...usted Identifiers in Cyberspace) for healthcare industry makes application authentication assurance statements available at all times for [[Trustworthy Healthcare Pr ...iving care and the one that "owns" the rights to the information. (In some cases the patient allows other users access to their PHI.)
  20 KB (3,074 words) - 22:40, 21 March 2021
• Patient Web Experience
  ...view of this Identity Wiki extends to the use cases across a range of use cases. This wiki page focuses on the interactions of the patient and their guardi * The majority of the focus will be on the use of a smart phone by the patent to provide a high assurance identifier from
  7 KB (1,136 words) - 20:39, 8 September 2020
• Delegation
  ===Use Cases=== * [[Delegate Credentials Use Case]]
  7 KB (1,127 words) - 21:03, 15 April 2021
• Self-issued Identifier
  This Wiki Page was created to track the use of [https://tcwiki.azurewebsites.net/index.php?title=Self-issued_Identifier .... It is recognized that other use cases also exist, but it seems that this use case covers all the issues.
  6 KB (856 words) - 23:37, 25 July 2020

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)