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

Need more clarification on local practioner registry.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • Approaches to Exchanging FHIR Data
    • 3.0.2 Overview of Approaches
    • Hide

      This question isn't really suitable for the scope of the section which isn't intended to address privacy/security appropriateness of the exchange, merely why the exchange mechanism might be used.

      Based on agreed clarifications on the scope of this section already agreed to elsewhere, balloter agrees to this disposition

      Show
      This question isn't really suitable for the scope of the section which isn't intended to address privacy/security appropriateness of the exchange, merely why the exchange mechanism might be used. Based on agreed clarifications on the scope of this section already agreed to elsewhere, balloter agrees to this disposition
    • Marti Velezis / James Tcheng : 6-0-1

    Description

      Perhaps we are misunderstanding what “their local practitioner registry” refers to, but if it is taking information housed by a practitioner and syncing it to a different registry, doesn’t the payer need to seek appropriate permissions to do so from the local practitioner registry? Will likely depend (from a HIPAA perspective) on the purpose of the synchronization. Also would require a way to deal with PHI requiring additional consents from the patient prior to redisclosure (e.g., Part 2 data).

      Existing Wording:

      A payer is synchronizing their local practitioner registry with a centralized registry

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: