Minutes - Patient Dossier WG 2025-11-26
From Health Level 7 Belgium Wiki
Revision as of 10:09, 26 November 2025 by KarlienErauw (talk | contribs)
Attendees
- Brian Thieren
- Ivan Coppieters
- José Costa Teixeira
- Karlien Erauw
- 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
- Sabine Withofs
- 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
, not yet merged
- refusalOfHearingTest is no longer be part of the structured data and is removed from the model
- eye results: issues should have removed, renaming has been done eyeScreeningOutcome, including the 3 individual observations
- inspectionPupilabnormal
- eyeMovementAndPosition
- eyeRemarks
- related person is 1**1: what if there is no info on the mother, should that be the biological mother ; mother should be optional
- Main branch will be what we have agreed upon: main branch will be communicated by email
- In parallel we will have another brach
- updating the issues on https://github.com/hl7-be/childrecord/issues
- 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
Action items
- validating profiles
- discussion with RIZIV to update BusDocuments and launch implementation process
- to decide where to put in BeDocument: in repo core or core clinical ?
Next meeting
- Monday TBC
