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

Please incorporate IHE Topologies profiling for discovering federated (i.e. indirect) electronic routes

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • National Directory of Healthcare Providers and Services (NDH) (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • Exchange Use Cases
    • 3.6
    • Hide

      Include values of DocShare-federate-in and DocShare-federate-ext in the OrganizationAffiliation.code value set  Include diagram based on the diagram in the IHE whitepaper

      Show
      Include values of DocShare-federate-in and DocShare-federate-ext in the OrganizationAffiliation.code value set  Include diagram based on the diagram in the IHE whitepaper
    • Bob Dieterle / Ming Dunajick: 10-0-0
    • Enhancement
    • Compatible, substantive

    Description

      Broken out from FHIR-42644:

      We appreciate NDH's inclusion of IHE profiling and work in the mCSD profile and Topologies whitepaper in the section on discovery of endpoints: 3.6 Discovery a HIE Endpoint via the NDH.

      The use case in NDH 3.6 currently shows how to use the IHE code HIEResponder in OrganizationAffiliation.code to reflect that an Organization is reachable through a given HIE, and OrganizationAffiliation.endpoint reflects dedicated endpoints to this Organization other members of the HIE can use if appropriate.

      This ticket is to request the IHE codes DocShare-federate-in and DocShare-federate-ext as well, on OrganizationAffiliation.code. This supports discovering when an Organization is reachable electronically, but only indirectly, through the Endpoint of a related Organization. This is the case with numerous IHE profiles for federated SOAP APIs like XCPD and XCA.

      The IHE profiling is available in full at https://profiles.ihe.net/ITI/papers/Topologies/index.html and this capability is walked with an example in section 5.1.8 Document Access: Putting it all together.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jlamy Joseph M. Lamy
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: