1 / 24

VA-OSEHRA Scheduling Kick-off …Building a community submission

VA-OSEHRA Scheduling Kick-off …Building a community submission. Introductions Level-Setting Project Schedule and Tech Overview Discussion: How are we going to work? Solutioning Drill-down. Agenda. One administrative item….

penn
Télécharger la présentation

VA-OSEHRA Scheduling Kick-off …Building a community submission

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. VA-OSEHRA Scheduling Kick-off…Building a community submission

  2. Introductions • Level-Setting • Project Schedule and Tech Overview • Discussion: How are we going to work? • Solutioning Drill-down Agenda

  3. One administrative item… • We have received a request (and form) to join the community from Ventera Corporation • They intend to bring FTEE technical resources, Java and .NET as needed by the team • Their self-interest is to broaden their understanding and exposure to VHA systems • HP recommends we endorse their membership

  4. Introductions

  5. Partners

  6. Current Team * Designates spokesperson for the organization on new community members

  7. Project Execution

  8. Running the Meritocracy: For Organizations From this point forward, all requests to join the community will be reviewed and decided BY the community An existing community member must endorse membership (e.g., help with value proposition, align objectives, vet solution and cultural fit, etc.). Onboarding occurs via a unanimous community vote in support We are working on a community set of principles to clarify IP policy, modus operandai, etc. Once in the community, you have all rights of the community and participate in ongoing decisions

  9. Running the Meritocracy: For Individuals Roles and Teams will be identified by the PM and Tech Lead, with input and feedback from the team As organizations begin to engage, they will bring forward candidates people to fill roles either in delivery or on teams Candidate individuals are reviewed by the team of peers, in addition to the PM and technical lead Unanimous support is required to install a new individual Individuals are just that. In other words, a slot is held by a person, not a company. If someone is to “roll off”, the new person must be installed based on their merit. If needed, a conditional approval can be done to “see how it goes” with a new member.

  10. Solution Concept / Roles& Responsibilities HP Enterprise Services • VistA Scheduling (MUMPS & Interfaces into) • SOA Scheduling Service API Design (joint with Microsoft) • Design, Architecture, Development & Testing Resources • Development Environments Microsoft • Scheduling Engine • SOA Scheduling Service API Design (joint with Microsoft) • Design, Architecture, Development & Testing Resources Parsons Institute of Information Mapping • User Interface • User Experience Solutioning focusing on usability • Existing User Interface Source Code • Limited Development & Testing Resources Red Hat • SOA Platform including Business Rules Engine (Drools), ESB, Business Process Engine • Design, Architecture, Development & Testing Resources

  11. How are we going to work Project Execution • Project Manager • List of Deliverables • Master Project Plan with milestones (sub project plans may exist) Solution Committee • The Committee will design and ensure that the overall solution is not compromised • How does one get a seat at the table? The existing committee will identify the needed roles and review the applicants Activities • Work groups & Sub Work groups Responsibility Assignment • Each task and deliverable will have an owner (a person) • Task delivery may be an integrated team or assigned a single organizational responsibility, • The owner of each task owns the delivery model based upon the team • “Outsource” decisions are based upon capability, resource commitment, and community confidence • The PM owns assignment responsibilities for each task, and can make substitutions if necessary

  12. Teams and Workgroups Workgroups • A limited number of cross-deliverable workgroups will be formed (e.g., “Solution Committee”) • These will have very limited membership and serve to advise Project Leadership • Goal is to keep everything practical while still providing the opportunity for feedback and course-correction Delivery Teams • Each will have a single owner with responsibility for corresponding deliverable(s) • Leadership and staffing will be based upon best-fit to task • Team membership based upon resource availability and meritocracy

  13. Team Structure ??? Project Manager Ken Rubin Solution Architect Teams &Teammates Teams &Teammates Teams & Teammates ??? Technical Lead Solution Committee Member Member Member

  14. List of Deliverables • Document the System Design (SDD) – evolving document • Use Case Analysis • API Design • Test Plan • Design, Develop & Test the Components • User Interface • Business Processes (BPMN) • Message Routing (ESB & BPEL) • Scheduling Engine (MS Dynamics) • Business Rules (Drools Expert\Guvnor) • Event Management (Drools Fusion) • Schedule Workflow • META-Data Management • Resource Management • Notification Service • VistA Enhancements & Interfaces to VistA • Reporting • Mock Services (Access Control & Authentication) • Deployment Plan • Lessons Learned

  15. Schedule (switch to the WBS) Note that skillset allocation and resourcing (LOE) will be done over the coming week…

  16. Solutioning

  17. Technology Stack • MUMPs • Java\J2EE • Dynamics (.NET) • Red Hat SOA Platform (JBoss, ESB, Drools, jBPM)JSF (Java Server Faces) • FLEX • Weblogic • MS SQL Server • XML\XSD\XSLT • Web Services (RESTful & SOAP) • BPMN

  18. Scheduling “Application” Design – MUMPS Scheduling Service (Corellating) Enterprise Service Bus VistA CPRS API VistA Laboratory API • Note: • Authoritative schedule is managed by the service • All local updates occur via the service • Sync with the local schedule is done via new APIs • All inter-package calls are done via new APIs • Cross-facility schedule management is done via the correlating service (Legacy) VistA Scheduling Package New Functional Capabilities Appointment Mgmt API Hospital Location File SOA Service - Local Waitlist Mgmt API Multiple Appointment Booking API Patient Care Encounter API User Experience

  19. Solution Concept – Component Diagram Schedule Analytics Dependency Management Middle Tier & Back-End User Profile Service Resource Profile / Preference Service Scheduling Svc - Correlation Audit Service Access Control Authentication Service Scheduling Service - Core Workflow Management Service Notification Service Business Rules Engine Open API Open API Open API Open API Open API Open API Open API API / Wrappering Development MDWS Waitlist Management Event Mgmt(trigger events) MUMPS App Enhancement User Experience / Interface External Sync (devices, personal calendar) Help MUMPS App Enhancement Application & UI

  20. Conceptual Architecture

  21. Federated Approach

  22. Scheduling Service

  23. Where do we go from here? • Form Solution Committee • Establish lines of communication (Wiki…? Weekly get together, etc) • Start assigning deliverables with milestones

More Related