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

Why can't a consumer app query the directory - seems like it should be able to

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • Human Services Directory (FHIR)
    • current
    • Human and Social Services
    • Home
    • 1.1
    • Hide

      This IG is intended to provide FHIR-based APIs used by FHIR-enabled applications to query human services directories that have been "standardized" to conform to  HSDS version 2.0-format, or whose local directory data has been mapped to corresponding HSDS fields). 

      Consuming applications may include EHR-systems, payer systems, CBO-vendor platforms, and any consumer (e.g., mobile) application that seeks to retrieve a set of services from a human services directory using the search capabilities provided in the FHIR IG.

      The scope/approach and use case section will be revised per reconciliation of use case related issues, in particular the in scope use cases FHIR-40060 Revisions to use case section: clarification on primary use case(s)

      to read:

      This STU1 release of the Implementation Guide focuses on read-only queries of a single directory of human services. Such queries might support a range of use cases:
      • Service discovery in which a care provider queries a service directory to find services that may help address clients’ social needs in accordance with their relevant criteria (geography, goals, relevant personal attributes).

       

      This IG is intended to support all FHIR-enabled applications/systems, including consumer apps that want to provide results of a human services directory query to its users.

       

       

      Show
      This IG is intended to provide FHIR-based APIs used by FHIR-enabled applications to query human services directories that have been "standardized" to conform to  HSDS version 2.0-format, or whose local directory data has been mapped to corresponding HSDS fields).  Consuming applications may include EHR-systems, payer systems, CBO-vendor platforms, and any consumer (e.g., mobile) application that seeks to retrieve a set of services from a human services directory using the search capabilities provided in the FHIR IG. The scope/approach and use case section will be revised per reconciliation of use case related issues, in particular the in scope use cases FHIR-40060 Revisions to use case section: clarification on primary use case(s) to read: This STU1 release of the Implementation Guide focuses on read-only queries of a single directory of human services. Such queries might support a range of use cases: • Service discovery in which a care provider queries a service directory to find services that may help address clients’ social needs in accordance with their relevant criteria (geography, goals, relevant personal attributes).   This IG is intended to support all FHIR-enabled applications/systems, including consumer apps that want to provide results of a human services directory query to its users.    

    Description

      In the diagram, it appears the scope for consumer apps is limited to interacting with on human service.  It seems that this limits the benefit for consumer apps which might want to provide the results of a query of the directory to its users.  Can the scope be changed to include that?  Why is the limitation needed?

      Attachments

        Activity

          People

            Unassigned Unassigned
            vlorenzi Virginia Lorenzi
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: