CTS 2 comments OmarBouddou
To: Solbrig, Harold R. Cc: Crandall, Glen (EDS); Lincoln, Mike Sent: 1/18/2005 4:07 PM Harold,
Please find below a few comments from the VHA Enterprise Terminology Services team regarding our preliminary experience with HL7 CTS 1.0 specifications. I hope these will be useful in your considerations for version 2.0.
We appreciate your work,
Omar Bouhaddou Department of Veterans Affairs VHA Enterprise Terminology Services (858) 832-1310 (801) 755-3263 (mobile)
- Concept IDs
HL7 CTS specifications assume that when consumers of terminology services make API calls, they will refer to the concept ID within the terminology source where the concept belongs. Thus, if consumers make a call targeted at SNOMED, then they will use SNOMED IDs, if they make a query to ICD9, they will be returned ICD9 codes, etc. At the VHA, all terminologies in use, whether they are VHA native like allergies or adopted like SNOMED problem list, we assign VHA unique IDs (VUIDs) to all entries. It may be more desirable to be able to refer to IDs as an object made of the concept ID and the terminology source ID to eliminate ambiguities and increase user flexibility.
We understand HL7 CTS 1.0 does not support versioning. We have began implementing our own versioning structures and APIs. We look forward to seeing this topic addressed in version 2.0.
If at the VHA we add local properties to a given code system (e.g., SNOMED-CT). Then, for instance, does the method 'lookupCodeSystemInfo' return all properties including the local extensions added by the VHA? We would think CTS should let the user decide whether they want the local terminology extensions to be returned as well or not.