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

Reflect the larger scope beyond consumer applications

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • Human Services Directory (FHIR)
    • 1.0.0-ballot
    • Human and Social Services
    • Home
    • Hide

      Figure 1 will be updated to clarify the scope for the implementation guide and the relationship between the HSDS specification (as a source for CBO directory requirements) and client and server roles and applications. We aren’t sure that we see a big difference between calling something a consuming application and consumer application, and this diagram is intended to specifically indicate that the source for the information exchange is in HSDS format, as the mapping between the HSDS implementation model and FHIR profiles in this IG is the primary focus for users, including EHR-systems, payer systems, CBO-vendor platforms, and consumer mobile apps (consuming application implementers).

      Show
      Figure 1 will be updated to clarify the scope for the implementation guide and the relationship between the HSDS specification (as a source for CBO directory requirements) and client and server roles and applications. We aren’t sure that we see a big difference between calling something a consuming application and consumer application, and this diagram is intended to specifically indicate that the source for the information exchange is in HSDS format, as the mapping between the HSDS implementation model and FHIR profiles in this IG is the primary focus for users, including EHR-systems, payer systems, CBO-vendor platforms, and consumer mobile apps (consuming application implementers).
    • Serafina Versaggi / Chirag Bhatt : 18 - 0 - 1
    • Clarification
    • Non-substantive

      The diagram indicates "consumer applications". That is too limiting considering the inclusion of the list above that inlcude EHRs, CBO-HIT, LTSS-CMS, etc. Perhaps "consuming applications" would be more descriptive, or "client application" (the latter works even better if "HSDS Source" is changes to "HSDS Server". Note that "HSD" for Health or Human Services Directory would be enough. "data specification" is only adding ambiguity, not clarity as the directory is not a specfication in this diagram, rather the actual directory.

      (Comment 4 - imported by: Hans Buitendijk)

        1. HSD FHIR Implementation Scope.png
          HSD FHIR Implementation Scope.png
          86 kB

            Unassigned Unassigned
            hbuitendijk Hans Buitendijk
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: