2015May core #560 - How is list narrative made non-redundant if generated?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Structured Documents
    • Narrative
    • 1.15.0
    • Hide

      Add a note that systems can be as intelligent as tehy want when generating narrative, but SHALL NOT assume that the resource is rendered in any particular context when generating narrative

      Show
      Add a note that systems can be as intelligent as tehy want when generating narrative, but SHALL NOT assume that the resource is rendered in any particular context when generating narrative
    • James Agnew / Grahame Grieve: 4-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: Narrative for a resource should include summary information about referenced resources as necessary for a consumer of the resource to be able to understand the key essential information about a resource without retrieving additional resources. For example, the narrative for a MedicationPrescription might include brief summary information about the referenced patient, prescriber and medication.

      Comment:

      I understand why this is stated, so that when a single resource (e.g., MedicationPrescription) is accessed, a human can understand that Dr. Smith wrote this Rx for John Doe. However, if there is a request for multiple resources, or a list of resources, or a FHIR document, then how is this "summary information about referenced resources" to be rendered without being verbose and redundant? For instance, a medication list for John Doe shouldn't have to list John Doe with each item in the list. A document composition would typically have the patient displayed at the top, but not shown again for every section or (worse) for every resource. Is there a way for the system to "suppress" unnecessary reference narrative for lists, documents, and multiple resource retrievals?

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

              Created:
              Updated:
              Resolved: