1 / 11

Ed Cheetham, Principal Terminology Specialist

SNOMED CT IHTSDO Query Language Specification & IHTSDO Public Consultation Relevance to analytics. Ed Cheetham, Principal Terminology Specialist. Scope & purpose.

kalei
Download Presentation

Ed Cheetham, Principal Terminology Specialist

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SNOMED CT IHTSDO Query Language Specification& IHTSDO Public ConsultationRelevance to analytics Ed Cheetham, Principal Terminology Specialist

  2. Scope & purpose • Provide a language specification that should be used to define an expression that selects concepts for inclusion in a simple concept reference set. • No metadata (which release etc.) specified • The specification can be used to define value sets that may be bound to fields in information models, or to define sets of concepts to be included or excluded in particular use-cases.

  3. Look and feel • Functionally • Presented as a set of functions operating on SNOMED CT data, and on the outputs of other functions • Set operations (intersection/union/excludes) • DAG-specific (children, descendants, leaf, roles) • Lexical matching • Syntactically • Human-readable function names • Parentheses denote ‘depth-first’ precedence • Care with non-commutative functions • Simple commenting convention

  4. Examples // This query expression returns concepts in the Clinical finding sub-hierarchy DescendantsAndSelf(404684003|Clinical finding|) /* This query expression returns all fully defined concepts in the Clinical finding * sub-hierarchy */ FilterOnFullyDefined(DescendantsAndSelf(404684003|Clinical finding|))

  5. Union( Descendants(118956008|Body structure altered from its original|), Excludes( Descendants(404684003|Clinical finding|), Union( DescendantsAndSelf(307824009|Administrative statuses|), DescendantsAndSelf(405533003|Adverse incident outcome categories|), DescendantsAndSelf(420134006|Propensity to adverse reactions|), DescendantsAndSelf(365858006|Prognosis/outlook finding|), DescendantsAndSelf(285153007|Sequelae of external causes and disorders|) ) ), Descendants(272379006|Events|), Descendants(413350009|Finding with explicit context|), Descendants(57177007|Family history of|), Descendants(4908009|Past history of|) )

  6. Tabular description

  7. ABNF expression = ws (intersection / filteronfullydefined / filteronprimitive / filteronleaf / filteronactive / all / filteronexcludes / filteroncontains / hasrel / hasdirectrel / hasgroupedrels / childrenandself / children / descendantsandself / descendants / excludes / membersof / union / concept) ws intersection = “Intersection” ws “(“ expression *(“,” expression) “)” filteronfullydefined = “FilterOnFullyDefined” ws “(“ expression “)” filteronprimitive = “FilterOnPrimitive” ws “(“ expression “)” filteronleaf = “FilterOnLeaf” ws “(“ expression “)” filteronactive = “FilterOnActive” ws “(“ expression “)” …

  8. Impact and interactions Relevance to analytics Candidate standard interchange format for SNOMED CT-based analysis predicates Designed to point at reference data, but near identical to parts of tests over record data. • Function-serving • Most likely to be used/expected for use in ‘query’ field of Query Specification Reference Set (TIG 5.5.2.9.) • Competing, complementing, conflicting • Local and National record query set specifications (QOF [G30% etc.]) • Extended SNOMED CT Compositional grammar (<< etc) • Visual notation in IHTSDO WB RefSet designer • Mistaken for • Expression constraint formalism (e.g. LRA) • Post-coordinated expression record query set specification

  9. Development stage Development, Approval, Maintenance and Review of IHTSDO Technical Reports, Guidelines and Standards • 8.8 Public comment on Draft Standard and consensus stage: • 8.8.1 Based on the recommendation of the relevant Committee(s), the Management Board will determine when a Standard is ready for public comment as a potential IHTSDO Standard. At this point, the official status of the document changes to Draft IHTSDO Standard. This status is intended to allow trialing of prospective standards before adoption and this trialing will have been reviewed by the Management Board.

  10. Consultation approach “... The IHTSDO Management Board has approved this specification as an IHTSDO draft standard for public consultation over a period of six months. Please forward all feedback on the specification to John Gutai at jgu@ihtsdo. org by 14th June, using the feedback sheet at: https://csfe.aceworkspace.net/sf/docman/do/listDocuments/projects. announcements/docman.root.ihtsdo_consultations.sct_query_specifications ...”

  11. Review and suitability testing UKTC intend to compare with QOF syntax Other familiar/useful formalisms? Other willing reviewers?

More Related