Difference between revisions of "Minutes - Population Health WG 2022-12-20"

From Health Level 7 Belgium Wiki
 
(6 intermediate revisions by the same user not shown)
Line 23: Line 23:
 
::::* there are some issues with the terminologies, NRC has to determine the codes  
 
::::* there are some issues with the terminologies, NRC has to determine the codes  
 
::::* there is a dependency on the dev profile  
 
::::* there is a dependency on the dev profile  
−
 
+
::* this issue can be closed
 
::* [https://drive.google.com/file/d/1XdpeVp132SfVLyyY7SU4PXO3ApPivL6n/view?usp=share_link question on screening, what do we use] ? We will have to check with a doctor/CVKO director : this will be moved to another issue
 
::* [https://drive.google.com/file/d/1XdpeVp132SfVLyyY7SU4PXO3ApPivL6n/view?usp=share_link question on screening, what do we use] ? We will have to check with a doctor/CVKO director : this will be moved to another issue
−
::* this issue can be closed
 
  
 
* [https://github.com/hl7-be/public-health/issues/11 Issue #11]: review references to other resources
 
* [https://github.com/hl7-be/public-health/issues/11 Issue #11]: review references to other resources
−
::* references to BE profiles have to be added where relevant at this time
+
::* references to BE profiles have to be added where relevant at this time and in scope of this work
  
 +
* [https://github.com/hl7-be/public-health/issues/6 Issue #6]: logical model
 +
::* the use of physical data/ resources in logical models is not really orthodox and should be cleaned up. However, we don't mine at this phase and it will be looked into by the HL7 Belgium core team ; meanwhile it is agreed to use the Patient resource in the [https://build.fhir.org/ig/hl7-be/public-health/StructureDefinition-BePopulationScreening.html logical model]
  
−
* [https://github.com/hl7-be/public-health/issues/10 Issue #10]: actors & transactions
+
* [https://github.com/hl7-be/public-health/issues/9 Issue #9]: BeObservation
−
::* Kurt has done some work and has put all the information in the issue itself
+
::* relying on BeObservation : can this pose any issues
 +
::::* code is must support in BeObservation
 +
::::* performer is mandatory : it can be CVKO by default
  
−
* [https://github.com/hl7-be/public-health/issues/9 Issue #9]: BeObservation
+
* [https://github.com/hl7-be/public-health/issues/8 Issue #8]: nextInvitation
−
::* a codeable concept should be used, then LOINC should be used (LOINC was used for labresults, snomed CT for other than labresults)
+
::* code & next possible date is needed
−
::* if LOINC will be used, no changes are needed to
+
::* we would need an extension
−
::* any update from NRC and LOINC responsable persons whether it shoould be LOINC or Snomed CT codes - ( Bart would contact NRC)
+
::* would the resource appointment fit ? we though not
 +
::*  we want it to be a date and a codeable concept to be able to have strings and codes
 +
::::* code could be : excluded indefinitively, you won't receive an invitation anymore
 +
::* the logical model will have to be changed accordingly
 +
::* the valueset and code system has to be created to include the current know codes  
 +
::* a new element nextInvitationDate has to be added
 +
::* issue can be closed once work has been done
  
−
* TBC [https://github.com/hl7-be/public-health/issues/8 Issue #8]: nextInvitation
+
* [https://github.com/hl7-be/public-health/issues/10 Issue #10]: actors & transactions
−
::* appointment doesn't seem to fit
+
::* what is the business workflow ? population screening author sends the screening to the repository
−
::* has change in logical model been made ?
+
::* this is the only transaction for now: update the patient's cancer screening information
 +
::* we will document the transaction including the use of any grouping mechanism e.g. bundle
 +
::::* José will work on a proposal as this is technical work
  
 
* when can we expect a publication ?
 
* when can we expect a publication ?
−
::* actors & transactors have to be added to the guidance : when can this be done ?
+
::* some technical work needs to be done and has to be validated on the meeting of 10 Jan
−
::* if no more remarks, publication can be prepared
+
::* if no more remarks, publication can be prepared for end of Jan
 +
 
 +
::* On Jan 17 we want to do a demo for the GP softs on this new feature - Karlien will invite the GP softs
  
 
=== Action Items ===
 
=== Action Items ===
Line 51: Line 64:
  
 
=== Date next meeting ===
 
=== Date next meeting ===
−
* Tuesday 20 Dec at 10AM
+
* Tuesday 10 Jan at 10AM

Latest revision as of 10:03, 20 December 2022

Attendees

  • Brecht Van Vooren
  • Hanne Vuegen
  • Jean-Michel Polfliet
  • José Costa Teixeira
  • Karlien Erauw
  • Kurt Dhaene
  • Patrick Beyltjens
  • Veerle Michiels

Excused

  • Bart Decuypere

Agenda

  • Resolution of issues

Minutes

  • there are plenty of warnings but not worrisome, some technical ones
  • José did some technical fixes: removing period & space at the end
  • BeLocation was blocking the build, we only have Location
  • there are some issues with the terminologies, NRC has to determine the codes
  • there is a dependency on the dev profile
  • Issue #11: review references to other resources
  • references to BE profiles have to be added where relevant at this time and in scope of this work
  • the use of physical data/ resources in logical models is not really orthodox and should be cleaned up. However, we don't mine at this phase and it will be looked into by the HL7 Belgium core team ; meanwhile it is agreed to use the Patient resource in the logical model
  • relying on BeObservation : can this pose any issues
  • code is must support in BeObservation
  • performer is mandatory : it can be CVKO by default
  • code & next possible date is needed
  • we would need an extension
  • would the resource appointment fit ? we though not
  • we want it to be a date and a codeable concept to be able to have strings and codes
  • code could be : excluded indefinitively, you won't receive an invitation anymore
  • the logical model will have to be changed accordingly
  • the valueset and code system has to be created to include the current know codes
  • a new element nextInvitationDate has to be added
  • issue can be closed once work has been done
  • what is the business workflow ? population screening author sends the screening to the repository
  • this is the only transaction for now: update the patient's cancer screening information
  • we will document the transaction including the use of any grouping mechanism e.g. bundle
  • José will work on a proposal as this is technical work
  • when can we expect a publication ?
  • some technical work needs to be done and has to be validated on the meeting of 10 Jan
  • if no more remarks, publication can be prepared for end of Jan
  • On Jan 17 we want to do a demo for the GP softs on this new feature - Karlien will invite the GP softs

Action Items

  • resolution of remaining open issues

Date next meeting

  • Tuesday 10 Jan at 10AM
Retrieved from "https://wiki.hl7belgium.org/index.php?title=Minutes_-_Population_Health_WG_2022-12-20&oldid=2006"