Search results
Jump to navigation
Jump to search
Page title matches
Page text matches
- The [[Identity Ecosystem]] Framework (IDEF) will need fine-grained specifications for appl *As a part of the creation of a set of [[Identity Ecosystem]]s this plan lays out how to address specific community needs for7 KB (988 words) - 21:22, 15 December 2018
- The commercial context includes a number of large Identity Providers like Microsoft, Google, Yahoo and Facebook each of which maintain #Customer Relationship Management (CRM) systems have been deployed in enterprises for decades, most have not12 KB (2,064 words) - 19:21, 28 May 2020
- 1) When choosing an identity provider at an RP site, the available options are clearly presented so that - needs to work well for both cases. What this means is that whatever is displayed by the RP26 KB (4,220 words) - 19:40, 19 December 2014
- # 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
- ...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. ...igital world by virtue of trust certificates. Some of these will perform [[Identity Proofing]]. The digital services that they provide are listed below.28 KB (4,415 words) - 17:28, 21 March 2021
- * For healthcare the intended purpose is to bind the subject to the identity proofing document (IAL2) and validate the user agent as being in compliance ...action to create user context within the larger user experience of consent management of the user with some digital entity.14 KB (2,250 words) - 01:29, 23 December 2020
- ...users) with their PHI and their [[UXC Dictionary|Consent]] as to permitted use. ...iving care and the one that "owns" the rights to the information. (In some cases the patient allows other users access to their PHI.)19 KB (2,997 words) - 01:34, 18 February 2021
- Privacy and terms of use policy infrastructures on the Receipts; Open Notice; Usable Consent; Terms of Use;17 KB (2,526 words) - 01:18, 21 February 2020
- ...]] that for [[IDEF Glossary DIGITAL IDENTITY MANAGEMENT FUNCTIONS|Identity Management]] applies to release of health care information and notifications of change *Consent management - particularly privacy consent - is complicated by the fact that consent to10 KB (1,599 words) - 22:38, 20 March 2021
- The [[Mobile Driver's License]] is being developed to expand the [[Identity]] functions of the driver's license to the online space. ...aKOtoxOLKkg9g9yTI9nM/edit#heading=h.tm3ctucmk6y1 Report from the Privacy & Identity Protection in mobile Driving License ecosystems Discussion Group] working d8 KB (1,167 words) - 20:52, 2 July 2021
- ...iving care and the one that "owns" the rights to the information. (In some cases the patient allows other users access to their PHI.) ...igital world by virtue of trust certificates. Many of these will perform [[Identity Proofing]]. All will provide evidence that a user is accepted as a patient20 KB (3,074 words) - 22:40, 21 March 2021
- The [[Mobile Driver's License Criteria]] for a high level of [[Identity]] and [[Authentication]] [[Level of Assurance|Assurance]]. ...aKOtoxOLKkg9g9yTI9nM/edit#heading=h.tm3ctucmk6y1 Report from the Privacy & Identity Protection in mobile Driving License ecosystems Discussion Group] working d30 KB (4,866 words) - 16:56, 9 June 2021
- '''Use Case Description''': ...to system with trusted identity, authenticate to system with pseudonymous identity, match names between systems, verify attributes with privacy protection]881 bytes (102 words) - 04:02, 28 June 2018
- #**Without another plan, could present the state of work related to use case analysis relative to draft functional elements. ...ions and elements. Agreed not for the functional elements of the identity management workflow5 KB (753 words) - 03:58, 28 June 2018