Uploaded image for project: 'Other Specification Feedback'
  1. Other Specification Feedback
  2. OTHER-2121

Practical Issues of Adoption

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Considered for Future Use
    • Icon: Highest Highest
    • HL7 Logical Model: Standardized Terminology Knowledge Base (OTHER)
    • 1.0
    • Terminology Infrastructure
    • Informative
    • Purpose
      Chapter 2.3.1: Operations
      Chapter 5: Next Steps
    • NA
    • Hide

      This informative ballot document delineates business requirements and needs. This document is not intended to provide implementation guidance.This informative ballot document delineates business requirements and needs. This document is not intended to provide implementation guidance.

      In Chapter 3 “Tinkar Reference Model”, Section 3.7 “Future Iterations”, we added:

      The current Tinkar Reference Model is expressive enough to be able to represent any terminology. Future iterations of the Tinkar specification will require harmonized implementation guides to be created for each terminology. Doing so will ensure that implementers will be able manage terminology produced by a variety of organizations across a healthcare enterprise. Harmonized implementation guides will also support healthcare organizations' standard terminology modules, value sets, and coding systems as well as local terms and equivalence mappings.

      Show
      This informative ballot document delineates business requirements and needs. This document is not intended to provide implementation guidance.This informative ballot document delineates business requirements and needs. This document is not intended to provide implementation guidance. In Chapter 3 “Tinkar Reference Model”, Section 3.7 “Future Iterations”, we added: The current Tinkar Reference Model is expressive enough to be able to represent any terminology. Future iterations of the Tinkar specification will require harmonized implementation guides to be created for each terminology. Doing so will ensure that implementers will be able manage terminology produced by a variety of organizations across a healthcare enterprise. Harmonized implementation guides will also support healthcare organizations' standard terminology modules, value sets, and coding systems as well as local terms and equivalence mappings.
    • Carol Macumber / Keith Campbell : 14 - 0 - 0

      Assuming Tinkar will be adopted by HL7 or the US at large, please explain you view of the pathway from today's world of multiple terminologies to a world where the is a high degree of harmonization under the Tinkar architectue.

      A few things to consider:

      1) The size of the problem - What is the number of concepts and the time required, per concept? If hand curation is required, is this practical?

      2) Intermediate states - what does the world look and function while Tinkar is in the process of being populated? At what point does it become functional and useful (minimal viable product) that vendors can adopt? How does that transition look?

      3) Will this turn into a race between the rate of change of SNOMED, NCI, LOINC, and other existing terminologies and assimilation into Tinkar? What is the prospect for Tinkar keeping up with this rate of change? How much would it cost?

      4) Given the goal of de-duplication between terminology systems, who does that, what is the process, and how long will it take?

            Unassigned Unassigned
            Mark_Kramer Mark Kramer
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: