Minutes - Patient Dossier WG 2025-11-26
From Health Level 7 Belgium Wiki
Attendees
- Brian Thieren
- Ivan Coppieters
- José Costa Teixeira
- Karlien Erauw
- Sabine Withofs
- Walter Callebaut
Excused
- Anne Nerenhausen
- Benny Verhamme
- Brecht Van Vooren
- Etienne Cantineau
- Jan Lenssens
- Hanne Vuegen
- Jan Lenssen
- Jean-Michel Polfliet
- Marcelo Romero-Cors
- Philippe Baise
- Werner De Mulder
Agenda
- Review the FHIR work on Child record FHIR IG
Meeting minutes
- FHIR draft logical model and FHIR IG has undergone some changes following our previous meeting
- Opgroeien needs to validate the logical model
- a separate federal IG will be published, separate from eBirth ; howevr the SnomedCT codes from the child record and eBrith have to be aligned, separate meetings will be organised on this
- Logical model is here: https://build.fhir.org/ig/hl7-be/childrecord/branches/draft/en/StructureDefinition-BeModelChildReport.html
- once approved it can be merged to main
- discussion on Related person: it is essential info for the child's health, however child record is not the authentic source : it has to be removed, see new issue https://github.com/hl7-be/childrecord/issues/15
- looking at https://build.fhir.org/ig/hl7-be/childrecord/branches/draft/en/StructureDefinition-BeModelDocument.html
- discussing unique identifier (stays the same upon update), recorded date & author
- presentedForm in PDF is mandatory
- Checking issue 12 (issues from last WG): all has been resolved
- There are dependencies of publication of child record on BeProblem and BeClinicalObservation
- Alignment is necessary b/w the business documentation and the FHIR draft logical model
- Ivan will update the Business Requirements once the FHIR model is stable
- RIZIV/INAMI has a specific template
- We decide to rename the deliverable into ChildReport but keep the repo as childrecord
- Profile has been merged into the main branch, see here: https://build.fhir.org/ig/hl7-be/childrecord/en/StructureDefinition-BeModelChildReport.html
- Ivan to contact RIZIV on terminology codes, see issue 3
Action items
- make changes & move to main branch
- discussion with RIZIV to update BusDocuments
- publication process awaits publication of BeProblem and BeClinicalObservation
- other Patient dossier issue: to decide where to put BeDocument: in repo core or core clinical ?
Next meeting
- TBC: once BeProblem and BeClinicalObservation have been published to validate that the profile is complete and can moved to publication
