Difference between revisions of "Minutes - Referral WG 2020-11-16"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | ===== Attendees ===== | + | ===== Attendees ===== |
* Robin Bosman | * Robin Bosman | ||
* Jamie Verelst | * Jamie Verelst | ||
| − | * | + | * Frederic Istace |
| − | * | + | * Frederik De Kegel |
* Kristof Jaubin | * Kristof Jaubin | ||
| − | |||
| − | |||
* Karlien Erauw | * Karlien Erauw | ||
* Hans De Keersmaecker | * Hans De Keersmaecker | ||
| − | * | + | * Jos Bellen |
| − | |||
* Paul Neyens | * Paul Neyens | ||
| − | |||
* 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 ===== | ||
| − | * | + | * 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
Contents
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
- Peter is sharing the project planning for the Labo reporting
- Next Meeting: Monday November 30 at 4PM
- Action points for all: please review the implementation guide & send us your comments (through the feedback icon)
