Minutes - Core Profiles WG 2024-11-13

From Health Level 7 Belgium Wiki
Attendees
  • Bart Decuypere
  • Benny Verhamme
  • Brian Thieren
  • Didier Temans
  • Dominiek Leclerq
  • Félix De Tavernier
  • Isabelle Mannekens
  • Ivan Coppieters
  • Jean-Michel Polfliet
  • Karlien Erauw
  • Philippe Baise
  • Pablo Christiaens
  • Tak Hoo Chak
Excused/Not present
  • Annabel Dompas
  • Anne Nerenhausen
  • Anthony Maton
  • Brecht Van Vooren
  • Cyprien Janssens
  • Elien De Koker
  • Erwin Bellon
  • Eva Eggers
  • Emmanuel de Grunne
  • Guy Vandenboer
  • Hanne Vuegen
  • Isabelle Pollet
  • Jacques Yakoub
  • José Costa Teixeira
  • Marcelo Romero-Cors
  • Marie-Alexandra Lambot
  • Maxime Caucheteur
  • Olivier Latignies
  • Nick Hermans
  • Nico Vannieuwenhuyze
  • Philip Sidgwick
  • Ruben Walraevens
  • Stef Hoofd
  • Walter Bollaert
  • Pablo D'Alcantara
  • Steven Van den Berghe
  • Werner De Mulder
  • Yannick Guldentops
Agenda
  • updates & resolution of issues
Minutes
  • Resolution of issues
  • Issue 134: we received feedback from Ilse
  • active will not be part of the logical model because its definition is largely system related and we define nation wide profiles
  • discussion on telecom: telecom will be added to the logical model, but it will be optional. The contactpoint is the contact point for direct communication, this means that in some cases this can be the contactpoint for the closest next-of-kin (then the contact point will also occur under "contact" (=next of kin))
  • we will add contact, communication, generalPractitioner and managingOrganisation, but not in a mandatory way. If this information is explicitly needed in a use case, a specific profile needs to be made.
  • link: we think this relationship is too abstract on a logical level, and we would like to add a more functional relationship for the options that can be expressed by link. If the need arises we will add them on a more functional level.
  • in system to system communication, the name of the organization if often not necessary and an identifier (business) is often enough. We do not want to impose this restriction on those cases. In KMEHR, this is also the case
  • issue can be closed
  • the workgroup suggests to make profiles with a narrower scope (e.g. containing more specific identifiers) for the cases in which they are really required (such as exchange with the vaults, etc... This applies for all core resources, not only Organisation. We will need some clear communication/definition to make the distinction between the two levels. The higher could for instance also be used for internal communication in hospitals, or other settings. It is not the goal to use profiles from other nationalities/countries to handle citizens from those countries in Belgian systems (even internally in hospitals, e.g.)


Next agenda meeting agenda points
  • Resolution of issues & finalize guidelines on packages creation &usage
Next meeting
  • Wednesday 27 November at 9AM