You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
Attendees
Zuzana Srostlik, Davide, Cary, Dhruv, John, Lloyd Dugan, Matt Burton, Tracie, Mike Meier, Mike Cesino, Nathan Vafaie, Peter Haug, Pieter Steyn, Ron Schuldt, Shane McNamee, Trish Williams, Vincent McCauley, Robert, Pawan
Agenda and Minutes
Document any tasks here, Document any decisions on group page
Agenda Item | Lead | Minutes |
---|
| Cary | |
| Tracie | Tracie notes BPM Workshop end of March Maturity model and playbook ACTION: determine what/if we want to contribute? Decision by next session;
|
| Cary, Davide | what to include who to develop
|
| Davide, John | |
| Davide, Cary | ODEF partnership with Process Automation & Enablement Group - leads and next steps; who Process Automation & Enablement Group right now? Mike Cesino to coordinate with Imp WG, sometimes Denis; Process Automation & Enablement Group (Ken Allgood and Ben Cushing); Workgroup Mtg in March? Potential Healthcare DTF;
|
| Davide, Shane | Methodology group RFPs and working groups responding to those; 2+1 areas in the Plus space, could use more BPM; situational data, packaging of complex BPM artifacts, and artifacts; three RFPs are out for response; Lario, White and Butler are leading teams to develop/contribute; those interested should reach out to leads; Call for Papers; strategies around community topics - CAC paper, what other ideas to be reviewed FYI?; focus on automation in healthcare; one doc coming from CAC; additional self-org to submit other papers in this regard; CAC and Causeway approaches; feedback and notional criteria;
|
| Mike/Ron, Denis/ John, Shane | ODEF - what are follow up actions from that; deeper dive discussion; modeling and implementation workgroups on integration of data resources; SDMN RFP - shared data models; common concepts for ODEF to apply; Authoring Patterns and data alignment with mix of applications; purpose of ODEF integrate across different data models (neutral bridge between data models with common concept); implementation workgroup discussion (work in partnership with that team) on the data binding program, approach based on neutral ground; define scopes as modelers; ODEF has been used in an EU application BIOTOPE, ODEF was one of three; this discussion also to occur with Process Automation & Enablement Group; biotope-project.eu; Consent Model Review - 5 minutes today and then deep dive next mtg; opportunity related to pattern development; ACTION: agenda, failure negative patterns; need to define boundaries on what to achieve; dealing with exceptions other than generic way; modeling the “happy” path and only addressing exceptions when uniquely specific and value-add; leave the opportunity to add patterns; deeper dive on this topic; problem solving escalation; ACTION: model ready for feedback; Clinical failure points (two separate points); IHE Connection; IHE USA, profiles and standards, testing for ONC;
|
| | |