2015May core #561 - Narrative only shouldn't be a List

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • List
    • 6.1.5
    • Hide

      Add documentation to the wiki about list vs Basic in the light of SD decision about Composition

      Show
      Add documentation to the wiki about list vs Basic in the light of SD decision about Composition
    • James Agnew / Grahame Grieve: 4-0-0
    • Correction
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: human written narrative may be the only content if the list has no entries (which would equate to a narrative only section in a document).

      Proposed Wording: human written narrative may be the only content if the list has no entries (which would equate to a narrative only section in a document). However, the content should still be regarded by humans as a list, e.g., a manually entered list of past procedures without structured entries. But narrative that is not a "list" at all, such as a Chief Complaint, should not use the List resource.

      Comment:

      It is legitimate to have narrative-only section, but it does not make sense to call it a "List." A list should be a set of things of the same or similar character, e.g., a med list, a problem list, a result list that might in narrative be represented as bullets, enumerated, or a table. Narrative that is "paragraphs" or not a set of entries – e.g., Hospital Course, Chief Complaint – does not fit the definition of a list. The suggested wording tries to clarify.

            Assignee:
            Unassigned
            Reporter:
            david_tao
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: