Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-40354

Inconsistent workflows, Proper use of IAL levels (8 of 9)

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Interoperable Digital Identity and Patient Matching (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • Digital Identity
    • Hide

      Full proposed disposition for review on 3/2

      • Move the text of the NOTE in 5.1 to become the second sentence in the first paragraph of 5.1 (changing "may" to "can") and with the word NOTE: removed
      • Add the text in the disposition to 3.2 above the NOTE except insert final sentence right after NOTE text in first paragraph of section 5 Overview; amend text as below
      • Re-title 5.2 to include "...for Individuals" for clarity
      • Insert “human” before “subject”

      Put this text in the Guidance tab instead (incorporates the tie-in to credential that Joe requested in ticket comments last week, as well as another question yesterday re: when this is relevant):

      Organizational identity, when relevant, is verified through an attestation by an individual, whose identity is also verified at a level of assurance commensurate with that of the credential desired, that they are an authorized representative of that unique legal organizational entity. The legal existence of the organization {}SHALL{} also be verified, along with a street address asserted by the individual, through government records or equivalent, as well as the control of any host name or other electronic endpoint presence that will be asserted in a credential or otherwise bound to the organizational identity. 

      Keep this sentence in first paragraph of Overview as per resolution description:

      The combination of a legally verified organization name and the state in which it is verified uniquely identifies an organization.

      Remove footnote; does not add information and may create confusion

      Show
      Full proposed disposition for review on 3/2 Move the text of the NOTE in 5.1 to become the second sentence in the first paragraph of 5.1 (changing "may" to "can") and with the word NOTE: removed Add the text in the disposition to 3.2 above the NOTE except insert final sentence right after NOTE text in first paragraph of section 5 Overview; amend text as below Re-title 5.2 to include "...for Individuals" for clarity Insert “human” before “subject” Put this text in the Guidance tab instead (incorporates the tie-in to credential that Joe requested in ticket comments last week, as well as another question yesterday re: when this is relevant): Organizational identity, when relevant, is verified through an attestation by an individual, whose identity is also verified at a level of assurance commensurate with that of the credential desired, that they are an authorized representative of that unique legal organizational entity. The legal existence of the organization { }SHALL{ } also be verified, along with a street address asserted by the individual, through government records or equivalent, as well as the control of any host name or other electronic endpoint presence that will be asserted in a credential or otherwise bound to the organizational identity.  Keep this sentence in first paragraph of Overview as per resolution description: The combination of a legally verified organization name and the state in which it is verified uniquely identifies an organization. Remove footnote; does not add information and may create confusion
    • Jeff Brown / Rick Lisseveld : 8-0-0
    • Clarification
    • Non-substantive

    Description

      Section 5.1
      The following text: "Note: digital identities involved in healthcare transactions may correspond to Patients, Providers, Payers, and other healthcare actors."

      Note that NIST Special Publication 800-63 is only targeting people, not entities.
      Could we further elaborate if NIST is being applied to Payer entities? How would assurance/digital work for each of these?

      • add clarifying language re: how organizational credentials at a level of assurance are established in networks more generally

      Attachments

        Activity

          People

            Unassigned Unassigned
            nussteja Aaron Nusstein
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: