This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Candidate Terminology Service Solutions"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "Possible solutions to consider for HL7 Tooling replacement * 3M HDD and Terminology Services (https://www.hddaccess.com/home/overview email Sentil) * Apelon DTS 4.x * CareCom...")
 
 
(4 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
* 3M HDD and Terminology Services (https://www.hddaccess.com/home/overview email Sentil)
 
* 3M HDD and Terminology Services (https://www.hddaccess.com/home/overview email Sentil)
 +
** Proprietary (HDD)
 +
** Open Source (HDD Open Access)
 
* Apelon DTS 4.x
 
* Apelon DTS 4.x
 
* CareCom (http://www.care.com)
 
* CareCom (http://www.care.com)
 
* Clinical Architecture (http://www.clinicalarchitecture.com/products/symedical-server/what-is-symedical/)
 
* Clinical Architecture (http://www.clinicalarchitecture.com/products/symedical-server/what-is-symedical/)
 
* Health Language (Language Engine)
 
* Health Language (Language Engine)
* IMO (ask Gaye on status and capabilities - Columbia International eHealth Laboratory (CIEL))
+
* IMO  
 +
* Ontoserver (http://ontoserver.csiro.au/)
 
* Open Toolkit Framework (Rory) - http://ihtsdo.github.io/  
 
* Open Toolkit Framework (Rory) - http://ihtsdo.github.io/  
* Revamp existing HL7 tool set (ya, right)
+
* Revamp existing HL7 tool set  
 
* Snow Owl Terminology Server
 
* Snow Owl Terminology Server

Latest revision as of 17:45, 17 August 2016

Possible solutions to consider for HL7 Tooling replacement