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

Concerns about use of NPI.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • HRex Practitioner Profile
    • Resource Profile: Practioner
    • Hide

      The use of NPI is inherited from US Core and is not HRex specific - and the concern raised is more about "private" information of practitioners being used inappropriately.  Suggest that the respondent submit a change request against US Core and/or the base FHIR specification highlighting the fact that Practitioner (and PractitionerRole) information may include private individual information and therefore needs to be treated with appropriate security and disclosure considerations.

      Show
      The use of NPI is inherited from US Core and is not HRex specific - and the concern raised is more about "private" information of practitioners being used inappropriately.  Suggest that the respondent submit a change request against US Core and/or the base FHIR specification highlighting the fact that Practitioner (and PractitionerRole) information may include private individual information and therefore needs to be treated with appropriate security and disclosure considerations.
    • Marti Velezis / James Tcheng : 6-0-1

    Description

      Some of our members have concern with the use of their NPI. For instance, a client app gaining access to an NPI and using it for marketing. Is there a process in place to restrict NPI access to those with a legitimate need for these numbers? Further, how can a physician minimize the amount of information released in association with each NPI number?

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: