Log in Register

HDD Access Release Notes - January 2013

HDD Access Release Notes

January 2013

These are the January 2013 release notes for HDD Access – the public version of the 3M™ Healthcare Data Dictionary (HDD).  This release includes both additional software functionality and terminology content.  These release notes cover the following topics:

What’s changed in January 2013?

·         Support for local extensions

·         Capability to update content incrementally

·         Content version 6

·         Updating content

·         Installer version 1.3

o   Database version 2.0

o   Browser version 2.0

o   Application Programming Interface(API) version 1.1

·         Supported technologies

·         System requirements

o   Operating system, hardware, software, network resources, Internet access

·         Installation and Upgrade

·         Compatibility with earlier releases

·         Known issues

·         Documentation

·         Support

·         Content integrity

·         Licenses

 

 

 

Local Extensions

Conceptually, the HDD Access database can be partitioned logically into “individual namespaces” such as the “HDD Access global namespace” (containing HDD Access content obtained from 3M) and the “local namespace” (containing the “local extension” – the content created by the user).  Local extensions exist only in the user’s local copy of HDD Access and are not visible to 3M.  The local extension can be identified by the “ENTERPRISE_NCID” columns in the four main HDD tables (concept, concept_relation, rsform and rsform_context).  The global content would have ENTERPRISE_NCID of 1 (3M) for every data row, whereas the local extension would have the ENTERPRISE_NCID of the HDD Access customer for every data row created by the customer.

 

The January 2013 release (installer version 1.3) allows the HDD Access customer to prepare for a local extension by requesting its setup in the local copy of HDD Access, and to start authoring local content.  Both of these capabilities are provided through the online browser interface, and the customer can access these capabilities after logging in.  When the customer requests a local extension to be started, the locally installed HDD Access application will contact the namespace management system (named “Epsilon”) hosted on the HDD Access website, receive an exclusive range of unique identifiers for the local extension and save them to the local HDD Access database.  After this is done, the customer can add or edit the terminology content in the local extension through the same online browser interface.  Local extensions are described in the HDD Access documentation library under a separate section.

 

Currently, we set up a default user for each HDD Access customer and support a single local extension per HDD Access installation.  The default user would be using the same username and password used to log into the HDD Access website to request for a local extension.  In addition, we have also created local administration authentication for the default user before certain actions affecting the database content can be carried out, including updating the content, requesting a local extension and creating, editing or deleting local content.  The local administration authentication username and password are different from that used for the HDD Access website.   See the section on Browser version 2.0 for more information.

 

 

Capability to update HDD Access content incrementally

From the August 2012 to the December 2012 releases (installer versions 1.1 and 1.2), HDD Access installations required a complete replacement of the database content, which would overwrite any local extensions.  Therefore, to support local extensions, the January 2013 release (installer version 1.3) also includes the capability to update to newer content versions without overwriting, uninstalling, deleting or otherwise replacing the local database content.  Installer version 1.3 is packaged with the current content version 6, and would still be a complete replacement of previous content versions; but starting with the next content update (version 7), to be released in February 2013, the update process will apply changes to the global content provided by 3M without overwriting the local content created by the HDD Access customer. 

 

Also, a set of history tables have been added to the database schema in the January 2013 release to provide an audit trail of the content changes made to the local copy of HDD Access, to better support local extensions.  See the section on Database version 2.0 for more information.

 

 

Content Version 6

HDD Access terminology content Version 6 contains 224,761 unique concepts.  This release reviewed and added to previously released domains.  The list of domains is viewable in the left sidebar (“Search Domains”) of the HDD Access browser.  Clicking the triangle to the left of each domain will open sub-domains. 

 

Standard terminologies included are:

·         ICD-9-CM Diagnoses (codes and hierarchies)

·         ICD-9-CM Procedures (codes and hierarchies)

·         ICD-10-CM (codes and hierarchies)

·         ICD-10-PCS (codes but not attributes/hierarchies)

·         HCPCS Level II

·         HCPCS Modifiers

·         MS-DRG

·         TRICARE/CHAMPUS MS-DRG

·         APC

·         MS-DRG MDC

·         TRICARE/CHAMPUS MS-DRG MDC

HDD Access content will be incremented monthly in subsequent releases.

 

HDD Access Table

Row Count December 2012

(Content v5)

Row Count January 2013

(Content v6)

CONCEPT

223,652

224,761

CONCEPT_RELATION

458,875

461,290

RSFORM

1,147,210

1,150,511

RSFORM_CONTEXT

1,729,608

1,733,028

 

 

Updating Content

 

For the January 2013 release (installer version 1.3):  The January 2013 release is a complete replacement of our previous software and content versions.  The database schema has changed in this release.  HDD customers who have installed previous versions of software are strongly encouraged to uninstall (or delete/overwrite) past versions before installing the January 2013 release, which is packaged with the latest content (version 6).  There is thus no need to separately update content when installing the January 2013; this will only need to be done for subsequent content releases such as version 7 in February 2013.  New users who have not installed HDD Access previously should install the current release.  This will install both the most current software as well as version 6 of the content.

 

Unlike in the previous installations, it will not be necessary to rebuild the search index for the HDD Access browser (using the “Create Search Index” function) after the content has been updated; that function has been automated in the content update process.  However, we have kept the “Create Search Index” menu item in case users want to manually recreate the search index at any point in time (e.g. during debugging). In the event of a full manual database load, the user will need to update the search index separately.

 

For customers on the September 2012 release (installer version 1.2):  HDD Access customers who installed version 1.2 of the installer can choose to stay on the older software version and only update the content to version 6 by clicking the menu option “Update Content”.  The functionality to create local extension (local terminology content) will not be available in this case. The update utility can also be used by visiting the URL http://host:port/update, where the ‘host’ is the hostname or IP address (often ‘localhost’), and ‘port’ is the port number (often ‘8080’) where the HDD Access web application is installed.  The following will be displayed (your hostname and port may be different):

 

 

Clicking on the “here” link will bring the user to the HDD Access content and documentation download page.   Select “HDD Access terminology content v6 (XML files)” and save the file in your system, then return to the HDD Content Update dialog window to browse for the file and click “Update” to complete the process.  Note that you should rebuild the search index for the HDD Access browser, using the “Create Search Index” function, after you have updated the content.

 

Note that staying on older versions of HDD Access software means you will not be able to keep a local extension (local content data rows) in your copy of HDD Access, as all subsequent updates to the terminology content, being a complete replacement, will overwrite any local content created in your copy of HDD Access.

 

For customers on the August 2012 release (installer version 1.1):  This was replaced by the September 2012 release and should not be used if you intend to update the terminology content to keep current with the content provided by 3M.  HDD Access customers who are still on installer version 1.1 are strongly encouraged to move to the January 2013 release (installer version 1.3) and bypass version 1.2.

 

Installer Version 1.3

The HDD Access installer v1.3 gives users access to terminology content version 6, database version 2.0, browser version 2.0 and Application Programming Interface (API) version 1.1, for both Linux and Windows. 

 

In Windows, after installing HDD Access, the user can see the following menu items in the Windows Start Menu → All Programs→ HDD Access:

·         Create Search Index

·         HDD Access Browser

·         HDD Access Uninstaller

·         Shutdown HDD Access

·         Start HDD Access

·         Update Content

 

In Linux CentOS, while the server is running, users who have installed the current release can see the following menu items in the Application Menu → Other:

·         Browse

·         Create Search Index

·         Load Content

·         Shutdown Server

·         Start Server

·         Update Content

 

Database Version 2.0

HDD Access users will have the option of installing HDD Access to operate under any of the following database management systems (DBMS).  Each DBMS is listed with the version with which it was tested.  Previous or later versions may also work but have not been tested.

·         Oracle 11g

·         MySQL 5.1

·         H2 1.3

A denormalized table named PREFERREDNAME to hold the preferred 3M Display Name (Context_NCID 45821, Preferred_Score 0) of active concepts (Status_NCID 1024) has been added in the September 2012 release to improve performance of the HDD Access browser and the HDD Access Web Services API.

 

For the January 2013 release, tables have been added to support local extensions and to maintain an audit history of the four main tables. These new tables are:

·         user_ha

·         range_ha

·         namespace_ha

·         concept_history_ha

·         concept_relation_history_ha

·         rsform_history_ha

·         rsform_context_history_ha

When the user applies HDD Access updates or authors terminology content in their local installation, the changes are logged to the history tables. The history tables reflect the structure of the four main HDD Access tables (concept, concept_relation, rsform and rsform_context) with additional columns to track the changes:

·         ID – primary key of the history table

·         Creation_User_NCID – who did it (the “default user” is created as a concept and assigned and NCID in the HDD Access customer’s local extension)

·         Creation_Date – when was it done (in UTC timezone)

·         Action – what was done

 

Browser Version v2.0

 

The January 2013 software release now includes basic authentication to protect the database content.  Read-only access using the browser does not require authentication.  However, a username and password are required to perform the following actions:

·         Updating terminology content

·         Requesting a local extension

·         Adding, editing and deleting local content

 

The default username is "admin" and the default password is "admin".  It is recommended that the user change the password for security purposes.  To change the password, delete the password field from the user_ha table in the database.  To set a new password, the user may click on the "Login" link at the top right corner, or go directly to http://<server_address>/ensureLogin.  Enter the username and the new password.  The password entered will be saved to the database.

 

After logging in, the HDD Access customer can use the browser installed by the January 2013 release (installer version 1.3) to request for a local extension to be set up in the local installed copy of HDD Access.  A range of identifiers will be assigned for the customer to start creating local content.  For each request, a range of 100,000 identifiers (for each core table) will be assigned.  When these are consumed (the browser will provide an error message letting the customer know it is time to request a new range), the customer can request another range (Note: only one request can be made each day).

 

 The following browser functionalities are unchanged from the previous release:

·         Search by text string – this uses HyperSearch, a heuristic search engine developed by 3M, which searches for synonyms, abbreviations, abbreviation expansions, inflectional variants, spelling variations and word order variations of the input string.

·         Constrain text search by domain

·         Search by NCID (Numeric Concept IDentifier)

The HDD Access browser has been tested with Mozilla Firefox 14, 15, 16, 17 and 18, Google Chrome 21, 22, 23 and 24 and Internet Explorer 9.  Javascript is required by the HDD Access browser.

 

Application Programming Interface (API) Version 1.1

The HDD Access Web Services API version 1.1, released in September 2012, is designed to make it easier to interface the HDD Access terminology service with other client applications. The API supports the following functions:

 

·         HL7 CTS v1.2 Web Services API

HL7 CTS is a standard that specifies functions supported by terminology services.  The current version of the HDD Access Web Services API supports a subset of HL7 CTS v1.2 functions, as described in the help documentation.

·         3M Web Services API

3M Web Services API is designed to complement the functionality provided by the HL7 CTS Web Services API.  The 3M services are designed to support functionality specific to HDD Access and to improve performance.  They are described in the help documentation.

 

For January 2013, the API remains at version 1.1 with no changes.

 

Supported Technologies

The HDD Access database supports the following technologies and has been tested with the following application servers:

·         Apache Tomcat 7.0.27 (or later).

 

System Requirements

 

Operating System

The current version of HDD Access installer installs the HDD Access software to run on any of the following operating systems:

·         Microsoft  Windows 7 32-bit

·         Microsoft Windows Server 2008 R2 64-bit

·         CentOS Linux 6.3 32-bit or 64-bit

The software may also work on the following operating systems, but was not tested extensively: Microsoft Windows Server 2012 64-bit, Windows XP 32-bit, Windows 7 64-bit and other Linux distributions.

Advanced users may deploy the WAR file distribution of HDD Access software on Apache Tomcat on Microsoft Windows, Linux or other operating systems. 

 

Hardware

Minimum hardware requirements for HDD Access are:

·         Processor: 2 GHz

·         Memory (RAM): 3 GB

·         Disk space: 6 GB of free disk space

 

Software

HDD Access requires the software listed below:

·         Oracle Java (JDK or JRE) 1.7 (or later)

·         Database:

o   Oracle  11g (or later)

o   MySQL 5.1 (or later)

o   H2 version 1.3 (or later) – this will be installed for you if you choose “simple installation”

·         Java application server:

o   Apache Tomcat 7.0.27 (or later) – this will be installed for you if you choose “simple installation”

 

Network resources

‘Simple installation’ in the installer configures the installed Apache Tomcat server software to use network ports 8480 and 8485 by default.  These ports can be changed by the user during installation through the installer program, or after installation manually in the configuration file.

 

Internet access

The HDD Access software needs Internet access to request local extension namespaces from HDDAccess.com.  If Internet access is not available to the HDD Access web application, then local extension and local content authoring capabilities will not be available to your HDD Access installation.

 

Installation and upgrade

 

Installation

HDD Access is released as a graphical installer for Windows and Linux, a command-line installer for Linux, and a binary (WAR file) distribution that can be installed on Windows or Linux.  For the current release, the HDD Access content version 6 is included in all these distributions, and also as separate CSV (comma-separated values) files and zipped XML format – the latter, HDD Access terminology content v6 (XML files)”, can be used to update the content of the installed HDD Access database if the HDD Access customer chooses to remain on the previous version (installer version 1.2 released September 2012).

 

The graphical and the command line installers provide step-by-step installation instructions.

Installation instructions for the binary (WAR file) distribution are provided in the INSTALL.txt file within the archive file, and are also included in the HDD Access documentation library.

 

The CSV files are provided so that the users may open and use the terminology content with any application that can open these files (text editors, Microsoft Excel or Access, statistical analysis software, etc.).  Please read the HDD Access Documentation Library to understand the four core terminology tables and how to use them.

 

Upgrade

To upgrade to the January 2013 release (installer version 1.3), HDD Access customers are encouraged to do a complete installation of both the new software and the new content.  See the “Updating Content” section “for the January 2013 release (installer version 1.3).”

 

However, if a user chooses only to update content to an installation of the September 2012 release (installer version 1.2), please follow the  instructions in the “Updating Content” section “for customers on the September 2012 release (installer version 1.2)”  to bring the content up to version 6.  Note that if MySQL or Oracle was used for installation, the database will not be overwritten by the installer.  The user must manually remove the old database tables before installing the current version, or provide a new database or schema location during the installation.  Please note that all the local content modifications will be lost the previous installation is replaced with the current version.

 

Users on the August 2012 release (installer version 1.1) should uninstall the August 2012 release and install the current release (installer version 1.3).  See the “Updating Content” section “for customers on the August 2012 release (installer version 1.1).”

 

 

Compatibility with Earlier Releases          

The current release of the software depends on terminology content which is version 6.  Installing the current content will involve removing existing content first and then loading.  Any local content modifications in a previously installed version will be lost.

 

Known Issues

 

1.    If you choose ‘simple install’ and network ports 8480 and 8485 are not available, the Apache Tomcat server will fail to start.  You may make these ports available or manually change the port numbers used by Apache Tomcat to overcome this issue. This can be done when you run the installer, or after the installation. If the port numbers are modified, you will need to modify the tomcatPort variable in the following “.bat” files in Windows or “.sh” files in Linux:  hddBrowser, hddLoad, hddCreateIndex, and hddUpdate in the [HDDAccess]\hddServer\bin directory to add the new port to the URL and then manually start Tomcat.  Open a web browser and visit http://domain:port/load (the default is http://localhost:8080/load) to load the terminology content into your database.

 

2.    Text search in the HDD Access Browser uses HyperSearch. The time it takes for HyperSearch searches increases exponentially with the number of words (tokens) in the input string. This is a known limitation of HyperSearch.

 

3.    If you have installed the software on Linux and attempt to start Tomcat from one of the shortcuts (sym links), the page may remain blank with no action occurring. This is in order to allow you to place the hddFiles directory in a location other than the Tomcat bin directory. In order to avoid this problem, you must either start the Tomcat server only from the bin directory (not using the shortcut), or setup the environment variable i.e. export HDD_FILE_DIR="<install_directory>/HDDAccess/hddServer/bin/hddFiles/" (where install_directory is the absolute path to the installation directory).

 

4.    For Installer version 1.2 (September 2012 release) only:  The build instructions and some configuration files required for running the software after building were missing and were fixed and released as v1.2a with filename ‘HDDAcess_sources_1_2a.zip’.  No other changes (new features or modifications) have been made to the source code.  If you want to build from source, please download this new package and build it following the included instructions.  Installation instructions are also included to help you run the software that you build.

 

5.    If a concept is superseded, then the user attempts to "unsupersede" it by editing the concept and setting the status to active and deleting the superseded NCID field during the same edit session, the server is put into a state where the browser is broken.  The user can no longer view the details of a concept.  Restarting the server resolves the condition, but the superseded concept will be in an inconsistent state - active and superseded.  This can be fixed by editing the concept and setting the status to inactive.

 

 

Documentation

Documentation for HDD Access software and terminology content is available at http://www.hddaccess.com.

 

Support

HDD Access terminology content and software are published as-is without warranties or support.  Community support may be available through the HDD Access discussion forums at http://www.hddaccess.com

 

Content Integrity

All the downloadable packages (installer, binary, source, content files and documentation) have their MD5 checksum published on the HDD Access website. Users may verify the integrity of the downloaded files by calculating their MD5 checksums using a checksum application and comparing them with the checksums published on the website.

 

Users may validate the number of rows that were loaded into the four core tables in their database by comparing them against the row counts published at the beginning of this document.

 

Users may also use the web-based HDD Access online browser at http://search.hddaccess.com/ to manually browse and search against the read-only master version. The HDD Access Browser provides read-only access to HDD Access content, and can be used for comparing content in your local database against the master version.

 

Licenses

HDD Access software is open source under the Apache License, version 2.0.  Source code is available from http://www.hddaccess.com.

HDD Access terminology content is published under the HDD Content Download License (viewable at http://www.hddaccess.com/content_license/).  You will need to accept the license during the download process for the HDD Access installer to create the database and load the terminology content on your system.

Third-party software files included in the HDD Access software are released under their respective licenses by their authors.  They are listed below.  You can also view the list of third-party software files and their respective licenses during the installation process. 

The JAR files listed below are included in the [Web_application_root]/WEB-INF/lib directory in the binary builds. They may be located in other appropriate directories in the source distribution. Other files may be in other relevant directories.

 

1.      Public Domain

Third Party File

Copyright Notice

antlr-2.7.6.jar

http://www.antlr2.org/license.html

aopalliance-1.0.jar

http://aopalliance.sourceforge.net/

 

2.      Apache 2.0

http://www.apache.org/licenses/LICENSE-2.0.txt

 

Third Party File

Copyright Notice

cglib-nodep-2.2.2.jar

ASM: a very small and fast Java bytecode manipulation framework

Copyright (c) 2000,2002,2003 INRIA, France Telecom

All rights reserved.

gson-1.7.1.jar

http://code.google.com/p/google-gson/

commons-beanutils-1.8.3.jar

Apache Commons BeanUtils

Copyright 2000-2010 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

commons-codec-1.5.jar

Apache Commons Codec

Copyright 2002-2011 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

 

src/test/org/apache/commons/codec/language/DoubleMetaphoneTest.java contains test data from http://aspell.sourceforge.net/test/batch0.tab.

Copyright (C) 2002 Kevin Atkinson (This email address is being protected from spambots. You need JavaScript enabled to view it.). Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

commons-collections-3.2.1.jar

Apache Commons Collections

Copyright 2001-2008 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

commons-dbcp-1.3.jar

Apache Commons DBCP

Copyright 2001-2010 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

commons-digester-2.1.jar

Apache Commons Digester

Copyright 2001-2010 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

commons-fileupload-1.2.2.jar

Apache Commons FileUpload

Copyright 2002-2010 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

commons-io-2.1.jar

Apache Commons IO

Copyright 2002-2011 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

commons-lang-2.4.jar

Apache Commons Lang

Copyright 2001-2008 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

commons-pool-1.5.6.jar

Apache Commons Pool

Copyright 2001-2011 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

joda-time-1.6.jar

NOTICE file corresponding to section 4d of the Apache License Version 2.0

This product includes software developed by Joda.org (http://www.joda.org/).

log4j-1.2.16.jar

Apache log4j

Copyright 2007 The Apache Software Foundation

This product includes software developed at

The Apache Software Foundation (http://www.apache.org/).

flexjson-2.1.jar

http://flexjson.sourceforge.net/

commons-lang3-3.1.jar

Apache Commons Lang

Copyright 2001-2011 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

This product includes software from the Spring Framework,

under the Apache License 2.0 (see: StringUtils.containsWhitespace())

Apache Lucene

Copyright © 2011-2012 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.

http://lucene.apache.org/core/

lucene-core-3.6.0.jar

Apache Lucene

Copyright 2012 The Apache Software Foundation

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

tiles-template-2.2.2.jar

Tiles - Template Technologies Support

Copyright 2001-2010 Apache Software Foundation

This product includes software developed at

The Apache Software Foundation (http://www.apache.org/).

Third Party Files:

tiles-api-2.2.2.jar

tiles-core-2.2.2.jar

tiles-jsp-2.2.2.jar

tiles-servlet-2.2.2.jar

 

Apache Tiles

Copyright 1999-2010 The Apache Software Foundation

This product includes software developed at

The Apache Software Foundation (http://www.apache.org/).

Third Party Files:

org.springframework.roo.annotations-1.2.1.RELEASE.jar

spring-aop-3.0.0.RC3.jar

spring-asm-3.1.0.RELEASE.jar

spring-context-3.1.0.RELEASE.jar

spring-context-support-3.1.0.RELEASE.jar

spring-js-resources-2.2.1.RELEASE.jar

 

http://www.springsource.com/

© Copyright 2012 SpringSource, a division of VMware.  All Rights Reserved.

Third Party Files:

spring-aspects-3.1.0.RELEASE.jar

spring-beans-3.1.0.RELEASE.jar

spring-core-3.1.0.RELEASE.jar

spring-expression-3.1.0.RELEASE.jar

spring-jdbc-3.1.0.RELEASE.jar

spring-orm-3.1.0.RELEASE.jar

spring-tx-3.1.0.RELEASE.jar

spring-web-3.1.0.RELEASE.jar

spring-webmvc-3.1.0.RELEASE.jar

 

Spring Framework 3.1

Copyright (c) 2002-2011 SpringSource, a division of VMware, Inc.

This product is licensed to you under the Apache License, Version 2.0 (the "License").  You may not use this product except in compliance with the License.

This product may include a number of subcomponents with separate copyright notices and license terms. Your use of the source code for these subcomponents is subject to the terms and conditions of the subcomponent's license, as noted in the LICENSE file.

3.      Berkeley Software Distribution (BSD) 2-Clause

http://opensource.org/licenses/bsd-license.php

Third Party File:

hamcrest-core-1.1.jar


http://code.google.com/p/hamcrest/source/browse/trunk/hamcrest-java/LICENSE.txt
Copyright (c) 2000-2006, www.hamcrest.org
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Hamcrest nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 

4.      Berkeley Software Distribution (BSD) 3-Clause

http://opensource.org/licenses/BSD-3-Clause

Third Party Files:

asm-3.3.1.jar

asm-commons-3.3.1.jar

asm-tree-3.3.1.jar

 

http://asm.ow2.org/license.html

Copyright (c) 2000-2011 INRIA, France Telecom

All rights reserved.

 

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

 

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 
 
 

Third Party Files:

jquery.dataTables.min-1.9.1.js

jquery.dataTables-1.8.2.js

jquery.dataTables-1.9.1.js

http://datatables.net/license_bsd

Copyright (c) 2008-2012, Allan Jardine
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

·         Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

·         Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

·         Neither the name of Allan Jardine nor SpryMedia may be used to endorse or promote products derived from this software without specific prior written permission.

 

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 

 

5.      Berkeley Software Distribution (BSD) Variant

Third Party File:

dom4j-1.6.1.jar

 

http://dom4j.sourceforge.net/dom4j-1.6.1/license.html

Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:

1.       Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of this document.

2.       Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3.       The name "DOM4J" must not be used to endorse or promote products derived from this Software without prior written permission of MetaStuff, Ltd. For written permission, please contact This email address is being protected from spambots. You need JavaScript enabled to view it..

4.       Products derived from this Software may not be called "DOM4J" nor may "DOM4J" appear in their names without prior written permission of MetaStuff, Ltd. DOM4J is a registered trademark of MetaStuff, Ltd.

5.       Due credit should be given to the DOM4J Project - http://dom4j.sourceforge.net

THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved.

 

6.      Common Development and Distribution License (CDDL) 1.0

http://opensource.org/comment/983

Third Party File:

jstl-impl-1.2.jar

 

http://glassfish.java.net/public/CDDL+GPL.html

HDD Access elects to include this software in this distribution under the CDDL license

 

http://repo1.maven.org/maven2/org/glassfish/web/jstl-impl/1.2/jstl-impl-1.2.pom

Copyright (c) 1997-2011 Oracle and/or its affiliates. All rights reserved.

 

The contents of this file are subject to the terms of either the GNU General Public License Version 2 only ("GPL") or the Common Development and Distribution License("CDDL") (collectively, the "License").  You may not use this file except in compliance with the License.  You can obtain a copy of the License at https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html or packager/legal/LICENSE.txt.  See the License for the specific language governing permissions and limitations under the License.

 

When distributing the software, include this License Header Notice in each file and include the License file at packager/legal/LICENSE.txt.

 

GPL Classpath Exception:

Oracle designates this particular file as subject to the "Classpath" exception as provided by Oracle in the GPL Version 2 section of the License file that accompanied this code.

 

Modifications:

If applicable, add the following below the License Header, with the fields enclosed by brackets [] replaced by your own identifying information:

"Portions Copyright [year] [name of copyright owner]"

 

Contributor(s):

If you wish your version of this file to be governed by only the CDDL or only the GPL Version 2, indicate your decision by adding "[Contributor]elects to include this software in this distribution under the [CDDL or GPL Version 2] license."  If you don't indicate a single choice of license, a recipient has the option to distribute your version of this file under either the CDDL, the GPL Version 2 or to extend the choice of license to its licensees as provided above.  However, if you add GPL Version 2 code and therefore, elected the GPL Version 2 license, then the option applies only if the new code is made subject to such option by the copyright holder.

 

7.      Common Development and Distribution License (CDDL) 1.1

http://glassfish.java.net/public/CDDL+GPL_1_1.html

 

Third Party Files:

jersey-spring-1.12.jar

jersey-core-1.12.jar

jersey-server-1.12.jar

jersey-servlet-1.12.jar

 

http://glassfish.java.net/public/CDDL+GPL_1_1.html

HDD Access elects to include this software in this distribution under the CDDL license

 

http://repo1.maven.org/maven2/com/sun/jersey/contribs/jersey-spring/1.12-b01/jersey-spring-1.12-b01.pom

http://repo1.maven.org/maven2/com/sun/jersey/jersey-core/1.12/jersey-core-1.12.pom

http://repo1.maven.org/maven2/com/sun/jersey/jersey-server/1.12/jersey-server-1.12.pom

http://repo1.maven.org/maven2/com/sun/jersey/jersey-servlet/1.12/jersey-servlet-1.12.pom

Copyright (c) 1997-2011 Oracle and/or its affiliates. All rights reserved.

 

The contents of this file are subject to the terms of either the GNU General Public License Version 2 only ("GPL") or the Common Development and Distribution License("CDDL") (collectively, the "License").  You may not use this file except in compliance with the License.  You can obtain a copy of the License at https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html or packager/legal/LICENSE.txt.  See the License for the specific language governing permissions and limitations under the License.

 

When distributing the software, include this License Header Notice in each file and include the License file at packager/legal/LICENSE.txt.

 

GPL Classpath Exception:

Oracle designates this particular file as subject to the "Classpath" exception as provided by Oracle in the GPL Version 2 section of the License file that accompanied this code.

 

Modifications:

If applicable, add the following below the License Header, with the fields enclosed by brackets [] replaced by your own identifying information:

"Portions Copyright [year] [name of copyright owner]"

 

Contributor(s):

If you wish your version of this file to be governed by only the CDDL or only the GPL Version 2, indicate your decision by adding "[Contributor]elects to include this software in this distribution under the [CDDL or GPL Version 2] license."  If you don't indicate a single choice of license, a recipient has the option to distribute your version of this file under either the CDDL, the GPL Version 2 or to extend the choice of license to its licensees as provided above.  However, if you add GPL Version 2 code and therefore, elected the GPL Version 2 license, then the option applies only if the new code is made subject to such option by the copyright holder.

8.      Eclipse Public License (EPL) 1.0

http://opensource.org/licenses/eclipse-1.0.php

Third Party Files:

aspectjrt-1.6.12.jar

aspectjweaver-1.6.12.jar

 

The Eclipse Foundation makes available all content in this distribution ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at http://www.eclipse.org/legal/epl-v10.html. For purposes of the EPL, "Program" will mean the Content.

 

If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise indicated below, the terms and conditions of the EPL still apply to any source code in the Content and such source code may be obtained at http://www.eclipse.org.

Third Party File:

h2-1.3.168.jar

http://www.h2database.com/html/license.html

HDD Access elects to include this software in this distribution under the EPL license

 

H2 is dual licensed and available under a modified version of the MPL 1.1 (Mozilla Public License) or under the (unmodified) EPL 1.0 (Eclipse Public License). The changes to the MPL are underlined. There is a license FAQ for both the MPL and the EPL, most of that is applicable to the H2 license as well.

·         You can use H2 for free. You can integrate it into your applications (including in commercial applications), and you can distribute it.

·         Files containing only your code are not covered by this license (it is 'commercial friendly').

·         Modifications to the H2 source code must be published.

·         You don't need to provide the source code of H2 if you did not modify anything.

·         If you distribute a binary that includes H2, you need to add a disclaimer of liability - see the example below.

However, nobody is allowed to rename H2, modify it a little, and sell it as a database engine without telling the customers it is in fact H2. This happened to HSQLDB: a company called 'bungisoft' copied HSQLDB, renamed it to 'RedBase', and tried to sell it, hiding the fact that it was in fact just HSQLDB. It seems 'bungisoft' does not exist any more, but you can use the Wayback Machine and visit old web pages of http://www.bungisoft.com.

About porting the source code to another language (for example C# or C++): converted source code (even if done manually) stays under the same copyright and license as the original code. The copyright of the ported source code does not (automatically) go to the person who ported the code.

If you distribute a binary that includes H2, you need to add the license and a disclaimer of liability (as you should do for your own code). You should add a disclaimer for each open source libraries you use. For example, add a file 3rdparty_license.txt in the directory where the jar files are, and list all open source libraries, each one with its license and disclaimer. For H2, a simple solution is to copy the following text below. You may also include a copy of the complete license.

This software contains unmodified binary redistributions for H2 database engine (http://www.h2database.com/),
which is dual licensed and available under a modified version of the MPL 1.1 (Mozilla Public License)
or under the (unmodified) EPL 1.0 (Eclipse Public License).
An original copy of the license agreement can be found at: http://www.h2database.com/html/license.html

 

9.      GNU Lesser General Public License (LGPL) 2.1

http://www.gnu.org/licenses/lgpl-2.1.html

Third Party Files:

jackson-core-lgpl-1.9.0.jar

jackson-mapper-lgpl-1.9.0.jar

 

This product currently only contains code developed by authors of specific components, as identified by the source code files; if such notes are missing files have been created by Tatu Saloranta.

 

For additional credits (generally to people who reported problems) see CREDITS file.

Third Party Files:

 Hibernate

hibernate-core-4.1.5SP1.jar

hibernate-entitymanager-4.1.5SP1.jar

hibernate-validator-4.3.0.Final.jar

hibernate-commons-annotations-3.2.0.Final.jar

hibernate-jpa-2.0-api-1.0.1.Final.jar

jboss-logging-3.1.0.GA.jar

jboss-transaction-api_1.1_spec-1.0.0.Final.jar

 

http://www.hibernate.org/license

Free, as in Speech

Hibernate is Free Software.

Hibernate is licensed under the LGPL v2.1. The LGPL is sufficiently flexible to allow the use of Hibernate in both open source and commercial projects. The LGPL guarantees that Hibernate and any modifications made to Hibernate will stay open source, protecting our and your work. Anyone who wanted to release Hibernate under a different license would have to obtain permission from hundreds of people who have contributed code to Hibernate, which would be impractical. Hibernate is and will be open source distributed under the LGPL.

The use of the unmodified Hibernate binary of course never affects the license of your application or distribution. You will never have to pay money to any commercial entity for using or integrating Hibernate.

If you modify Hibernate and redistribute your modifications, the LGPL applies. Please submit any modifications to our issue tracking system for review and possible inclusion in the upstream Hibernate project(s).

 

10.  Massachusetts Institute of Technology

http://opensource.org/licenses/mit-license.php/

Third Party File

Copyright Notice

jquery.cookie.js

HDD Access elects to include this software in this distribution under the MIT license

 

 Copyright (c) 2006 Klaus Hartl (stilbuero.de)

 Dual licensed under the MIT and GPL licenses:

 http://www.opensource.org/licenses/mit-license.php

 http://www.gnu.org/licenses/gpl.html

jquery.jstree.js

HDD Access elects to include this software in this distribution under the MIT license

 

 jsTree 1.0-rc3

 http://jstree.com/

 Copyright (c) 2010 Ivan Bozhanov (vakata.com)

 Licensed same as jquery - under the terms of either the MIT License or the GPL Version 2 License

 http://www.opensource.org/licenses/mit-license.php

 http://www.gnu.org/licenses/gpl.html

jquery-ui-1.8.16.custom.min.js

HDD Access elects to include this software in this distribution under the MIT license

 

 jQuery UI 1.8.16

Copyright 2011, AUTHORS.txt (http://jqueryui.com/about)

Dual licensed under the MIT or GPL Version 2 licenses.

http://jquery.org/license

http://docs.jquery.com/UI

 

Third Party Files:

slf4j-api-1.6.4.jar

slf4j-log4j12-1.6.4.jar

jcl-over-slf4j-1.6.4.jar

 

http://www.slf4j.org/license.html

SLF4J source code and binaries are distributed under the MIT license.

Copyright (c) 2004-2011 QOS.ch All rights reserved.

 

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Third Party Files:

jQuery

jquery-1.7.2.js

 

HDD Access elects to include this software in this distribution under the MIT license

 

jQuery JavaScript Library v1.7.2

http://jquery.com/

 

Copyright 2011, John Resig

Dual licensed under the MIT or GPL Version 2 licenses.

http://jquery.org/license

 

Includes Sizzle.js

http://sizzlejs.com/

Copyright 2011, The Dojo Foundation

Released under the MIT, BSD, and GPL Licenses.

 

Date: Wed Mar 21 12:46:34 2012 -0700

 

11.  Mozilla Public License (MPL) 1.1

http://opensource.org/licenses/mozilla1.1

Third Party File:

javassist-3.15.0.GA.jar

 

Copyright (C) 1999-2010 by Shigeru Chiba, All rights reserved.

 

12.  SPECIALIST NLP Tools

http://lexsrv3.nlm.nih.gov/LexSysGroup/Docs/termsAndConditions.html

 

Third Party File:

lvg-2012.jar

 

Lexical Tools, 2012 Release. 12/01/2011.

Terms and Conditions for Use of the SPECIALIST NLP Tools

 1. Introduction

The following Terms and Conditions apply for use of the SPECIALIST NLP Tools. Using the SPECIALIST NLP Tools indicates your acceptance of the following Terms and Conditions. These Terms and Conditions apply to all SPECIALIST NLP Tools, independent of format and method of acquisition.

 

2. The SPECIALIST NLP Tools

The Lister Hill National Center for Biomedical Communications, National Library of Medicine, National Institutes of Health, Department of Health and Human Services, has developed the SPECIALIST NLP Tools to investigate the contributions that natural language processing techniques can make to the task of mediating between the language of users and the language of online biomedical information resources. The SPECIALIST NLP Tools facilitate natural language processing by helping application developers with lexical variation and text analysis tasks in the biomedical domain.

 

3. Availability

The SPECIALIST NLP Tools are available to all requesters, both within and outside the United States, at no charge.

 

4. Use of the SPECIALIST NLP Tools

a. Redistributions of the SPECIALIST NLP Tools in source or binary form must include this list of conditions in the documentation and/or other materials provided with the distribution.

b. In any publication or distribution of all or any portion of the SPECIALIST NLP Tools (1) you must attribute the source of the tools as the SPECIALIST NLP Tools with the release number and date; (2) you must state any modifications made to the SPECIALIST NLP Tools along with a complete description of the modifications, which may be in the form of patch files.

c. You shall not assert any proprietary rights to any portion of the SPECIALIST NLP Tools, nor represent the SPECIALIST NLP Tools or any part thereof to anyone as other than a United States Government product.

d. The name of the U.S. Department of Health and Human Services, National Institutes of Health, National Library of Medicine, Lister Hill National Center for Biomedical Communications may not be used to endorse or promote products derived from the SPECIALIST NLP Tools without specific prior written permission.

e. Neither the United States Government, U.S. Department of Health and Human Services, National Institutes of Health, National Library of Medicine, Lister Hill National Center for Biomedical Communications, nor any of its agencies, contractors, subcontractors or employees of the United States Government make any warranties, expressed or implied, with respect to the SPECIALIST NLP Tools, and, furthermore, assume no liability for any party's use, or the results of such use, of any part of these tools.

 

These terms and conditions are in effect as long as the user retains any part of the SPECIALIST NLP Tools.

 

13.  Content Data

The Centers for Medicare and Medicaid Services (CMS) publishes the Healthcare Common Procedure Coding System (HCPCS) level II code set, which includes Dental codes (D codes) provided (and owned) by the American Dental Association.  

http://www.cms.gov/Medicare/Coding/MedHCPCSGenInfo/index.html?redirect=/medhcpcsgeninfo/

and owned) ata Standarditectureeincludes Dental codes (D codes) provided by the American Dental Association.   

Third Party File:

Addendum B. Final OPPS Payment by HCPCS Code for CY 2013

 

Dental codes (D codes) are copyright 2011/12 American Dental Association.  All Rights Reserved.