Skip to content

Meeting Minutes 2017 09 01

Pace Ricciardelli edited this page Sep 1, 2017 · 1 revision

Agenda

  • New Member Introductions
    • Jesse Springer from WY
    • Duane, Marty, Jennifer, and Gary dialing in on behalf of James Lilly for NM
  • HIT Connect Meeting
    • April 5-6 in Baltimore
    • Abstract is due at the end of the month- will submit one for Poplin
  • Status Roundtable
  • Review Functional Area Assignments
  • Shared Services Update
  • Planning for Next Week

Status Roundtable

  • CNSI

    • Last week - Worked on the overall schedule and plan for the artifacts for providers - sent to Anshuman and Dave
    • This week - Working on Provider Eligibility Process Flow Diagram (draft due 9/29)
    • Blockers? - None
    • Next week, bringing in an additional person to the team – Colby
  • MITRE

    • Last week - Continued investigation of open source messaging, service registration, and service discovery solutions
    • This week - Write first drafts of service definitions for service registration/discovery and messaging. Resend meeting invites to avoid conference call confusion.
    • Blockers? - None
  • Vermont

    • Last week - Progressing on schedule with service definition development, object definition for case management (mid-sprint), extended toward ERDs and context diagrams
    • This week - Delivery of Case Management draft next Friday (9/8/2017)
    • Blockers? - None
    • "Open Source" has come up in conversations a few times and there are misunderstandings about security models in open source work. We should work as a group to correct this whenever we encounter it.

Next week

  • CNSI, VT, MITRE to continue developing service definitions
  • Anshuman to reach out to new members to define their interest in functional areas

Shared Services Update

  • Review of proposed messaging solutions
    • CNSI has used Kafka, it is lightweight, has not seen any major pitfalls
    • VT, NM - SI vendor is proposing a licensed product
  • Review of Service Registration and Discovery
    • NM is taking a human services-wide context, but are planning on more of a microservices architecture
    • MITRE is only building shared services to prove out the service definitions for shared services - states can use this to define whether they have the same infrastructure or not
    • NM is working with a SI to determine whether Oracle Service Bus or IBM Information Bus will be used for shared services

UML Tooling Discussion

  • UML definitions need to be interoperable across all the tools that we are using (ARGO UML, Magic Draw, Sparx, etc.)
  • NM just got licensing for an ER studio tool - most tools support XML data interchange - we should take this into consideration
  • VT can export its work into whatever format we need. The company is very willing to provide technical support
  • VT to start interoperability checks by exporting some items for a test next week