Resources

Export citation:

Statistics

  • Views: 295
  • Aggregate Downloads: 42

Information

Share


VA Code in Flight Submission - Collaborative Terminology Tooling & Data Management
Revision: 7
Please use this identifier to cite or link to this publication: http://hdl.handle.net/10909/11244
Knowledge Based Systems (KBS) and Standards and Terminology Services (STS) are working to establish a collaborative Enterprise Terminology Service (ETS) that bridges clinical and technical domains in order to address both the Congressional and Executive mandates for interoperability, standardization, computability, and meaningful use. The ETS will consist of two primary components operating in tandem.

First, a robust Clinical Terminology Service (CTS) is necessary to establish and continually improve the VA’s ability to collect and accurately and fully represent healthcare data in the medical record. The CTS will address internal VHA terminology consultation and business ownership needs. These needs have grown tremendously because of the new demands from the Veterans Health Information Systems Technology Architecture (VistA) Evolution, Connected Health, and Compensation and Pension (C&P) and the shift of responsibilities back to VHA from the Interagency Program Office (IPO).

Secondly, a robust Technical Terminology Service (TTS) is necessary to publish standard terminologies and to ensure their complete integration with VA Health Information Technology (HIT) systems and applications. The TTS will address internal Office of Information and Technology (OI&T) technical needs, including terminology publication and distribution, as well as technical consultation for accessing terminology resources, for example, Service Oriented Architecture (SOA) integration.

Collectively, the ETS is foundational to establishing and maintaining robust interoperability with VA partners, such as DoD and VBA, and addressing longstanding Congressional concerns. Specific business objectives that necessitate stating these requirements include:

1. The safety and life-critical nature of the health data VA encodes and processes. Mistakes in the semantic encoding and/or processing of this health data result in morbidity and mortality to the Veterans we serve.
2. Health data must be ubiquitously standardized to deliver the full promises of HIT systems, including the ability to compare the processes, and quality, of care among national and
international health providing organizations. Achieving this ubiquitous standardization requires
participation in collaborative and open-source development efforts. We have a variety of existing relationships, and contemplated relationships, that center around particular open-source projects, such as the International Health Terminology Standards Development Organization (IHTSDO) Open Tooling Framework, and the IHTSDO workbench that is currently utilized by the IHTSDO, Denmark, Sweden, the United States National Library of Medicine, Kaiser Permanente, and some internal VA projects. In cases where contributions to, or extension of, these shared projects is a business requirement, we will specify requirements for specific development languages, libraries, developer operations automation frameworks, and database technologies.
Revision Version
Submitted By
Submission Date
Certified
Notes
7OI&T EPMO Lean Systems Engineering Open Source Coordination Office05-11-2017Adding updated docs
6OI&T EPMO Lean Systems Engineering Open Source Coordination Office03-29-2017Adding updated docs and code
5OI&T EPMO Lean Systems Engineering Open Source Coordination Office03-23-2017Adding updated docs
4OI&T EPMO Lean Systems Engineering Open Source Coordination Office02-17-2017The previous revision submitted was an incomplete code set. This revision makes available the complete code set currently under development and currently "in-flight".
3OI&T EPMO Lean Systems Engineering Open Source Coordination Office01-05-2017This revision makes available the full set of in-flight source code. It was determined by VA that the previous submission did not include all of the source code. This revision remedies that.
2OI&T EPMO Lean Systems Engineering Open Source Coordination Office11-10-2016This revision provides the in-flight source and documentation for version 2 Iteration 2
1OI&T EPMO Lean Systems Engineering Open Source Coordination Office09-27-2016

Reviews (Phase: Peer)

There is no review at this time.
To submit one, please log in.

Comments

COMMENTS

Powered by Midas