Use Case. Enhanced SVS Nikolay Lipskiy, MD, DrPH, Centers for Disease Control (CDC), USA Sundak Ganesan, MD, Northrop Grumman for CDC Proposal discussion February 1-4, 2010. Current SVS: Purpose.
Nikolay Lipskiy, MD, DrPH, Centers for Disease Control (CDC), USA
Sundak Ganesan, MD, Northrop Grumman for CDC
February 1-4, 2010
“This profile describes a mechanism of retrieving a Value Set from a Value Set Repository by a Value Set Consumer. “
“The Sharing Value Sets (SVS) profile provides a means through which healthcare systems producing clinical or administrative data, such as diagnostic imaging equipment, laboratory reporting systems, primary care physician office EMR systems, or national healthcare record systems, can receive a common, uniform nomenclature managed centrally. “
220.127.116.11 Updating terminology codes for a medical and billing across systems
18.104.22.168 Consistent Encoding Terms for anatomical regions in imaging
22.214.171.124 Modification of a protocol code for a mammogram exam
1. Enhanced profile will describe a mechanism of
from a Value Set Repository by a Value Set Consumer
2. Adding Value Set’s Group ID (and OID?) for:
2.1. Immunization Domain
2.2. Cancer registries Domain
2.3. Public Health Case Reporting (PHCR)
Enhanced SVS: Overview of the Process Flow (cont.)
VS Repository (PHIN VADS)
Retrieve VS Version
Query/ Retrieve VS Version or Grouping
Provide & Register /Update VS
VS Source (i.e. Cancer Registry Program)
VS Registry (HL7 OIDs Registry)
Register /Update VS
Issues such as multiple registries, etc. need to be determined, as does the issue of whether the update should come from the VS Repository Actor or the VS Source actor. The diagrams show it coming from the Repository Actor.
Use Case 0. (?-Sondra R. Renly)
The Management of Clinical Document Vocabularies.
Current SVS: Can we extend existing case for this use case?
Use Case 1.
The Management of Immunization Vocabularies.
See proposed profile
Use Case 2.
The Management of Cancer Vocabularies
See proposed profile
New Transactions (Cont.)
2. Retrieving Data from Registry and Repository
Currently a consumer must know the OID of a value set to retrieve it from the Repository. A query will be specified to obtain OIDs of interest.
2.1. Query for a flat file that depicts a relationship between value set groupings
2.2. Query for a list of VS by subject category
2.3. Query for a list of VS associated with specific template/document ID
2.4. Query for a specific VS
2.5. Query for a specific VS group version (i.e., associated with a time stamp)