PlanDefinition for Care Planning

Profile Development Work

• Meeting is every other Wednesday 2-3pm EST
• Webex
  • Call-in toll-free number (US/Canada): 1-866-469-3239
  • Call-in toll number (US/Canada): 1-650-429-3300
  • Access code:926 359 852

December 6, 2017 Call Notes

• Attendees
  • Emma Jones
  • Denise Downing
  • George Dixon
  • Dr. Holly Miller
  • Raffaele Giordano
  • Thomson Kuhn
  • Laura Heerman-Langford

• Agenda
  • Confirm template to use
  • Discuss if we should write a new profile or add an update to DCP
  • Raffaele use case

• Notes
  • Open Issue - Add recommendation for opt-in for updates as default for when treatment recalls occur - Make a SHALL
  • Raffaele reviewed his pregnancy workflow use case
  • Decision made to work on updating DCP with new profile work
  • Discussed how updates of the carePlan resource occurs in DCP

December 20, 2017 Call Notes

• Attendees
  • Emma Jones
  • Raffaele Giordano
  • Thomson Kuhn
  • John Moehrke
  • Denise Downing
  • Gila Pyke
  • Anna Orlova

• Agenda
  • Review process flow
  • Confirm Actors and start transactions
  • Review Actor Diagram

• Notes
  • Reviewed Actor Transactions diagram
  • Reviewed New Actors and transactions
  • Updated profile template used

January 03, 2018 Call Notes

• Attendees
  • Emma Jones
  • John Moehrke
  • Raffaele Giordano
  • Chris Melo
  • Thomson Kuhn
  • George Dixon
  • Denise Downing

• Agenda
  • Review Actors, transactions, options, actor grouping
  • Plan use case update

• Notes
  • Profile artifacts on FTP site
  • Raffaela will send me his use case
  • Emma will post updated profile on the FTP site.
  • Question about a care plan specific implementation google group - John will start the google group.

January 17, 2018 Call Notes

• Attendees
  • Emma Jones
  • Chris Melo
  • Denise Downing
  • Raffaele Gordano
  • George Dixon
  • Laura Heerman-Langford

• Agenda
  • Review use case

February 28, 2018 Call Notes

• Attendees
  • Emma Jones
  • Gila Pyke
  • George Dixon
  • John Moehrke
  • Raffaele Giordano
  • Jeffrey Danford
  • Thomson Kuhn

• Agenda
  • Review Transactions

Discussion

• walk thru forge to define the constaints and use the output of Forge to define the constraints and drop the definition in volume 2
• Have been working with ClinFHIR as well. ClinFHIR can create the same think and have a better graphical representation.
• Volume 1 - server must support subscription and subscription on plan definition
  • when the user get a list of plan def
• ClinFHIR - can generate the profile and export into Forge
• Transaction - no specific constraints on the transactions can leave as is

Use an apply operation to generate the care plan Suggestions:

• (John) ITI document sharing pattern uses the broader document description that anything can be shared with the specific mimeType - FHIR resouce can be defined as a mimeType. MHD document sharing - change back to mime. Will need to create a format code
• Another suggestion for the interaction between content creator and content consumer is to get rid of content creator and use operations as transactions between Care Plan Contributer and Content Consumer. Don't use RESTFUL transactions.
  • Using $Apply
    • Agreement that the requests $Apply should be an operation - not the usual RESTFUL transaction. See Apply
    • Updates made to Figure X.1-1: DCP Actor Diagram.

To Do

• Emma will post this version on the FTP site for folks to review.

• Agenda
  • Review use case

March 14, 2018 Call Notes

• Attendees
  • Emma Jones
  • George Dixon
  • Gila Pyke
  • Jeff Danford
  • John Moerke
  • Thom Kuhn
  • Sarah Bell
  • Raffaele Giordano

• Agenda
  • Review Transaction - FHIR $Apply

Discussion

• Overview by Jeff Danford
  • Care Plan Guidance service provides a library of planDefinition and activityDefinition resources to Care Plan Contributor
  • Care Plan Contributor acts on the provided planDefinition and activityDefinition resources by using FHIR $Apply operation
  • The $Apply operation causes generation of a care plan that will contain request resources that is used by the Care Plan Service Actor
• To Do

1. Get rid of Content Consumer because it deals with documents.
2. Add one new transaction between Care Plan Contributor and Care Plan Service

• What STU version should we use for the structure definitions?
  • PlanDefinition
  • ActivityDefinition
• STU 4 will be published before the end of the year - use by 2020 at the earliest - no implementation before 2019
• STU 3 will be a better place to start.
• Structured definition tools currently supports STU 3.

March 28, 2018 Call Notes

• Attendees
  • Emma Jones
  • Jeff Danford
  • Raffaele Giordano
  • Sarah Bell
  • George Dixon
  • Thomson Kuhn
  • John Moehrke

• Agenda
  • Review Transaction continue - FHIR $Apply
  • New Structure Definitions needed
    • PlanDefinition - forge
      • Workflow resource - profile with a structure definition (used for messages and document constraints)
      • Creating a structure definition of a planDefinition - defines constraints on a resource. see this as example [1]
    • ActivityDefinition - forge
      • care plan profile will come out of the
      • Workflow resource
    • ImplementationGuide - hand create in xml
    • CapabilityStatement - use grahame's FHIR client.
      • Need to create one for every actor and one for each option
      • IHE capability statement is definition for the actor only in this profile.
        • Kind - kind == "requirements" to indicate that this is a requirements capabiltyStatement indicating desired requirements (not a server)
  • Update existing structure definitions
    • CarePlan - need this to reflect the $Apply operation
    • Subscription

Discussion

• Profile STU 3
• Canonical can continue to evolve.

April 11, 2018 Call Notes

• Attendees
  • Emma Jones
  • Jeff Danford
  • Raffaele Giordano
  • Sarah Bell
  • George Dixon
  • Thomson Kuhn
  • Gila

• Agenda
  • Review Capability Statements
  • Discuss task resource R/T to request resources
  • Start Activity definitions - Emma and Jeff will work off-line for the initial draft

April 25, 2018 Call Notes

• Attendees
  • Emma Jones
  • Thom Kuhn
  • Jeff Danford
  • John Moerhke

• Agenda
  • Discuss task resource R/T to request resources (support for XDW implementations)
  • Review Structure Definitions
• Discussion
• Don't use bold or red in the supplement - bold means IHE CP changes
• Red does not print
• Add a column for IHE PCC Constraints
• CarePlan - any changes needed?
  • identifier.value identifying this is an IHE profile is not needed. this is addressed in .meta of the profile.
• PlanDefinition
  • identifier.value identifying this is an IHE profile is not needed. this is addressed in .meta of the profile.
• ActivityDefinition
  • identifier.value identifying this is an IHE profile is not needed. this is addressed in .meta of the profile.
• Task
  • identifier.value identifying this is an IHE profile is not needed. this is addressed in .meta of the profile.