Proposed changes to support non clinical use cases - List

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • List
    • Hide

      1. Will add Organization & Practitioner to subject
      2. Will update the description of List.date to indicate "Date list was last reviewed/revised and determined to be 'current'"
      3. There's nothing special about List.source for us to document this. PractitionerRole allows identifying the organization the Practitioner was acting on behalf of and what 'hat' they were wearing. So, for example, a Practitioner might have two different problem lists for the same patient - one for their clinic and one for their hospital practice. We don't think there's a reason to call this out in the spec.

      Show
      1. Will add Organization & Practitioner to subject 2. Will update the description of List.date to indicate "Date list was last reviewed/revised and determined to be 'current'" 3. There's nothing special about List.source for us to document this. PractitionerRole allows identifying the organization the Practitioner was acting on behalf of and what 'hat' they were wearing. So, for example, a Practitioner might have two different problem lists for the same patient - one for their clinic and one for their hospital practice. We don't think there's a reason to call this out in the spec.
    • Christiaan Knaap/Jeff Danford: 12-0-0
    • Enhancement
    • Compatible, substantive

       As part of the review of the List resource to ensure it addresses both the clinical and the nonclinical scope, some aspect have been identified as needing updates or clarifications. 

       

      1. Please extend the List.subject list with: Organization, Practitioner to support regulated authorizations.

       

      1. Please clarify the description of List.date so it is unambiguous if the intended use is date of initial creation or date of last modification.

       

      1. While the concept of PractitionerRole as the List.source makes logic in some ways it might be helpful to illustrate when this would be used rather than using the associated Practitioner directly.

            Assignee:
            Unassigned
            Reporter:
            Peter Bomberg
            Peter Bomberg, Rik Smithies, Smita Hastak
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: