Minutes - FHIR Validation Group 2021-09-30

From Health Level 7 Belgium Wiki
Revision as of 09:48, 30 September 2021 by Costateixeira (talk | contribs) (Created page with "Thursday, 30th September 2021, 10:00 CET = Agenda = * Welcome * Process enhancements - lightweight process for communication towards Program Board B * Process enhancements -...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Thursday, 30th September 2021, 10:00 CET

Agenda

  • Welcome
  • Process enhancements - lightweight process for communication towards Program Board B
  • Process enhancements - change management process for FHIR artifacts
  • Process enhancements - change management process for our own process ?


Participants

  • Veerle Michiels (VAZG)
  • Filoretta Velica
  • Félix de Tavernier
  • Anne Nerenhausen
  • Stefan Beerten
  • José Costa Teixeira

Minutes

Process enhancements - lightweight communication towards Program Board B

The current communication to Program Board (via a Project Proposal) is heavy to review at the Program Board meetings. We can improve the communication by notifying the Program Board with a readable summary. This summary should contain:

  • Impact: Functional, Architecture, Adoption, Planning impact, etc. as needed
  • Link to the Project Proposal
  • Status summary of the current project

The Program Board should then have the opportunity to validate the status of the work, and - if anyone wants - look into the details of the use cases and implementation, etc.

Action item (Jean-Michel): Make a summary for the Medication Dispense to see how it looks. If we don't find any blocking issues, we will add it to our process

We can also publish (or send to the Program Board) the current status of the projects and artifacts.

Action item (Anne and José): Check the current XLS for planning (that was made for the Steering Committee) and make a "publishable overview".


Process enhancements - change management for FHIR artifacts

We will reach out to the initial process owners (Wouter and Brecht will advise on who else) to see who can validate the changes to our governance process. We will start working on a new version of the process for those people to validate.

  • BPMN notation is desired (including artifacts)
  • Include NRC in the process
  • Less sequential
  • Include Change management and "Change Request Impact Decision" activity
  • This may include (even if at a different zoom level) the details of the tooling and artifacts such as Pull Requests, Issue management, etc.



Adjourned at 11:44