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

Define how an aggregated care plan in its entirety can be sent to another information system

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Multiple Chronic Condition Care Plan (FHIR)
    • 1.0.0-ballot [deprecated]
    • Patient Care
    • Multiple Chronic Care Condition Care Plan
    • Hide

      Define how  an aggregated care plan in its entirety can be sent to another information system. 

      The intent of this FHIR Care plan is to retrieve info for a single EHR or across many systems and aggregate it into an independent app (patient or provider facing) or perhaps a Care Plan Module in an EHR.

      It would be valuable to also describe and define how such an aggregated CarePlan would/could be send leveraging, for example FHIR Bundle.

      Please add the technical information (diagrams, a Profile on FHIR Bundle, Capability statement requirements etc.. to inform and provide guidance to developers/implementers prior to the STU ballot in September 2023

      -------

      Consider adding a new Jira that requests descriptions of 

      Reading and writing Care Plan information (Create and Updates) see http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/CapabilityStatement-SDOHCC-PatientApp.html#rest-client-behavior

      Show
      Define how  an aggregated care plan in its entirety can be sent to another information system.  The intent of this FHIR Care plan is to retrieve info for a single EHR or across many systems and aggregate it into an independent app (patient or provider facing) or perhaps a Care Plan Module in an EHR. It would be valuable to also describe and define how such an aggregated CarePlan would/could be send leveraging, for example FHIR Bundle. Please add the technical information (diagrams, a Profile on FHIR Bundle, Capability statement requirements etc.. to inform and provide guidance to developers/implementers prior to the STU ballot in September 2023 ------- Consider adding a new Jira that requests descriptions of  Reading and writing Care Plan information (Create and Updates) see http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/CapabilityStatement-SDOHCC-PatientApp.html#rest-client-behavior
    • Gay Dolin / Emma Jones: 9-0-0
    • Enhancement
    • Compatible, substantive

    Description

      Define how  an aggregated care plan in its entirety can be sent to another information system. 

      The intent of this FHIR Care plan is to retrieve info for a single EHR or across many systems and aggregate it into an independent app (patient or provider facing) or perhaps a Care Plan Module in an EHR.

      It would be valuable to also describe and define how such an aggregated CarePlan would/could be send leveraging, for example FHIR Bundle.

      Please add the technical information (diagrams, a Profile on FHIR Bundle, Capability statement requirements etc.. to inform and provide guidance to developers/implementers prior to the STU ballot in September 2023

      Attachments

        Activity

          People

            Unassigned Unassigned
            GDolin Gay Dolin
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: