Minutes - Core Profiles WG 2024-01-24

Attendees

• Anthony Maton
• Bart Decuypere
• Benny Verhamme
• Brian Thieren
• Brecht Van Vooren
• Dominiek Leclerq
• Elien De Koker
• Hanne Vuegen
• Jean-Michel Polfliet
• Karlien Erauw
• Maxime Caucheteur
• Philippe Baise
• Philip Sidgwick
• Pablo Christiaens
• Steven Van den Berge

Excused/Not present

• Anne Nerenhausen
• Cyprien Janssens
• Didier Temans
• Erwin Bellon
• Félix De Tavernier
• Filoretta Velica
• Isabelle Pollet
• José Costa Teixeira
• Lodewijk Sioen
• Marco Busschots
• Nick Hermans
• Nico Vannieuwenhuyze
• Stef Hoofd
• Werner De Mulder

Agenda

• work on patient core profile following up on the raised issues
• set priorities for action items

Minutes

• We look at the issues that have been raised in other HL7 Belgium working groups
• We agree to start working on issue 60 BeCommunication & BeDocumentReference

• NIC is in particular interested in BeCommunication

• hospitals are interested so send RIZIV documents/forms, currently sent by normal post, in a digital way ; some are information only, some have to be checked by OA/VIs. There are 100/200 different forms, linked to regulations. Purpose is to transfer the PDF version of the form in a digital way to the OA/VI. Pdf would be the scanned version of the original form. ePDF would be used. 3 levels of categories would be added (A, B and C). The category would identify the paper document and would determine. Hospitals will need to categorize all the forms that they send. A common taxonomy would have to be defined for all categories (together with RIZIV). some of the documents have to be signed by the patient (accepting the rules, treatment). For this a way has to be found to transfer the signed document.

• needs from other project (Maxime) needs author, content, context and subject seem important for us

• is the practioner an author

• facility type is proposed, from/to which facility the document is referenced ; a value set is proposed. WG decides that this is already covered by context.Related ; but there is already an encounter in context

• we determine the scope of the logical model, therefore we discuss the functional need
• do we need a BE profile?

• we do have the need to have some specific elements to store in the vaults

• we will call the logical model BeModelPatientDocument, there will no longer be an overlap with BeCommunication

• the reference will be used to store any type of data, including unstructured data

Next agenda meeting agenda points

• continue work on document reference
• resolution of issues

Next meetings

• Wednesday 7 February at 9AM