Date

01 Mar 2023

 Participants

List meeting participants using their @ mention names

• Martha Vasquez

• Steve Conrad

• Jonas Bergmeier

 Goals

List goals for this meeting (e.g., Set design priorities for FY19)

1. Define scope and goals of upcoming sessions

2. Review index of information

3. Test run over at least one wireframe to review BB involvement

 Discussion topics

 Action items

Add action items to close the loop on open questions or discussion topics:

• Steve Conrad GDPR and Data privacy → review current state 17 Mar 2023
• review https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements 03 Apr 2023 Jonas Bergmeier Martha Vasquez
• Artun Gürkan Martha Vasquez Jonas Bergmeier : try to identify workflow patterns (“capabilities”) for our USCT and share results with Steve Conrad / Wes Brown 17 Mar 2023
• Jonas Bergmeier create ticket for this and share with others 03 Mar 2023
• add Gitbook links to BB in https://govstack-global.atlassian.net/wiki/spaces/DEMO/pages/edit-v2/177012747 Jonas Bergmeier 03 Mar 2023

 Decisions

Type /decision to record the decisions you make in this meeting:

Follow-Up on 06 Mar 2023

Martha Vasquez Steve Conrad Artun Gürkan Jonas Bergmeier

Goals

• Test run over at least one wireframe to review BB involvement: Identify explicit UI and action-based BB involvement in USCT Simulation

• Check in regarding capabilities: If, when and could we contribute and feedback?

Notes and Action Items

Steves Feedback on Wireframes

• Payment - adding Voucher payment options, currently only bank options visible

• Wireframes Feedback - Create more versions of different states (e.g. Civil Servant view, more possible outcomes, validation pages)

• Data storage - where is it stored right now? Additional data, registration, digital registry not sufficient enough

• Localisation - multi language options should be considered

Goals - Test run Notes

• ID Buildingblock - Authentication; Information Mediators, workflow building block

  • Would we store a list of civil servants and their roles on a digital registry?
    Where would we store the list?
    Not defined by the current building blocks

  • Rolebased management is part of the security but not defined yet.

  • Registry topic - clarification necessary for the MVP

  • Is there a separate database that will store information about civil servants (including their roles/permissions)

  • What BBs manage the login process? The ID BB is just for foundational ID, so how is login managed?

• https://docs.google.com/document/d/1yyuzxfAQndrxkNaya5kcSbhc9hFqQ2vZtUF4aDPdvaI/edit related BB

• identify the high level BBs for the next steps

• Digital registry database stores who is registered and enrolled

• Workflow BB - which information (Programs) does the civil servant has access to?

• https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/PzBEEsm2haAbBj2uBAKN/consent

Action Item

• Registry / identification BB details should be clarified for the MVP Steve Conrad
• Rework package description and additional information, wireframe, so that the context is clear; info depends on the user Artun Gürkan Martha Vasquez
• identify parts of the USCT journey which could be transferred into other use cases Jonas Bergmeier Artun Gürkan Martha Vasquez