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

How should payer organization be identified? - PCDE #74

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci PCDE (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Hide

      We will add a pre-condition indicating that the two payers must be able to recognize the each other based on an agreed set of payer identifier scheme. 

      Will add an open issue noting that work is in progress on standardizing how payer identification will be managed, as well as how the FHIR endpoint for a given payer will be found - i.e. through the use of a registry.  For now, this is left to site-to-site negotiation.

      Show
      We will add a pre-condition indicating that the two payers must be able to recognize the each other based on an agreed set of payer identifier scheme.  Will add an open issue noting that work is in progress on standardizing how payer identification will be managed, as well as how the FHIR endpoint for a given payer will be found - i.e. through the use of a registry.  For now, this is left to site-to-site negotiation.
    • Bob Dieterle / Kathleen Conner: 24-0-3
    • Clarification
    • Non-substantive

    Description

      Comment:

      How should payer organization be identified? TIN, plan info, etc. Should the FHIR endpoint be an ideentifier? Is this specific enough?

      Summary:

      How should payer organization be identified?

      Attachments

        Activity

          People

            Unassigned Unassigned
            jskapik Julia Skapik
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: