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

From Health Level 7 Belgium Wiki
Line 26: Line 26:
  
 
===== Minutes =====
 
===== Minutes =====
−
* Comment on versioning (business identifier): in guidance in 3.6 : the combination of system and identifier needs to be globally unique
+
* Based on the comments raised during last week's meeting the following changes have been made in the implementation guide, in the Guidance part:
−
* 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
+
::* section 3.6 Versioning of reports: the combination of system and identifier needs to be globally unique
−
* Clarification on UCUM codes in Guidance page - sentence has been added: highly recommended to use UCUM's way to express units
+
::* 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
 +
{| class="wikitable"
 +
|-
 +
! Faze !! Taken !! Wie !! Doorlooptijd !! Startdatum !! Eindddatum !! Stavaza !! Comments
 +
|-
 +
| 1 || CDA berichten omzetten naar Fhir formaat || eHealth - Robin B || 2 maanden || 1/09/2020|| 30/10/2020 || OK|| Example
 +
|-
 +
| 2 || Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 3 || Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 4 || Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 5 || Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 6 || Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 7|| Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 8 || Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 9 || Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| 10|| Example || Example || Example || Example || Example || Example || Example
 +
|-
 +
| Example || Example || Example || Example || Example || Example || Example || Example
 +
|}
  
 
* '''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)

Revision as of 17:04, 16 November 2020

Attendees
  • Robin Bosman
  • Jamie Verelst
  • Benny Verhamme
  • Jos Bellen
  • Kristof Jaubin
  • Frederik De Kegel
  • Frederic Istace
  • Karlien Erauw
  • Hans De Keersmaecker
  • Peter Laridon
  • Frederik Lenaerts
  • Paul Neyens
  • Frank Vandewiele
  • Dr Alain Derom
  • Theo Schumacher
  • Tom Fiers
Excused
  • José Costa Teixeira
  • Dieter De Gruyter
Agenda
  • recent changes in the implementation guide
  • project related information sharing
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:
  • 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
Faze Taken Wie Doorlooptijd Startdatum Eindddatum Stavaza Comments
1 CDA berichten omzetten naar Fhir formaat eHealth - Robin B 2 maanden 1/09/2020 30/10/2020 OK Example
2 Example Example Example Example Example Example Example
3 Example Example Example Example Example Example Example
4 Example Example Example Example Example Example Example
5 Example Example Example Example Example Example Example
6 Example Example Example Example Example Example Example
7 Example Example Example Example Example Example Example
8 Example Example Example Example Example Example Example
9 Example Example Example Example Example Example Example
10 Example Example Example Example Example Example Example
Example Example Example Example Example Example Example Example
  • Next Meeting: Monday November 30 at 4PM
  • Action points for all: please review the implementation guide & send us your comments (through the feedback icon)
Retrieved from "https://wiki.hl7belgium.org/index.php?title=Minutes_-_Referral_WG_2020-11-16&oldid=659"