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

PDex and HRex identify different profiles for $member-match

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • HRex Parameters - Member Match Request Profile
    • 11.10.1.1
    • Hide

      Will change the HRex profile to refer to the HRex demographics profile rather than US Core

      Show
      Will change the HRex profile to refer to the HRex demographics profile rather than US Core
    • Lloyd McKenzie/Jimmy Tcheng: 9-0-0
    • Correction
    • Compatible, substantive
    • Yes

    Description

      Hi!

      In HRex, the Member Match Request Profile identifies the following profiles in the Text Summary of 11.12.1.1:

      • US Core Patient Profile
      • HRex Coverage Profile
      • HRex Consent Profile

      In PDex, it is stated in 5.2.1.2 that the profiles used in the Member Match operation are also defined in HRex but then identifies them as:

      • HRex Patient Demographics Profile
      • HRex Coverage Profile
      • HRex Consent Profile

      Which is correct when implementing $member-match to support payer-to-payer exchanges? Please fix this inconsistency.

      I'm inclined to go with the PDex-identified profiles because HRex Patient Demographics Profile makes date of birth a required element...but that doesn't amount to much if others are implementing differently.

      It's worth noting that HRex Patient Demographics Profile is not derived from US Core Patient Profile so there may be other issues I have yet to notice.

      Thanks!

      Attachments

        Activity

          People

            rosemaryh Rosemary Hofstede
            dmuylwyk Diederik Muylwyk
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: