Peter G. Williams

Rob Hausam

Daniel Karlsson

• 2018-02-13 - SNOMED on FHIR Meeting (TB)
  
  

• Jane Millar working on draft Terms of Reference, to be reviewed by The Member Forum (meeting in February)
• All please review Terms of Reference prior to submission to Member Forum Meeting.

Peter G. Williams

All participants are invited to review this local copy of that page.

Suggestion for text since "Legacy SNOMED Identifiers" has been removed: "Please note that antecedant SNOMED codes (e.g. ...) may not be used with the http://snomed.info/sct code system. Please refer to <insert link> for more information."  

• All comments to be received by 20 February 2018. Potential to ballot for Normative Status.

Query coming from Grahame G. about how implementable this is eg with cross field validation. Risk of introducing performance issues. Perhaps easier to introduce as "Best Practice" for those with the capability to implement.

How constrained should our profiles be eg allowing for non-SNOMED coding? Dion suggested allowing cherry picking from options available. Rob suggested need for expectations of conformance.

Dion McMurtrie

Attempt to achieve conclusion:

• CodeSystem, ValueSet and ConceptMap resource naming, identification and versioning

• Dion McMurtrie to ask Liam Barnes to contribute what is being done for NCTS in Australia
• Rob Hausam to provide tracker item for further discussion.
  GForge tracker #13820
  Add explicit parameters to ValueSet $expand value set and code system version
  https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13820

Dion McMurtrie

Overlap with FHIR Server capabilities / CodeSystem resource. How do we determine for a given FHIR Server which code systems and versions are supported?

https://www.hl7.org/fhir/capabilitystatement.html vs http://build.fhir.org/terminologycapabilities.html

• Sufficient to query the code system resource ? Is not considered sufficient (due to possibility of declared resources not being operationally implemented, ie used for simple storage). Could instead be declared in a capability statement.

• Rob Hausam to supply tracker item on this issue.
  GForge tracker #14539
  The existence of a CodeSystem resource on a server should only be interpreted as a declaration of the code system properties, not as a declaration of server support and expected behavior
  https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14539&start=0
  

Suggestion (GG) that we document the minimal acceptable capabilities of a SNOMED FHIR Server.

Dion McMurtrie

See Collaborative Work :

• Setting up and operating a FHIR terminology service
• Intensional reference sets versus intensional ValueSets
• Review and maintenance of Using SNOMED CT with FHIR page
• Changes to SNOMED CT to improve usage through terminology services
• Medication Resources for drug terminologies

• All - Invitation to fill in capabilities of known FHIR Implementations: Features of Known Servers ( Linda Parisien ? ). Suggestion that this could be taken forward into SnomedInside (MHosking)
• Peter G. Williams to speak to Nick Egarhos about above.
  
• Peter G. Williams Jane Millar Linda Bird to return to issue of identifiers for legacy versions of SNOMED and respond for 20 Feb.
  

Peter G. Williams

Peter G. Williams