Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-39902

Care Plan Note to Balloters feedback

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Core (FHIR)
    • 6.0.0-ballot [deprecated]
    • Cross-Group Projects
    • US Core CarePlan Profile
    • Profiles and Extensions
    • Hide

      Decision:

      Change CarePlan.text from Mandatory min = 1 to Must Support min = 0

      Add bullets to Careplan Profile Specific Implementation Guidance:

       

      • The original Assessment and Plan design in the CarePlan was to support the 'Assessment and Plan' from a narrative Progress Note. Systems have advanced significantly since the introduction of this requirement in 2015. Relaxing this to 0..1 allows more sophisticated systems to discretely encode a CarePlan while still allowing a narrative 'Assesment and Plan'

       


      • Alternatively, Assessment and Plan of Treatment may be included in various types of [Clinical Notes], such as Progress Notes, History & Physical (H&P), Discharge Summaries, etc.

      Background and Rationale

      From 2015 CCDS

      From USCDI:

      Assessment and Plan of Treatment

      Health professional’s conclusions and working assumptions that will guide treatment of the patient.

       

      • We believe that the USCDI class of 'Assessment and Plan' may be too broad and generic.
      • Our selection of CarePlan in DAF/Argonaut/US Core preceded  US Core Clinical Notes design
      • The Assessment and Plan design in the CarePlan is confusing and, in hindsight, may not have been the best choice.
      • Nevertheless, it is worth noting that it has been a part of the US Core since Argonaut DSTU in 2017 and has thus been widely adopted. The suggested modifications provide a roadmap for future developments and allow systems flexibility in representing care plans.
      Show
      Decision: Change CarePlan.text from M andatory min = 1 to Must Suppor t min = 0 Add bullets to Careplan Profile Specific Implementation Guidance:   The original Assessment and Plan design in the CarePlan was to support the 'Assessment and Plan' from a narrative Progress Note. Systems have advanced significantly since the introduction of this requirement in 2015. Relaxing this to 0..1 allows more sophisticated systems to discretely encode a CarePlan while still allowing a narrative 'Assesment and Plan'   Alternatively, Assessment and Plan of Treatment may be included in various types of [Clinical Notes] , such as Progress Notes, History & Physical (H&P), Discharge Summaries, etc. Background and Rationale From 2015 CCDS From USCDI: Assessment and Plan of Treatment Health professional’s conclusions and working assumptions that will guide treatment of the patient.   We believe that the USCDI class of 'Assessment and Plan' may be too broad and generic. Our selection of CarePlan in DAF/Argonaut/US Core preceded  US Core Clinical Notes design The Assessment and Plan design in the CarePlan is confusing and, in hindsight, may not have been the best choice. Nevertheless, it is worth noting that it has been a part of the US Core since Argonaut DSTU in 2017 and has thus been widely adopted. The suggested modifications provide a roadmap for future developments and allow systems flexibility in representing care plans.
    • Eric Haas/Jason Vogt: 12-0-0
    • Clarification
    • Compatible, substantive

    Description

      Option #4 except:

      • Retain CarePlan Text - at least must support and should be derived from structured element if possible
      • CarePlan.description could contain a narrative only assessment and plan  "A description of the scope and nature of the plan" https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-careplan-definitions.html#CarePlan.description
      • CarePlan.supportingInfo could hold any resource, so could point to any relevant resource (for example a shift assessment (whatever resource that would) be or a Questionnaire Assessment, or a risk assessment)
      • CarePlan.activity.reference is intended to be a PLANNED ACTIVITY and will be renamed as such in R5 - and should hold plans (which should just be pulled into or referenced to the relevant orders, etc
      • DO NOT use CarePlan.activity.detail.reasonReference  as CarePlan.activity.detail may be removed (see https://jira.hl7.org/browse/FHIR-39101)
      • Activity.outcomeReference could be used instead for a performed assessment, as that is intended to be a performed activity and was renamed as such in R5

      Attachments

        Activity

          People

            Unassigned Unassigned
            GDolin Gay Dolin
            Emma Jones
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: