These pages will be used to propose collaborative work topics and to organise the results of this collaborative work under the following high level categories.
Terminology Services Stream
- CodeSystem, ValueSet and ConceptMap resource naming, identification and versioning
- Setting up and operating a FHIR terminology service
- Intensional reference sets versus intensional ValueSets
- Changes to SNOMED CT to improve usage through terminology services
- Update SNOMED CT Search and Data Entry Guide
- SNOMED CT "Universal" Edition
- SNOMED CT canonical CodeSystem resource
- Check and fix ECL in the FHIR spec
- Normal form and normal form terse definition
- Implementation Guide for using SNOMED CT with FHIR
- ConceptMap
- Expand (Valueset)
- FHIR Frequently Asked Questions
- General Implementation Considerations
- Implementing Terminology Services with SNOMED CT
- Introduction to using SNOMED with FHIR
- SNOMED CT Post Coordination in FHIR
- SNOMED specific behaviours
- System Architects working with SNOMED and FHIR
- Terminology Binding
- Test Suites for using SNOMED with FHIR Servers
- Working with Language Reference Sets
- Working with Languages
- Working with ValueSets
- Mechanisms for working with Languages
- Discussion on Global Patient Set (GPS)
- API for FHIR Resource to SNOMED Expression
- snowstorm FHIR requirements, issues, etc.
- SNOMED CT and CodeSystem Fragments
- Discussion related to changes appearing in R5
Terminology Binding Stream
- ConceptMaps for FHIR code systems to SNOMED CT
- Binding patterns
- Implementation Guidance Principles
- Resource bindings
- Molecular Pathology harmonising V2 and FHIR Datasets
- Developing and publishing ValueSets
- Free SNOMED CT set for FHIR
- COVID-19 Analysis
- Flavours of Null and Degrees of Certainty