This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Candidate Terminology Service Solutions"
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 8: | Line 8: | ||
* 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 | + | * IMO |
| − | * Ontoserver (ontoserver.csiro.au/) | + | * 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 | * 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
- 3M HDD and Terminology Services (https://www.hddaccess.com/home/overview email Sentil)
- Proprietary (HDD)
- Open Source (HDD Open Access)
- Apelon DTS 4.x
- CareCom (http://www.care.com)
- Clinical Architecture (http://www.clinicalarchitecture.com/products/symedical-server/what-is-symedical/)
- Health Language (Language Engine)
- IMO
- Ontoserver (http://ontoserver.csiro.au/)
- Open Toolkit Framework (Rory) - http://ihtsdo.github.io/
- Revamp existing HL7 tool set
- Snow Owl Terminology Server
