You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Objectives
- FHIR Terminology Services and Resources
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
---|
1 | Welcome and introductions | 5 | | Recording + Notes. Note that this meeting will clash with the HL7 meeting in Cologne and the timings will not line up to allow a joint call. We agreed to proceed as planned, with expected reduced numbers. |
2 | Summary of previous week | 5 | | |
3 | $validate-code behaviour | 20 | |
|
4 | Main item for discussion | 60 | | SNOMED CT canonical CodeSystem resource- Review and attempt to resolve detail questions
- Issue around extensions and what this CodeSystem resource actually represents
|
5 | Current items | 10 | | - SNOMED CT "Universal" Edition
- Definitely useful to have a catalogue of all concepts ever issued if not a proper edition which may be much harder?
- Is this work for this group, or should this be handed on to a more appropriate SI group?
- Check and fix ECL in the FHIR spec
- Is there a way to systematically identify all ECL expressions in the FHIR spec?
- If we run these through validation is there appetite/volunteers to review and fix them as feedback to the spec?
- Is there a way to integrate ECL validation into the FHIR spec tooling to prevent recurrence?
- Rob Hausam to progress Michael's tracker item on this issue.
- Normal form and normal form terse definition
- Rob Hausam to progress returning NormalFormTerse to the page.
- Linda Bird to progress defining Terse Normal Form with the Family of Languages group (Rob Hausam confirms needed for July)
- SLPG agreed that the Languages group is not the appropriate forum for this definition. Instead, we believe this should be defined in the DL subgroup of the Modelling Advisory Group.
- Also agreed that the terms that need defining are "Canonical Normal Form" (which is terse by definition) and "Necessary Long Normal Form"
|
6 | Review of "Using SNOMED with FHIR" page
| 5 | | All participants are invited to review this local copy of that page. - Section 4.2.1.0.5 suggestion that we terse Normal Form properties (Peter J disagreed). Clarity needed on which Normal Form is being represented (eg breaking sufficiently defined concepts down to their primitive components, unlike what is supplied in the browser). Further discussion needed on what these properties are being used for. Perhaps only 1 is necessary since terms can be added/removed as required
- Supplements are a possible way to allow language reference set type functionality.
|
7 | Review of TS Collaborative Work | 5 | | Collaborative Work |
8 | Any other business
|
|
|
Next Meeting: Tuesday 12 June Questions for next week: |
Meeting Files
No files shared here yet.