Dynamic Care Planning Meetings: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Ejones (talk | contribs)
1,406 edits
No edit summary
Ejones (talk | contribs)
1,406 edits
No edit summary
Line 1: Line 1:
This Profile team meets on Mondays 10-11:00 EST
This Profile team meets on Mondays 10-11:00 EST
Please navigate to [https://himss.webex.com https://himss.webex.com] for call in information.  
Please navigate to [https://himss.webex.com https://himss.webex.com] for call in information.  
Profile Supporting documents are here [ftp://ftp.ihe.net/Patient_Care_Coordination/yr12_2016-2017/Technical%20Committee/DynamicCarePlanning/]




Line 8: Line 10:
== Monday November 30, 2015 ==
== Monday November 30, 2015 ==
Attendees:  
Attendees:  
Anne Diamond
* Anne Diamond
Lisa Nelson
* Lisa Nelson
Emma Jones
* Emma Jones
Keith Boone
* Keith Boone
Amit Popat
* Amit Popat
George cole
* George cole
Denise Downing
* Denise Downing
Elena Vio
* Elena Vio
 
* Gunther Meyer
Did I miss someone?
* Did I miss someone?


Goal for Today's call
Goal for Today's call
Line 23: Line 25:
2. Discuss concerns with scope and infrastructure and what we were thinking about profiling in terms of CCS Capabilities
2. Discuss concerns with scope and infrastructure and what we were thinking about profiling in terms of CCS Capabilities


Use Cases
* Use Cases
Decided we should do two - transition of care and chronic disease management (Chronic disease management - can be useful in Canada)
** Decided we should do two - transition of care and chronic disease management (Chronic disease management - can be useful in Canada)
To assist with marketing suggestion made to ensure we include support of MU CCDS
** To assist with marketing suggestion made to ensure we include support of MU CCDS
Recommendation made to not be specific with use of 'Post-acute' - need to keep it high level and more generalized. Post-acute means different things to different folks
** Recommendation made to not be specific with use of 'Post-acute' - need to keep it high level and more generalized. Post-acute means different things to different folks
Suggestion to flush out the use case before we work on the transactions and actors
** Suggestion to flush out the use case before we work on the transactions and actors
 
 
Scope and infrastructure
Reviewed the CCS capabilities we may need to support
Discussion about the scope of what we will profile - the CCS capabilities- this will be the actors and transactions.
Suggestion made to focus on care Plan management capabilities primarily
Discussion about combination of subscribing and publishing - can be logically and virtual
Discussion about not needing to do anything special to have a transaction that is to 'create the plan'. Let that be a pre-condition, one or more care plan exists and this is the process to get those plans aligned and centralized
 
George presented the 'Back of the napkin' idea


Actor A provides content, actor B pulls data out of the care plan


Certain set of FHIR operations - can get multiple FHIR servers to synchronize their activities. There is a subscription resource in FHIR that can set up queries to query- resource describing a query
* Scope and infrastructure
** Reviewed the CCS capabilities we may need to support
** Discussion about the scope of what we will profile - the CCS capabilities- this will be the actors and transactions.
** Suggestion made to focus on care Plan management capabilities primarily
** Discussion about combination of subscribing and publishing - can be logically and virtual
** Discussion about not needing to do anything special to have a transaction that is to 'create the plan'. Let that be a pre-condition, one or more care plan exists and this is the process to get those plans aligned and centralized


Discussion about resolving patient identity. Community EMPI, PDQ - use of PQm
*George presented the 'Back of the napkin' idea
First approach is to do a handshake about what patient we're talking about - we would have to profile this -  
** Actor A provides content, actor B pulls data out of the care plan
First we have to know the identity - an agreed upon identity
** Certain set of FHIR operations - can get multiple FHIR servers to synchronize their activities. There is a subscription resource in FHIR that can set up queries to query-  resource describing a query
Or
** Discussion about resolving patient identity. Community EMPI, PDQ - use of PQm
Use chaining - care plan associated with patient.  
** First approach is to do a handshake about what patient we're talking about - we would have to profile this -  
Federated - Use a network of some sort. Community exchange will handle the staring. Lisa's Star.  
*** First we have to know the identity - an agreed upon identity Or Use chaining - care plan associated with patient.  
** Lisa presented her 'Star' idea
*** Federated - Use a network of some sort. Community exchange will handle the staring. Lisa's Star.  


Call ended. Next meeting Monday Dec 7th
Call ended. Next meeting Monday Dec 7th

Revision as of 16:56, 1 December 2015

This Profile team meets on Mondays 10-11:00 EST Please navigate to https://himss.webex.com for call in information.

Profile Supporting documents are here [1]


Meeting Minutes

Monday November 30, 2015

Attendees:

  • Anne Diamond
  • Lisa Nelson
  • Emma Jones
  • Keith Boone
  • Amit Popat
  • George cole
  • Denise Downing
  • Elena Vio
  • Gunther Meyer
  • Did I miss someone?

Goal for Today's call 1. Need to determine the Use cases we will need 2. Discuss concerns with scope and infrastructure and what we were thinking about profiling in terms of CCS Capabilities

  • Use Cases
    • Decided we should do two - transition of care and chronic disease management (Chronic disease management - can be useful in Canada)
    • To assist with marketing suggestion made to ensure we include support of MU CCDS
    • Recommendation made to not be specific with use of 'Post-acute' - need to keep it high level and more generalized. Post-acute means different things to different folks
    • Suggestion to flush out the use case before we work on the transactions and actors


  • Scope and infrastructure
    • Reviewed the CCS capabilities we may need to support
    • Discussion about the scope of what we will profile - the CCS capabilities- this will be the actors and transactions.
    • Suggestion made to focus on care Plan management capabilities primarily
    • Discussion about combination of subscribing and publishing - can be logically and virtual
    • Discussion about not needing to do anything special to have a transaction that is to 'create the plan'. Let that be a pre-condition, one or more care plan exists and this is the process to get those plans aligned and centralized
  • George presented the 'Back of the napkin' idea
    • Actor A provides content, actor B pulls data out of the care plan
    • Certain set of FHIR operations - can get multiple FHIR servers to synchronize their activities. There is a subscription resource in FHIR that can set up queries to query- resource describing a query
    • Discussion about resolving patient identity. Community EMPI, PDQ - use of PQm
    • First approach is to do a handshake about what patient we're talking about - we would have to profile this -
      • First we have to know the identity - an agreed upon identity Or Use chaining - care plan associated with patient.
    • Lisa presented her 'Star' idea
      • Federated - Use a network of some sort. Community exchange will handle the staring. Lisa's Star.

Call ended. Next meeting Monday Dec 7th

Retrieved from "http://wiki.ihe.net/index.php?title=Dynamic_Care_Planning_Meetings&oldid=90926"