Unclear PULL requirements - HRex #13

XMLWordPrintableJSON

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

      We will pull all documentation out of diagrams and represent it using the standard template (with standard fonts).  We'll be refactoring all of these pages to fit into an overall decision tree that provides guidance on when each type of communication mechanism should be used.  We will provide at least one real-world example for each showing where and why it would be appropriate.  We expect this guidance to eventually migrate into the FHIR core specification.

      Show
      We will pull all documentation out of diagrams and represent it using the standard template (with standard fonts).  We'll be refactoring all of these pages to fit into an overall decision tree that provides guidance on when each type of communication mechanism should be used.  We will provide at least one real-world example for each showing where and why it would be appropriate.  We expect this guidance to eventually migrate into the FHIR core specification.
    • Richard Esmond / Marti Velezis : 9-0-0
    • Clarification
    • Non-substantive

      Existing Wording: n/a

      Proposed Wording: n/a

      Comment:

      PULL 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 PULL requirements

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

              Created:
              Updated:
              Resolved: