Revision as of 16:44, 2 June 2015

Minutes DD-Mon-YYYY

Identified existing sources of functionality in use by HL7. Review initial spreadsheet on wiki and discussed how to complete. Apelon volunteered assistance to extract functional requirements from VML/CTS2.

Identified potential candidate solutions located here [1]

Get sign off on requirements from Vocab/Tooling
Draft RFI (with HL7 support)
If we can get rqmts and RFI drafted before WGM, would be nice to give people the opportunity to present at the HL7 WGM to further inform the RFI and requirements

@@ Line 23: / Line 23: @@
 === Candidate Solutions ===
-Identified potential candidate solutions including:
+Identified potential candidate solutions located here [http://wiki.hl7.org/index.php?title=Candidate_Terminology_Service_Solutions]
-* 3M HDD and Terminology Services (https://www.hddaccess.com/home/overview email Sentil)
-* 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 (ask Gaye on status and capabilities - Columbia International eHealth Laboratory (CIEL))
-* Open Toolkit Framework (Rory) - http://ihtsdo.github.io/
-* Revamp existing HL7 tool set (ya, right)
-* Snow Owl Terminology Server
 === Discussion ===