Provide guidance to application that use FHIR to interrogate EHRs for resources conformant with US-Core. The current guidance focuses on the 'responder', primarily. - USCore #65

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered - No action required
    • Priority: Medium
    • US Core (FHIR)
    • STU3
    • Structured Documents
    • (many)
    • Hide

      We believe additional elements may need to be displayed beyond those mandated in this specficiation. Defining display requirements is difficult and not something considered fully in this current tproject.

      This is a great question and believe is appropriate for a future project.

      Show
      We believe additional elements may need to be displayed beyond those mandated in this specficiation. Defining display requirements is difficult and not something considered fully in this current tproject. This is a great question and believe is appropriate for a future project.
    • Eric Haas/Calvin Beebe: 23-0-6
    • Enhancement

      Comment:

      Implementers need guidance on how to use profile identifier to search for resources compatible with the display characteristics of their client application. There are many data elements that could be included in a resource in the response bundle. However, the client applications are only mandated to display the must-support data elements. Are we expecting application to display other data elements? What should be the expectation of users/clinicians who use client applications that conform to this spec (i.e. the "requestor" actor0?

      Summary:

      Provide guidance to application that use FHIR to interrogate EHRs for resources conformant with US-Core. The current guidance focuses on the 'responder', primarily.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Ioana Singureanu
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: