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 | SnoChillies Server ( NZ ) | Terminz (NZ exemplar) | (SNOMED International) | Snow Owl | STS (PHAST) | |
---|---|---|---|---|---|---|
Test endpoint | https://valentiatech.snochillies.com/fhir | https://terminz.azurewebsites.net/fhir | https://snowstorm-alpha.ihtsdotools.org/fhir/metadata?_format=json https://dev-snowstorm.ihtsdotools.org/fhir/metadata?_format=json | https://topaze.phast.fr/resources-server/api/fhir | ||
Source Code | https://github.com/IHTSDO/snowstorm | |||||
Supported FHIR Version(s) | STU3 + R4 in beta | STU3 | R4 (FHIR version 3.3.0) | R4 | STU3 | R4 |
Explicit SNOMED CT support | Y - supports multiple concurrent Editions and Versions | Y | Y | Y | Y | Y |
Implicit SNOMED CT ValueSets | Y - Refset and Isa and ECL (R4) | Y - Refset and Isa | Y - Refset and Isa and ECL | Y - Refset and Isa and ECL (R4) | Y (Refset, IsA, ECL) | Y (full, IsA, ECL, Refset) |
Implicit SNOMED CT ConceptMaps | Y - Historical, Inactivation Indicators, READ CTV3 map, ICD-O map, Australian Substance map, and ARTGID map. Others configurable at deploy time | N | N | Y - Historical, Inactivation Indicators, READ CTV3 map, ICD-O map, ICD-10 | Y | N |
ValueSets defined using ECL | Y - all features of v1.3 including cardinality constraints | N | Y - all features of v1.3 - including cardinality constraints - except concrete values | Y - v1.3 | Y (All features) | Y - all features of v1.3 except concrete values |
Create/Read/Update/Delete of FHIR CodeSystems | Y | Read only | Read only | Read only | Read only, CUD via dedicated authoring environment | Y: CRUD |
Create/Read/Update/Delete of FHIR ValueSets | Y | Read only | Read only | Read only | Read only, CUD via dedicated authoring environment | Y: CRUD |
Create/Read/Update/Delete of FHIR ConceptMaps | Y | Read only | Read only | Read only | Read only, CUD via dedicated authoring environment | Y |
Able to expand ValueSets defined in terms of arbitrary (known) FHIR CodeSystems using filters | Y | Y | Y | Y | Y | Y |
Support for other well-known code systems | LOINC, CLAML (including ICD 10, OPCS, ICPC 2), OWL (including HPO) | LOINC, ICD 10 | LOINC, NZULM/NZMT, RXNORM (limited) | N | ATC, ICD-10/AM/CM/UK, LOINC, OPCS | LOINC, EDQM Standard terms, ICD-10 (in process) |
Search of FHIR CodeSystems | Y | Y | Y | N | Y | Y |
Search of FHIR ValueSets | Y | Y | Y | N | Y | Y |
Search of FHIR ConceptMaps | Y | Y | Y | N | Y | Y |
SMART on FHIR support | Y | N | N | N | N | N |
$lookup | Y | Y | Y | Y | Y | Y |
$expand | Y | Y | Y | Y | Y | Y |
$validate-code | Y | Y | Y | N | Y | Y |
$subsumes | Y | Y | Y | N | Y | Y |
$closure | Y | Y | Y | N | Y | Y |
$find-matches | N - FHIR spec is lacking clear definition of semantics | N | partially for SCT - operation definition incomplete | N | N | N |
$translate | Y - includes several implicit algorithmic maps | Y ( Read Code, ICD 10, LOINC, NZPOC | Y | Y | Y | Y |
SNOMED post-coordination support | N | N | N | N | N | N |
Support for close-to-user form post-coordinated expressions? | ||||||
Support for normal-form post-coordinated expressions? | ||||||
| N | N | ||||
| N | N | ||||
| N | N | ||||
| N | N | ||||
| N | N | ||||
| N | N | ||||
| N | |||||
Support for the ExpansionProfile resource | N | N | N | N | N | N |
Support for CodeSystem.supplements (R4) | Y - display, designations, and properties | N | Y - partial | N | N | N |
Support for the NamingSystem resource | Y including $preferred-id | Y (including the $preferred-id operation) | N | Y | Y | |
Support for the TerminologyCapabilities resource (R4) | Y | Y | N | Y | Y | |
Support for the StructureDefinition resource | Y - SCRUD | N | N | N | ||
Support for the Bundle resource | Y - SCRUD | Y (e.g. for accepting batches of $validate-code and $translate requests) | N | N | ||
Support for other FHIR Resource types | OperationDefinition - Read only AuditEvent - Create only | Location & Organization (Read-Only support for NZ Health Provider Index Facilities & Organizations). | Definitional resources: PlanDefinition, ActivityDefinition, ObservationDefinition, SpecimenDefinition, Catalog (Composition) | Definitional resources for catalogs of healthcare products and services: ActivityDefinition, CatalogEntry, ObservationDefinition, SpecimenDefinition | ||
$validate | Y - All resource types | N | N | N | N | |
$convert | XML to/from JSON | |||||
Additional to FHIR | Content syndication via ATOM | CUD API, Syndication between servers and authoring environment | ||||