Terminology Services Track Report Connectathon 16 San Diego, CA September 10, 2017
Terminology Services Track Goals Enhanced formal testing of terminology services Integration of terminology services within other Connectathon tracks
Terminology Services Terminology capability statement Make server defaults explicit “should” be the latest version available? Will arrange breakout session for further discussion “type ahead” terminology search Use sequential filtered implicit value set queries? Add version of the code system used to validate to $validate-code Add $validate-code to CodeSystem resource? Active vs. inactive codes returned in implicit value sets Haven’t specified this yet?
Terminology Services Batch terminology operations i.e. batch translate of all CodeableConcepts with matching ConceptMap entries Updates by server will return new resource versions GF#13813 - Make ValueSet.expansion.identifier cardinality 0..1 GF#13810 – Make code system version explicit in $expansion return GF#13814 – Change ValueSet.compose to ValueSet.definition Minimal requirements for a FHIR terminology server? Need to finish this discussion and decide
Terminology Services GF#13820 – add ValueSet $expand parameters for version and codeSystemVersion Lantana Trifolia: Fixing the output of ValueSet resource so that it properly includes expansion vs. compose Setting up various types of FHIR Servers that can handle ValueSet resources Importing all ValueSet resources from Trifolia into these various FHIR servers Developing $subsumes operation capability for HAPI R4 server
Terminology Services Multiple terminology servers tested and passing to varying degrees Terminz Apelon IMO Any others? Discovered and have begun working through issues with formal testing of VSAC terminology services from US NLM – the value sets aren’t overlapping Can’t test $expand operation because of this “positive failure” identified: $subsumes test fails due to an incorrect data type being returned Discussed need for developing version aware test scripts
Terminology Services Planning for further enhancements to formal terminology service testing in future Connectathons Continue efforts to reach out to other Connectathon tracks for further integration of terminology services within those tracks