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

From Health Level 7 Belgium Wiki
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
===== Attendees =====  
+
===== Attendees =====
* Robin Bosman -
+
* Robin Bosman
* Jamie Verelst -
+
* Jamie Verelst
* Kristof Jaubin -
+
* Frederic Istace
 
* Frederik De Kegel
 
* Frederik De Kegel
* Frederic Istace
+
* Kristof Jaubin
* Karlien Erauw -
+
* Karlien Erauw
* Hans De Keersmaecker -
+
* Hans De Keersmaecker
* Paul Neyens -
+
* Jos Bellen
 +
* Paul Neyens
 +
* Dr Alain Derom
 +
* Theo Schumacher
 +
* Tom Fiers
 
* Frank Vandewiele
 
* Frank Vandewiele
* Dr Alain Derom -
 
* Theo Schumacher -
 
* Tom Fiers -
 
* Dieter De Gruyter -
 
* Frank Vandewiele -
 
* Olivier Lothaire -
 
* Mieke Buckinx -
 
 
 
* Peter Laridon
 
* Peter Laridon
 
* Benny Verhamme
 
* Benny Verhamme
* Jos Bellen
 
  
 
===== Excused =====  
 
===== Excused =====  
Line 30: Line 25:
  
 
===== Minutes =====
 
===== Minutes =====
* Based on the comments raised during last week's meeting the following changes have been made in the implementation guide, in the Guidance part:
+
* New comments came in since last week
::* section 3.6 Versioning of reports: the combination of system and identifier needs to be globally unique
+
::* 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.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
 
::* 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

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)