Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

r4.ontoserver.csiro.au/fhir

https://

r4

stu3.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://topaze.phast.fr/resources-server/api/fhir 

Uses basic authentication:

user = Connectathon

pass = Fhir_Connectathon1

Source Code


https://github.com/IHTSDO/snowstormhttps://github.com/b2ihealthcare/snow-owl
Supported FHIR Version(s)

R4 (FHIR version 4.0.1)
STU3 +

R4 in beta

(FHIR version 3.02 + some R4 features)

STU3R4 (FHIR version 3.3.0)R4
STU3
R4R4
Explicit SNOMED CT supportY - supports multiple concurrent Editions and VersionsYYYY - single edition, multi-edition, multi-extension deployments, more info here: https://docs.b2i.sg/snow-owl/index-2Y
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
- Refset and Isa and ECL (R4)Y (full, IsA, ECL, Refset)
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-10Y Historical, Inactivation Indicators, READ CTV3 map, ICD-O map, ICD-10, and any maps created runtimeN
ValueSets defined using ECLY - all features of v1.
3
4 including cardinality constraintsNY - all features of v1.3 - including cardinality constraints - except concrete valuesY - v1.3Y
(All features
- all features of v1.6, including concrete values, cardinality constraints, and custom unofficial filters (https://github.com/b2ihealthcare/snomed-ecl)Y - all features of v1.3 except concrete values
Create/Read/Update/Delete of FHIR CodeSystemsYRead onlyRead onlyRead onlyRead-only, CUD via dedicated REST API and authoring environmentY: CRUD

Create/Read/Update/Delete of FHIR ValueSets

YRead onlyRead onlyRead onlyRead-only, CUD via dedicated REST API and authoring environmentY: CRUD
Create/Read/Update/Delete of FHIR ConceptMapsYRead onlyRead onlyRead onlyRead-only, CUD via dedicated REST API and 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)N
ATC
LOINC, ICD-10/AM/CM/UK/CA,
LOINC
ATC, OPCSLOINC, EDQM Standard terms, ICD-10 (in process)
Search of FHIR CodeSystemsYYYNYY
Search of FHIR ValueSetsYYYNYY
Search of FHIR ConceptMapsYYYNYY
SMART on FHIR supportYNNNNN

$lookup

YYYYYY
$expandYYYYYY
$validate-codeYYYNYY
$subsumesYYYNYY
$closureYYYNYY
$find-matches
N
Y - 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 support
N
YNNNNN
Support for close-to-user form post-coordinated expressions?N


N
Support for normal-form post-coordinated expressions?Y


N
  • $lookup for SNOMED post-coordinated expressions
Y
N
N

N

  • $expand for SNOMED post-coordinated expressions
Y
N
NN
  • $validate-code for SNOMED post-coordinated expressions
Y
N
NN
  • $subsumes for SNOMED post-coordinated expressions
Y
N
NN
  • $closure for SNOMED post-coordinated expressions
Y
N
NN
$compose
  • $find-matches for SNOMED post-coordinated expressions
N
N
NN
  • $translate for SNOMED post-
coordinates expressions
  • coordinated expressions
Y - no special additional support, but PCEs can be included in a ConceptMap and used in $translate as-is
N
NN

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

NNNNNN
Support for CodeSystem.supplements (R4)

Y - display, designations, and properties

can also include post-coordinated expressions

NY - partialN
N
Y - display, designations, propertiesY - display, designations, properties
N
Support for the NamingSystem resourceY including $preferred-id
Y (including the $preferred-id operation)NYY
Support for the TerminologyCapabilities resource (R4)Y
YNYY

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)
N

Y - read-only, CUD via dedicated REST APIN
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 for catalogs of healthcare products and services: ActivityDefinition, PlanDefinition, ObservationDefinition, SpecimenDefinition, Composition, ChargeItemDefinition
$validateY - All resource types
NNNN
$convert

XML to/from JSON

STU3 → R4






Additional to FHIRContent syndication via ATOM


CUD API,
Syndication
syndication between servers
and authoring environment
using official release packages, dedicated authoring environment for content management
Security

OAuth2 including SMART-on-FHIR

Resource-level protection using FHIR security labels




Fully customizable resource access management, filtering and security