1 / 8

Terminology Service Bureau Vision

Processes Procedures for adding new content Procedures for maintaining the content Procedures for versioning the content Tools Content import/export tools Terminology load and analysis tools Run-time Environment Reference implementation Web services. People

didina
Download Presentation

Terminology Service Bureau Vision

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. Processes Procedures for adding new content Procedures for maintaining the content Procedures for versioning the content Tools Content import/export tools Terminology load and analysis tools Run-time Environment Reference implementation Web services People Medical professionals who specialize in clinical terminologies Individuals to manage the processes Developers to build the tools Tasks Creation of the MHS Core Ontology Adding terminologies to the core ontology Content Reusable Portable Partitionable Terminology Service Bureau Vision Northrop Grumman Private / Proprietary Level I

  2. TSB Features • Atomic concepts • Reference Terminologies (e.g. SNOMED CT) • Administrative and billing terminologies (e.g. ICD) • Comprehensive concepts • User interface terminologies • Terms • Context for term translation • Simple hierarchies • Complex hierarchies • Unordered sets • Pure cross mapping of terminologies • Pick lists Northrop Grumman Private / Proprietary Level I

  3. TSB Features (Part 2) • Content is not proprietary • Allows business rules to be applied to the mapping process • Portability • Design is generic based on web services – can be moved as needed • Partitionability • Design allows for smaller extracts of content into a run-time environment • Versioning of Standard Terminologies • Concept translation can be done against specific versions or “current” • Complex relationships • Vertical relationships • Horizontal relationships Northrop Grumman Private / Proprietary Level I

  4. Processes, Tools, Run-time Environment TSB Content Management Environment TSB Run-time Environment Client - Applications Terminology Load Services Application Application Application TSB Content Main Database MCO Client API LinkFactory GUI Administration Mid-Tier Server MCO Run-time Web Services TSB Content Export File TSB Content Release Database TSB Content Release Database TSB Content Export Service TSB Content Import Service Northrop Grumman Private / Proprietary Level I

  5. Terminology Service Bureau Purpose • Two key requirements create a need for the TSB • COTS Integration Strategy • Computability/Interoperability across COTS products • If you used only one vendor’s products you would not need a TSB • TSB is a non-proprietary ontology that creates a bridge which enables integration and interoperability among COTS systems Northrop Grumman Private / Proprietary Level I

  6. TSB Current Status • People • Teams are in place and are operational • Tasks • Content development methodology is operational • Content Northrop Grumman Private / Proprietary Level I

  7. TSB Current Status (cont.) • Processes • Procedures are defined and operational • Tools • Content management environment is operational • Import services • Export service • Run-time Environment • AHLTA Build Release 3.4 Northrop Grumman Private / Proprietary Level I

More Related