Incomplete tasks from meetings

Description	Due date	Assignee	Task appears on
Reoccurring Bi Weekly Meetings. Cadence start July 5th 12:30pm-1:30pm EST			2019-06-21 Platform Architecture Meeting notes
Tentative Cancel the 5th			2019-06-21 Platform Architecture Meeting notes
Alternate week of Product call			2019-06-21 Platform Architecture Meeting notes
HSPC Platform Architecture Activities: Nominal Timeline: 30 May: Project Plan and Public Project Sketch (scope, etc.) 15 July: Pre-Alpha Work on each artifact; Clarity around direction and approach, but detail incomplete. Face-to-Face: Late July (ish)? September 13: Alpha Draft Release Candidate 1 October: Publish to HSPC the Alpha Document Workstream 1: - Artifact 1: Scope and purpose , and product of HSPC platform (inform interrelationship among projects and products) – (See intro material above) [ Bo ] - Artifact 1: Elaborate this into a short document: The products of the architecture? - Blueprint for …… - Enabler for the creation of a certification platform - Reference API specification - Visual depiction of the components and the interrelationships of those components – Platform 5/15: Bo is working on an initial-cut draft document Workstream 2: - Artifact 2: Enumerated list of capabilities (relate to what is out there in the sandbox, or what is likely to be in short-window. Roadmap?) . Hierarchial [Ken] Activities to undertake: Workstream 3: - Artifact 3: Map between business function (concerns) and capabilities. Crosswalk. (Key use cases enabled?). Systems/services? [ Lorraine ]			2019-05-15 Platform Architecture Meeting notes
Next Steps – · 5 or 6 on call and start to bring in other folks point zero to draft on first. · Team work collectively on each of the artifacts · The scope and purpose {It's defining the product architecture and how it's going to be · One artifact, ALPHA and artifact a Purpose is artifact one · Artifact two with the enumerated list of capabilities? Grid or list? · Under capability to generic health system rap map there should be a crosswalk within capabilities and in the systems · The actual capability map, under system, some of the systems column in the summarizing · This defines a business guidance · What are we trying to do as a capability? · What are the physical mental station in terms of systems, four components that satisfy those needs? · Want to be able to release fall, need to get practical · Think backwards for what we're going to time that we do have. · Budget, your ideas are going to be some staff time to help · Set participation expect patience for contributors The first release. · Do we want to talk about some specific next steps? · How many how many people are going to be additional seven? · Weekly calls (1-hour sessions) · Set up a doodle · Maybe it the short term? · Try to advance the word and frame the boundaries. · See if we can get one of these artifacts far enough along that we can then open it to the community and get more involvement. · In addition: o Get that front page on the new website saying same thing for the roadmap o 1 to 2pages as visual as possible for the website that new visitors will be able to just click on directly from the homepage, and within one click, just be able to get information			2019-05-30 Platform Architecture Meeting notes

All meeting notes

Title	Creator	Modified
2019-05-30 Platform Architecture Meeting notes	Sharnita Riley	Jul 09, 2019
2019-05-15 Platform Architecture Meeting notes	Sharnita Riley	Jun 24, 2019
2019-06-21 Platform Architecture Meeting notes	Sharnita Riley	Jun 24, 2019

Browser not supported