Difference between revisions of "Minutes - Patient Dossier WG 2023-12-14"

From Health Level 7 Belgium Wiki
Line 26: Line 26:
  
 
=== Agenda ===
 
=== Agenda ===
* Review implementation guide and resolve issues/questions for patient will
+
* Final review implementation guide and resolve issues/questions for patient will
* Plan for upcoming meetings
+
* Plan upcoming work and meetings
  
 
=== Minutes ===
 
=== Minutes ===
 
* Work on Patient Will is almost finished
 
* Work on Patient Will is almost finished
::* an email has been sent out regarding the  
+
::* an email has been sent out regarding the publication, review is open until 22 Dec, publication is planned for 12 Jan
::* we will start these meetings in January, most probably as from 11 Jan
+
::* see logical model here: https://build.fhir.org/ig/hl7-be/patientwill/branches/issue-1/StructureDefinition-BeModelPatientWill.html
::* we need to indentify the involved stakeholders, f.e. from Data Capabilities projects, HL7 Belgium will look into this
+
::* see implementation guide here: https://build.fhir.org/ig/hl7-be/patientwill/branches/issue-1
::* eBirth is a priority so we will start working on this, this includes condition and observation, it is mainly about malformation congenital, afterwards goal is to work on addiction
+
::¨issues can be generated here: https://github.com/hl7-be/patientwill/issues/
  
* Patient will
+
* Upcoming work on observation and problem list
::* FYI: The business rules document version 1.1 can be found [https://github.com/hl7-be/patientwill/issues/12 here in NL and FR]
+
::* we will start these meetings on 11 January
::* we look at the logical mode: [https://build.fhir.org/ig/hl7-be/patientwill/branches/issue-1/StructureDefinition-BeModelPatientWill.html see here]
+
::* this meeting will be prepared in advcance by HL7 Belgium and RIZIV (incl. setting priorities)
::::* the representative is the one who is officially mandated to represent the patient - recorder description will be updated
+
::* we need to identify the involved stakeholders, f.e. from the Data Capabilities projects, HL7 Belgium will reach out to already identified stakeholders
::::* source: possibility to add a URI or pdf - binary or uri
 
::::* changes will be made
 
  
::* FHIR profile: [https://build.fhir.org/ig/hl7-be/patientwill/branches/issue-1/StructureDefinition-be-patientwill.html see here]
+
::* what about a general representative for the patient ? [https://github.com/hl7-be/patientwill/issues/13 see issue 13]
::::* do we make the identifier mandatory? no and more than one is possible
+
::::* RIZIV has reached to FOD Volksgezondheid, issue remains open
::::* proposal to adopt the same system as for UHMEP
 
::::* you provide identifier in a http header when sending for the first time, the receiving system will communicate an identifier to the sending system ; if sthg goes wrong, you can re-send the same request using the same identifier, the receiving system will send that he already processed the request. The vaults will be responsible to assign a unique identifier
 
::::* status: is a code, not a codeable concept
 
::::* scope: is not on the logical model, mustSupport must be removed
 
::::::* related to [https://github.com/hl7-be/patientwill/issues/11 issue], issue can be closed
 
::::::* business rules document have to indicate that it is not used
 
::::* scope is mandatory in the int'l profile (in R4 - in R5 is disappears), what will be the default value ; since it is not used, it does not matter what i
 
::::::* an extension will be made to the valueset, and a value "not applicable" will be added
 
::::* category is mustSupport and mandatory: has to be changed into mandatory in logical model
 
::::*  the performer is the representative
 
::::* recorder will be used in all caresets, we have created a BeRecorder, description will be updated
 
::::* source: can be a reference, can be binary file
 
::::* policyRule: is not in logical model, we will remove it as it is not mandatory in the int'l profile
 
::::* provision refers to WillCode etc from the logical model
 
::::::*  status seems to be missing as it is not the same as type, but we can use that status higher up
 
::::::* code is mandatory
 
::::* note: we miss it here, we can add BeNote that we have created and will be there in all caresets
 
 
 
::* what about a general representative for the patient ? see issue 13
 
::::* RIZIV will have to look into it
 
::::* is it a possibility there the fallback is defined by law, not by this profile
 
::::* is not blocking but could be an improvement
 
  
 
* Next actions:
 
* Next actions:
::* final review of last changes before merging
+
::* prepare publication of patient will
 +
::* prepare work on observation and observation
  
 
'''Next Patient Dossier/Observation & Problem WG meeting: 11 January at 9AM'''
 
'''Next Patient Dossier/Observation & Problem WG meeting: 11 January at 9AM'''

Revision as of 12:56, 14 December 2023

Attendees

  • Alexis Van Zeveren
  • Anne Nerenhausen
  • Bart Decuypere
  • Elisabeth Buekers
  • Hans De Keersmaeker
  • Karlien Erauw
  • Pablo Christiaens
  • Veerle Michiels

Excused

  • Brecht Van Vooren
  • Félix De Tavernier
  • François Depelchin
  • Hanne Vuegen
  • Isabelle Pollet
  • Jean-Michel Polfliet
  • Jens Penny
  • José Costa Teixeira
  • Nick Hermans
  • Philippe Baise
  • Sam Jocqué
  • Tom De Backer
  • Walter Bollaert
  • Wouter De Jonghe

Agenda

  • Final review implementation guide and resolve issues/questions for patient will
  • Plan upcoming work and meetings

Minutes

  • Work on Patient Will is almost finished
¨issues can be generated here: https://github.com/hl7-be/patientwill/issues/
  • Upcoming work on observation and problem list
  • we will start these meetings on 11 January
  • this meeting will be prepared in advcance by HL7 Belgium and RIZIV (incl. setting priorities)
  • we need to identify the involved stakeholders, f.e. from the Data Capabilities projects, HL7 Belgium will reach out to already identified stakeholders
  • what about a general representative for the patient ? see issue 13
  • RIZIV has reached to FOD Volksgezondheid, issue remains open
  • Next actions:
  • prepare publication of patient will
  • prepare work on observation and observation

Next Patient Dossier/Observation & Problem WG meeting: 11 January at 9AM