Page tree
Skip to end of metadata
Go to start of metadata

Comments invited to discuss which features are important to users and why.

Could we have a URL also please, if there is a publicly facing test server available, or link to source / download?

Capability

Ontoserver

SnoChillies Server ( NZ )


Terminz (NZ exemplar)

Snowstorm

(SNOMED International)

Snow Owl

(Open Source)

STS

(Phast)

Test endpoint

https://stu3.ontoserver.csiro.au/fhir

https://r4.ontoserver.csiro.au/fhir

https://valentiatech.snochillies.com/fhirhttps://terminz.azurewebsites.net/fhir

https://snowstorm-alpha.ihtsdotools.org/fhir/metadata?_format=json

https://dev-snowstorm.ihtsdotools.org/fhir/metadata?_format=json


https://jade.phast.fr/resources-server/api/fhir 
Source Code


https://github.com/IHTSDO/snowstorm

Supported FHIR Version(s)

STU3 +

R4 in beta

STU3R4 (FHIR version 3.3.0)R4STU3R4
Explicit SNOMED CT supportY - supports multiple concurrent Editions and VersionsYYYYY
Implicit SNOMED CT ValueSetsY - Refset and Isa and ECL (R4)Y - Refset and IsaY - Refset and Isa and ECLY - Refset and Isa and ECL (R4)Y (Refset, IsA, ECL)N
Implicit SNOMED CT ConceptMapsY - Historical, Inactivation Indicators, READ CTV3 map, ICD-O map, Australian Substance map, and ARTGID map. Others configurable at deploy timeNNY - Historical, Inactivation Indicators, READ CTV3 map, ICD-O map, ICD-10YN
ValueSets defined using ECLY - all features of v1.3 including cardinality constraintsNY - all features of v1.3 - including cardinality constraints - except concrete valuesY - v1.3Y (All features)Y - all features except operator memberOf and concrete values
Create/Read/Update/Delete of FHIR CodeSystemsYRead onlyRead onlyRead onlyRead only, CUD via dedicated authoring environmentY

Create/Read/Update/Delete of FHIR ValueSets

YRead onlyRead onlyRead onlyRead only, CUD via dedicated authoring environmentY
Create/Read/Update/Delete of FHIR ConceptMapsYRead onlyRead onlyRead onlyRead only, CUD via dedicated authoring environmentY
Able to expand ValueSets defined in terms of arbitrary (known) FHIR CodeSystems using filtersYYYYYY
Support for other well-known code systemsLOINC, CLAML (including ICD 10, OPCS, ICPC 2), OWL (including HPO)LOINC, ICD 10LOINC, NZULM/NZMT, RXNORM (limited)NATC, ICD-10/AM/CM/UK, LOINC, OPCSLOINC
Search of FHIR CodeSystemsYYYNYY
Search of FHIR ValueSetsYYYNYY
Search of FHIR ConceptMapsYYYNYY
SMART on FHIR supportYNNNNN

$lookup

YYYYYY
$expandYYYYYY
$validate-codeYYYNYY
$subsumesYYYNYY
$closureYYYNNY
$find-matchesN - FHIR spec is lacking clear definition of semanticsNpartially for SCT - operation definition incompleteNNN
$translateY - includes several implicit algorithmic mapsY ( Read Code, ICD 10, LOINC, NZPOCYYYY
SNOMED post-coordination supportNNNNNN
Support for close-to-user form post-coordinated expressions?





Support for normal-form post-coordinated expressions?





  • $lookup for SNOMED post-coordinated expressions
N
N


  • $expand for SNOMED post-coordinated expressions
N
N


  • $validate-code for SNOMED post-coordinated expressions
N
N


  • $subsumes for SNOMED post-coordinated expressions
N
N


  • $closure for SNOMED post-coordinated expressions
N
N


  • $compose for SNOMED post-coordinated expressions
N
N


  • $translate for SNOMED post-coordinates expressions


N


Support for the ExpansionProfile resource
(this was removed in R4)

NNNNNN
Support for CodeSystem.supplements (R4)Y - display, designations, and propertiesNY - partialNNN
Support for the NamingSystem resourceY including $preferred-id
Y (including the $preferred-id operation)NNY
Support for the TerminologyCapabilities resource (R4)Y
YNNY

Support for the StructureDefinition resource

Y - SCRUD
N
NN
Support for the Bundle resourceY - SCRUD
Y (e.g. for accepting batches of $validate-code and $translate requests)
NN
Support for other FHIR Resource types

OperationDefinition - Read only

AuditEvent - Create only



Location & Organization (Read-Only support for NZ Health Provider Index Facilities & Organizations).
NDefinitional resources for catalogs of healthcare products and services: ActivityDefinition, CatalogEntry, ObservationDefinition, SpecimenDefinition
$validateY - All resource types
NNNN
$convertXML to/from JSON




Additional to FHIRContent syndication via ATOM


CUD API, Syndication between servers and authoring environment







  • No labels

4 Comments

  1. This is a great summary of capabilities, thank you for putting this together.

    Once this page has been developed to include a reasonable number of vendors. This page could be published on a single "Vendor Capability Comparison" page on snomedinside.org. I think this would be hugely valuable for organisations to understand the differences and capabilities.

    If this page were to be published in a publicly available SNOMED site, I feel that there should be an additional column summarise/explain (with an example) the capability in plain English from the perspective of a user interface and for secondary data use (for audiences who are non-technical)

  2. Abdul Rauf I've added some more detail rows to the table to help gather more information.  As Snochillies is the only server so far to have post coordination support it would be great to get more detail about how it behaves for each of the operations.

  3. Michael Lawley, post coordination is implemented without FHIR formatting.

    For more detail please visit following URL.

    URL: https://snochillies.com

    Thanks

    1. Thanks Abdul Rauf, does that mean that there's no support for post coordination via the FHIR APIs?  The table above is meant to capture what is available via FHIR only.