Difference between revisions of "Vocabulary Quality Assurance Project"
Line 2: | Line 2: | ||
=Overview= | =Overview= | ||
− | + | ==Scope== | |
+ | Define and communicate consistent set of QA processes for decentralized development of terminology artifacts used across all HL7 product families, coupled with a centralized governance structure. This process would be followed by all HL7 groups, I.E.: all HL7 standards that reference terminology. | ||
+ | |||
+ | ==Need== | ||
+ | It has become apparent that the terminology published in HL7 artifacts does not demonstrate the quality and consistency generally required for interoperability among modern HIT systems. In addition, HL7 internal consistency and harmonization has become increasingly difficult due to a lack of standardized quality processes applied to terminology artifacts. This problem has resulted in excessive effort and resource use across HL7 projects. | ||
=Project Processes= | =Project Processes= |
Revision as of 19:58, 5 March 2015
Project to clarify expected practices and process for WG when using coded vocabulary
Contents
Overview
Scope
Define and communicate consistent set of QA processes for decentralized development of terminology artifacts used across all HL7 product families, coupled with a centralized governance structure. This process would be followed by all HL7 groups, I.E.: all HL7 standards that reference terminology.
Need
It has become apparent that the terminology published in HL7 artifacts does not demonstrate the quality and consistency generally required for interoperability among modern HIT systems. In addition, HL7 internal consistency and harmonization has become increasingly difficult due to a lack of standardized quality processes applied to terminology artifacts. This problem has resulted in excessive effort and resource use across HL7 projects.
Project Processes
This project will use DropBox as a collaborative document sharing process during the formative draft development process. If you are interested in viewing the current draft please attend the meetings. If you are interested in participating in the editing and review of the drafts, please send a request to get access to the dropbox folder to Rob McClure ( rmcclure AT mdpartners.com ).
Project Participants
Preparation Tooling
Conference Call Schedule and Minutes
Calls occur every-other Thursday 1:30 - 3pm ET beginning March 5, 2015 One upcoming call scheduled prior to March 5 on Feb 12 for 30 min
Call Info: Standard Vocabulary phone line: Phone: +1 770-657-9270, Participant Code: 598745
Webmeeting Info: Please click on the link below to join the Mikogo session https://go.mikogo.com/?sp=&sid=503395699
If the above link does not work, you can follow these steps instead to join a session:
- Go to http://go.mikogo.com
- Enter the Session ID: 503-395-699
- Enter your name
- Click "Join Session"
Agenda for next meeting March 19
- Continue work on creating the PSS content
- Plan is to use a Peer Review Process deliverable
Core Documents
Minutes documents
2015-02-05_Minutes 2015-02-12_Minutes 2015-03-05_Minutes