Guidelines for a Standardized Terminology Knowledge Base
1b. Project ID
1c. Is Your Project an Investigative Project (aka PSS-Lite)?
1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?
1e. Today's Date
1f. Name of standard being reaffirmed
1g. Project Artifact Information
1h. ISO/IEC Standard to Adopt
1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?
1j. Unit of Measure
2a. Primary/Sponsor WG
2d. Project Facilitator
2e. Other Interested Parties (and roles)
2f. Modeling Facilitator
Ioana Singureanu (VA)
2g. Publishing Facilitator
Ioana Singureanu (VA)
2h. Vocabulary Facilitator
2i. Domain Expert Representative
Keith Campbell (VA), Swapna Abhyankar (Regenstrief), Possible others include CDC and FDA
2j. Business Requirements Analyst
Loren Stevenson (VA)
2k. Conformance Facilitator
2l. Other Facilitators
-- UTG (collaboration, exchange format)
-- Department of Veterans Affairs
3a. Project Scope
To describe a flexible self-describing standard logical model for format and distribution of terminology knowledge bases. The logical model will include the ability to represent structures/collections like value sets, refsets, etc.
The resuling logical model is aimed to standardize representation of machine-processable semantics, consistent representation of language and dialect, and change over time.
References and previous standards that will be considered include:
- The Data Management Requirement re: reference data (DMBOK 2019)
- Existing ISO Standards including https://www.iso.org/standard/32881.html, https://www.iso.org/standard/61979.html
- Existing HL7 standards including CTS2, MIF and FHIR
Specifically, the scope includes 1) outlining how the standardized terminology knoweledge base can support FHIR resource generation, perhaps closing gaps that are currently covered as extensions 2) a gap analysis of CTS2 logical model, including an evaluation of why it may be cosnidered a unsuccessful attempt to provide a single logical model, so that those pitfalls may be avoided with this attempt and 3)
3b. Project Need
This project is intended to create a logical model and distribution format to represent represent HL7 Codesets, SNOMED, LOINC, RxNorm, and other clinical terminologies. This model is needed to represent machine-processable semantics for standard terminology and local content/concepts.
3c. Security Risk
3d. External Drivers
3e. Objectives/Deliverables and Target Dates
Jan 2021 Ballot
- White Paper including a Logical Model (use case, information model, operations)
- Example implementation (platform-specific) - e.g., XML Schema
3f. Common Names / Keywords / Aliases:
Master Terminology Knowledge Base, Master Term Dictionary