Download Full Subset(s) |
|
Some subsets contain content from LOINC® (http://loinc.org). The LOINC table, LOINC codes, LOINC panels and forms file, LOINC linguistic variants file, LOINC/RSNA Radiology Playbook, and LOINC/IEEE Medical Device Code Mapping Table are copyright © 1995-2015, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/terms-of-use.
|
|
Download Terminology Updates |
|
Call Update Web Service directly:The wsdl file for the web service is located at https://vtsl.vetmed.vt.edu/nahln/ws/dataupdate.cfc?wsdl. Web service parameters:
|
|
Why update? Terminology is not a static beast-new species are discovered, new tests are developed, terminologists change their minds. This means that new terms WILL be added to the subsets, and some concepts WILL be retired or removed from the subsets. How can we all possibly keep up? More technology! The terminologists at Virginia Tech have developed a web service in order to synchronize the data between the Terminology Service and the NAHLN data repository servers. The form on this page accesses that web service and returns either an XML format (recommended) or an optional CSV format file. How does this web service work for NAHLN? Each time a concept is requested by a lab or the terminologists retire a concept, the subsets at the Terminology Service are changed. Each day, the central repository (Rhapsody...soon to be EMS) makes a call to the web service which returns all concepts that have been added, and all concepts that have been retired (along with potential replacements for the retired concepts), in XML format. The XML files are processed updating the subsets used to validate messages. So what do YOU do? Accurate data transmission partially relies on accurate mapping of laboratory data to the standards (SNOMED, LOINC, HL7) that are required in the message. Initial mappings are a substantial portion of the process for intitiating messaging. However, maintaining these mappins is equally important. As the terminology changes, existing laboratory mappings may become inaccurate (mapped to now inactive terms). This negatively impacts the quality of the data coming into the central system. As validation efforts become more stringent, these inaccruate mappings can cause failed messages. It is important that labs set up an internal plan for monitoring terminology changes and reviewing their mappings accordingly. It is recommended that each lab determine how frequently that can/should review mappings and then either manually download the updates using the tool above, or set up their own automated procedures to call the webservice. Note about .NET: Issues have been discovered between .NET (and possibly other languages) and the Java based engine the drives our web services. It seems they disagree on how (or how not) to define XML document objects. Long story short, you can't call the web service above using .NET and retrieve an XML document. We have created an alternative web service that returns the XML as a string rather than a document object. It can be accessed at https://vtsl.vetmed.vt.edu/nahln/ws/String/dataupdate.cfc?wsdl. All parameters are the same, only the return type is different. |