Search results

Jump to navigation Jump to search
  • ...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 ...nect. We opted to take care of the 80% of use case that way. There are use cases that are not fulfilled by this approach, namely when A and B can become off
    31 KB (5,332 words) - 04:35, 27 November 2023
  • 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
  • ==Full Title of Use Case== * The test use case will be a patient that desires to transfer personal healthcare informa
    13 KB (2,156 words) - 18:55, 7 December 2020
  • ==Full Title of Use Case== * The test use case will be a patient that desires to download or upload medical records,
    14 KB (2,290 words) - 21:36, 30 March 2020
  • ...imary use case is smart phones running iOS or Android operating systems in use by the patient or their guardian. *Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentica
    19 KB (3,008 words) - 20:23, 20 March 2021
  • ...Blue"|'''Working Draft'''|| Committee Review || Compilation || Approval || Publication ==When to use this Pattern (Context)==
    11 KB (1,838 words) - 16:48, 19 January 2016
  • In some ways this is similar to existing use case that discuss privacy enhancing technology, but the purpose is quite di ...Blue"|'''Working Draft'''|| Committee Review || Compilation || Approval || Publication
    9 KB (1,467 words) - 20:46, 9 September 2018
  • In some ways this is similar to the existing use case that discusses privacy enhancing technology, but the purpose of the pa ...Blue"|'''Working Draft'''|| Committee Review || Compilation || Approval || Publication
    17 KB (2,712 words) - 19:20, 28 November 2021
  • == Use Case Metadata == ...such as liability, regulatory concerns, privacy, and business value. This use case is being posted to the wiki to obtain greater exposure within the IDES
    13 KB (1,990 words) - 21:48, 5 December 2020
  • == Use Case Metadata == ====Use Case Lifecycle Status====
    12 KB (1,835 words) - 20:44, 5 November 2020
  • ...| bgcolor="SteelBlue"|'''Committee Review''' || Compilation || Approval || Publication # The terms of use of each Trustmark will evolve as user and regulatory understanding grows.
    24 KB (3,856 words) - 16:05, 16 December 2021
  • == Use Case Metadata == Privacy enhancing technology generic use case. In some ways this is similar to the functional models produced in oth
    14 KB (2,167 words) - 01:45, 15 May 2021
  • == Use Case Metadata == ====Use Case Lifecycle Status====
    12 KB (2,056 words) - 20:35, 27 November 2019
  • == Use Case Metadata == ====Use Case Lifecycle Status====
    3 KB (328 words) - 21:41, 10 January 2020
  • ...ed at an Identity Provider (IdP). This has lead to a back-lash against the use of the term identity in the technical community. This model uses the term Identifier in places where other models use the term Identity for reasons that should be clear towards the end of the
    56 KB (9,154 words) - 00:16, 30 October 2020
  • ...Blue"|'''Working Draft'''|| Committee Review || Compilation || Approval || Publication ==When to use this Pattern (Context)==
    10 KB (1,596 words) - 20:11, 15 October 2019
  • == Use Case Metadata == A general use case which all other use cases can depend (unless they chose not to.)
    5 KB (810 words) - 04:00, 28 June 2018
  • <center>'''Federal Information Processing Standards Publication'''</center> Rules that have been established and implemented concerning use of, security in, and acceptable level of Risk for the System. Rules will cl
    135 KB (15,051 words) - 04:00, 28 June 2018

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