Unclear PUSH requirements - HRex #9

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • Financial Mgmt
    • Profile overview [deprecated]
    • Hide

      For all of the different workflow types, we will:

      • move text out of graphics and into HTML so that the appearance is consistent and so it's searchable
      • if possible, change diagrams to be SVGs so the text within them is also searchable
      • clearly differentiate requirements imposed by this IG from general expectations of the FHIR core spec
      • where we're reflecting requirements from the FHIR core spec, we'll include a hyperlink into that spec
      • we will provide example scenarios highlighting where each exchange scenario would be appropriate for use (and explain why)
      • for scenarios where we're doing more than just passing around a single resource, we'll include example instances showing what the exchange would look like (will evaluate whether ExampleScenario is ready to use for this purpose).
      Show
      For all of the different workflow types, we will: move text out of graphics and into HTML so that the appearance is consistent and so it's searchable if possible, change diagrams to be SVGs so the text within them is also searchable clearly differentiate requirements imposed by this IG from general expectations of the FHIR core spec where we're reflecting requirements from the FHIR core spec, we'll include a hyperlink into that spec we will provide example scenarios highlighting where each exchange scenario would be appropriate for use (and explain why) for scenarios where we're doing more than just passing around a single resource, we'll include example instances showing what the exchange would look like (will evaluate whether ExampleScenario is ready to use for this purpose).
    • Richard Esmond / Marti Velezis : 10-0-0
    • Correction
    • Non-substantive

      Existing Wording: n/a

      Proposed Wording: n/a

      Comment:

      PUSH page includes at least 5 different fonts, some unreadable, with no clear differentiation on requirements here vs base FHIR.

      Emphasize the requirements of this guide, don't restate FHIR requirements, or at minimum reference into FHIR specification.

      Consider proving real-world example scenarios and example instances

      Summary:

      Unclear PUSH requirements

            Assignee:
            Unassigned
            Reporter:
            Brett Marquard
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: