Difference between revisions of "Minutes - Referral WG 2020-11-16"

From Health Level 7 Belgium Wiki
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
===== Attendees =====  
+
===== Attendees =====
 
* Robin Bosman
 
* Robin Bosman
 
* Jamie Verelst
 
* Jamie Verelst
* Benny Verhamme
+
* Frederic Istace
* Jos Bellen
+
* Frederik De Kegel
 
* Kristof Jaubin
 
* Kristof Jaubin
* Frederik De Kegel
 
* Frederic Istace
 
 
* Karlien Erauw
 
* Karlien Erauw
 
* Hans De Keersmaecker
 
* Hans De Keersmaecker
* Peter Laridon
+
* Jos Bellen
* Frederik Lenaerts
 
 
* Paul Neyens
 
* Paul Neyens
* Frank Vandewiele
 
 
* Dr Alain Derom
 
* Dr Alain Derom
 
* Theo Schumacher
 
* Theo Schumacher
 
* Tom Fiers
 
* Tom Fiers
 +
* Frank Vandewiele
 +
* Peter Laridon
 +
* Benny Verhamme
  
 
===== Excused =====  
 
===== Excused =====  
Line 26: Line 25:
  
 
===== Minutes =====
 
===== Minutes =====
* Comment on versioning (business identifier): in guidance in 3.6 : the combination of system and identifier needs to be globally unique
+
* New comments came in since last week
* Comment on replacing report (use of extensions): guidance has been simplified in 3.7; report can have a version or a status. It is up to the receiver to give the correct interpretation
+
::* use of images
* Clarification on UCUM codes in Guidance page - sentence has been added: highly recommended to use UCUM's way to express units
+
section 3.6 Versioning of reports: the combination of system and identifier needs to be globally unique
 +
::* section 3.7 Relating reports: reports can have a version and/or a status --> It is up to a receiving consumer, when it receives a new version of a report to correctly interpret any change in statuses on an Observation. When a diagnosticReport is solicited by a party, it should always receive the most up to date version and again, it is up to the consuming party to correctly interpret statuses.
 +
::* section 3.10.2 Expression of results : Clarification on UCUM , sentence has been added: it is HIGHLY RECOMMENDED to always use the UCUM way to express units
 +
 
 +
* Project related information - by Peter Laridon, eHealth Platform
 +
::* Peter is sharing the [https://drive.google.com/file/d/1bN6veZPh1q3TQNjzMonT2V4MdM_-L6Nn/view?usp=sharing project planning] for the Labo reporting
 +
 
  
 
* '''Next Meeting:''' Monday November 30 at 4PM  
 
* '''Next Meeting:''' Monday November 30 at 4PM  
 
* '''Action points for all:''' please review the implementation guide & send us your comments (through the feedback icon)
 
* '''Action points for all:''' please review the implementation guide & send us your comments (through the feedback icon)

Latest revision as of 12:17, 23 December 2020

Attendees
  • Robin Bosman
  • Jamie Verelst
  • Frederic Istace
  • Frederik De Kegel
  • Kristof Jaubin
  • Karlien Erauw
  • Hans De Keersmaecker
  • Jos Bellen
  • Paul Neyens
  • Dr Alain Derom
  • Theo Schumacher
  • Tom Fiers
  • Frank Vandewiele
  • Peter Laridon
  • Benny Verhamme
Excused
  • José Costa Teixeira
  • Dieter De Gruyter
Agenda
  • recent changes in the implementation guide
  • project related information sharing
Minutes
  • New comments came in since last week
  • use of images

section 3.6 Versioning of reports: the combination of system and identifier needs to be globally unique

  • section 3.7 Relating reports: reports can have a version and/or a status --> It is up to a receiving consumer, when it receives a new version of a report to correctly interpret any change in statuses on an Observation. When a diagnosticReport is solicited by a party, it should always receive the most up to date version and again, it is up to the consuming party to correctly interpret statuses.
  • section 3.10.2 Expression of results : Clarification on UCUM , sentence has been added: it is HIGHLY RECOMMENDED to always use the UCUM way to express units
  • Project related information - by Peter Laridon, eHealth Platform


  • Next Meeting: Monday November 30 at 4PM
  • Action points for all: please review the implementation guide & send us your comments (through the feedback icon)