Search results
Jump to navigation
Jump to search
- access profile An individual applying for a PIV Card/credential. The Applicant may be a current or prospective Federal hire, a Federal empl845 KB (86,833 words) - 04:00, 28 June 2018
- ...ered SAML protocol binding. This technique is used in the browser/artifact profile of SAML. An identity credential; previously stored personal questions and answers. Also known as Challenge/135 KB (15,051 words) - 04:00, 28 June 2018
- ...ublic Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile '''Category''': Credential Interoperability Profile481 bytes (49 words) - 04:00, 28 June 2018
- '''Interoperability''': ...nt Agreement]], [[Participant Operating Practices]], [[Privacy Policy]], [[Profile]], [[Public Key Cryptography]], [[Public Key Infrastructure]], [[Relying Pa2 KB (205 words) - 04:01, 28 June 2018
- ...tle''': X.509 Certificate and Certificate Revocation List (CRL) Extensions Profile for Personal Identity Verification '''Category''': Credential Interoperability Profile709 bytes (80 words) - 21:24, 25 March 2021
- ...es that: “users must have the opportunity to decline registration; decline credential provisioning; decline presentation of their credentials; and decline releas ==Interoperability Considerations==24 KB (3,856 words) - 16:05, 16 December 2021
- ...validated and attributes are captured as part of their community mobile ID credential. ...edentialing program that a Community can adapt to their culture, needs and profile to help vulnerable populations integrate into their community and to assist3 KB (399 words) - 18:50, 13 May 2020
- This [[Health Care Profile]] is one of the [[Framework Profiles]] that will allow developers of code a # Creation of a profile for the use of the [[UXC NSTIC Principles]] in the US Healthcare community.18 KB (2,580 words) - 18:52, 7 December 2020
- # Profile of IDEF (Trusted Identifiers in Cyberspace) for healthcare industry in US. ...t include all 4 IDEF components of: Security, Privacy, User Experience and Interoperability.28 KB (4,415 words) - 17:28, 21 March 2021
- Using a Patient's Cell Phone as the holder of their (1) Health Care Credential and (2) personal healthcare Information store. ...change of EHI. A QHIN shall not unfairly or unreasonably limit exchange or interoperability with any other QHIN, Participant, Participant Member, or Individual User su19 KB (3,008 words) - 20:23, 20 March 2021
- This is an extension of the [[Phone as Health Care Credential]] proposal to a broader audience of teams interested in high assurance [[Au * [https://ims.ul.com/interoperability-mobile-driver-license-mdl-application Interoperability with Mobile Driver's Licence]3 KB (420 words) - 17:40, 24 May 2020
- * The wiki page [[Health Care Profile]] establishes the context for this page. * The wiki page [[Health Care Profile]] establishes the context for this page.19 KB (2,997 words) - 01:34, 18 February 2021
- ...nity for identity proofing with dual factor authentication (IAL2) and user credential protection (AAL2). #A Remote Attestation Service (aka Credential Service Provider) that can handle the following functions:14 KB (2,290 words) - 21:36, 30 March 2020
- ## The interoperability of the APIs used by the app. This applies to the identification proofing an ## Credential Services Providers for both (1) Patient Identity Proofing and (2) patient a11 KB (1,637 words) - 23:44, 10 November 2020
- ...describes how the mobile driver's license can be used as identity proofing credential in healthcare service (aka Medicaid). ...ey solution to states that comes with a "wallet" that only handles the one credential.8 KB (1,360 words) - 01:30, 7 January 2021
- * The wiki page [[Health Care Profile]] establishes the context for this page. * The wiki page [[Health Care Profile]] establishes the context for this page.20 KB (3,074 words) - 22:40, 21 March 2021