1 / 18

Care Plan (CP) Team Meeting Notes (As updated during meeting)

See post meeting notes from Kevin about Storyboards. To join the meeting: Phone Number : +1 770-657-9270 Participant Passcode : 943377 WebEx link is on the wiki ( link below ). Care Plan (CP) Team Meeting Notes (As updated during meeting). André Boudreau (a.boudreau@boroan.ca)

saskia
Download Presentation

Care Plan (CP) Team Meeting Notes (As updated during meeting)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. See post meeting notes from Kevin about Storyboards. To join the meeting: Phone Number: +1 770-657-9270Participant Passcode: 943377 WebExlinkis on the wiki (linkbelow) Care Plan (CP) Team Meeting Notes(As updated during meeting) André Boudreau (a.boudreau@boroan.ca) Laura Heermann Langford (Laura.Heermann@imail.org) 2011-06-22 (No. 16) Care Plan wiki:http://wiki.hl7.org/index.php?title=Care_Plan_Initiative_project_2011 HL7 Patient Care Work Group

  2. Agenda for June 22nd • Minutes of June 8th • Storyboards (Laura, Danny, Susan) • NOTE: this is our top priority deliverable • How will we vet our storyboards? • Chronic Care Sequence Diagram (Luigi) • Care Management Concept Matrix: update (Susan) • Next meeting(s) agenda

  3. Agenda for July 6 • Storyboard vetting process • Storyboards • Perinatology: Laura • Stay healthy: Laura • Home care SB resolution • Models (Luigi) • Requirements (André) • Stakeholders expectations • Next meeting agenda

  4. Meetings During the Summer Period • We will move to a meeting every second week until the end of August. Schedule is: • July 6 • July 20 • August 3 • August 17 • We will keep the intermediate slot in place in case we want to use them for specific cases like… • Review of the ISO CONTSYS work on care plan aspects • Review of EHR-S FM R2 work by the HL7 EHR WG

  5. Future Topics • Review of EHR-S FM R2 work by the HL7 EHR WG: Aug. 17, tentatively • John Ritter, Sue Mitchell, Pat Van Dyke, Lenel James • Review of the ISO CONTSYS work on care plan aspects • André to contact ISO Lead • Care Plan elements from KP, Intermountain, VA, etc. (Laura) • Requirements (André) • EA Vs Eclipse: EA is preferred by many: Luigi, +++ • Comparison of care plan contents (Ian, Laura) • To inform the information model • Start of spreadsheet (Laura…) • Overarching term to use (Ian M.) • Care Plan Glossary • Forward plan- first cut

  6. Participants- WGM Meetg of 2011-06-22 p1

  7. Participants- WGM Meetg of 2011-06-08 p2

  8. Storyboards

  9. Storyboards • Ref file: Care Plan Storyboards-HL7 Patient Care WG- v0.2c 20110621b.docx • Pediatric and Allergy/Intolerance: first draft • See updated Storyboard document • Deferred to next meeting • Home Care: • Resolve /reconcile 2 versions • Acute Care Plan Storyboard: Danny • In progress • Perinatology: Laura • Stay healthy: Laura

  10. Post Meeting Notes by Kevin Coonan • The Care Plan and the Health Concern share a similar issue about state management, and how it gets updated between providers involved with care of a mutual patient. • Both an instance of a Health Concern and a Care Plan need well prescribed use of the Act state machine (along with the associated specific transitions, which need to be part of the picture) to do this.  We need to be very explicit in our use cases and stories about when the status of a plan/problem is updated, and how that updated is communicated to others.  The static semantics isn't the issue here (thankfully), but the interactions are.  This is going to be different in enterprises (which can assume a single broker of Health Concern and Care Plan status, and manage updates to it, as well as record the history of updates) v. a loose federation (which may have some mechanism to pass messages/updates) v. a bunch if separate EHRS which need to exchange content (esp. if in the form of CDA r2, as there is no mechanism to handle status updates other than generating a new document instance).  • An order (ActRequest) is something that also has state, and needs to be managed by a order entry system.  The details of how the order entry system makes its own sausage is out of scope for the Care Plan topic.  The order  state is not going to always agree with the pare plan state.  Care Plan/Health Concern state is pretty easy. • We have to call this out, as well as how interactions between systems/providers are managed to be sure the assumptions are explicit, so that we can be sure that we have a representative set when it comes time to define messages, documents, and services.  As long as we are careful to make this explicit in use cases, things will be OK.  It is just when we make assumptions about updating EHRSs we will get into trouble.

  11. Chronic Care Sequence Diagram • Luigi

  12. Chronic Care Plan Sequence Diagram • See updated Sequence Diagram for Chronic Care SB, next page

  13. Care Management Concept Matrix: update • Susan

  14. Care Management Concept Matrix: update • Descriptions and acronyms have been added • The document will be reviewed with the Case Management Society of America • This matrix provides a high level view of the range of care management situations that can be encountered • We will use the matrix to validate our portfolio of storyboards once we have completed their descriptions and their corresponding models (sequence diagrams, etc.)

  15. Conclusion

  16. Action Items as of 2011-06-22 NB: Completed action items have been removed.

  17. Appendix

More Related