Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Attendance can be found Here

Co-Chair and Key Participant information can be found on the Agenda found Here

Discussion items


TimeItemWhoNotes
1:46SNOMED on FHIRRob Hausam

SNOMED on FHIR is a group formed jointly between SNOMED International and HL7 and it intends to provide guidance on how to use SNOMED CT in FHIR. In particular terminology to use SNOMED CT in FHIR - the correct way to specify and define the value set, and also SNOMED terminology services.

https://confluence.ihtsdotools.org/display/FHIR/SNOMED+on+FHIR

There are also pages for using LOINC and other code systems in FHIR but there is concern that this is not delivering consistent ourcomes when code system lists are instantiated.

Ted Klein add discussion on SNOMED+on+FHIR page to the next teleconference call

2:02Ballot reconcilliation FHIR 18685Rob Hausam

VSD 11 - value set status must be active if expansion is present and compose is absent. Discussion with Grahame

Rob McClure moved that :

1: remove VSD 11,

2: Keep the name of ValueSet.status as it is,

3: Change the definition of ValueSet.status to clarify that

a) valueSet status applies only to the value.set.definition (ValueSet.compose)

b) value set expansions are always considered to be stateless (has no status)

4: add 'Value set expansions are always considered to be stateless' to the Comment for ValueSet.expansion. Explain what 'stateless' means in this regard.

Seconded Jim Case.

Vote: Against 0, Abstain 0, For 10

2:29Ballot reconcilliation 18461Rob Hausam


Action items

  •  Ted Klein add discussion on SNOMED+on+FHIR page to the next teleconference call
  • Robert Hausam to add 18685 to the FHIR I meeting tomorrow.
  • No labels