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

Difference between revisions of "CTS Implementation"

From HL7Wiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 3 users not shown)
Line 2: Line 2:
  
 
== Existing CTS Implementations ==
 
== Existing CTS Implementations ==
−
=== Mayo Clinic CTS Reference Implementation === 
 
  
−
http://informatics.mayo.edu/LexGrid/index.php?page=ctsimpl
+
=== Mayo Clinic CTS Reference Implementation ===
  
 
=== openEHR CTS C# Implementation ===  
 
=== openEHR CTS C# Implementation ===  
Line 13: Line 12:
 
=== Background ===
 
=== Background ===
 
* '''HL7 / Mayo Clinic'''
 
* '''HL7 / Mayo Clinic'''
−
**[http://www.hl7.org/ Health Level Seven (HL7)], an [http://www.ansi.org/ American National Standards Institute (ANSI)] -accredited Standards Developing Organization (SDO) operating in the healthcare arena,  recently published a standard for API’s to access clinical terminologies.  This specification, which is called the [http://informatics.mayo.edu/informatics_pages/standards/cts/specification/ctsSpec/cts.htm Common Terminology Services (CTS)], defines a set of interfaces that can be used to discover and query terminology content.  The scope of the CTS specification was limited to (a) read-only use cases and (b) only the use cases that were necessary to satisfy near-term HL7 requirements.
+
**[http://www.hl7.org/ Health Level Seven (HL7)], an [http://www.ansi.org/ American National Standards Institute (ANSI)] -accredited Standards Developing Organization (SDO) operating in the health care arena,  recently published a standard for API’s to access clinical terminologies.  This specification, which is called the [https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Common_Terminology_Services Common Terminology Services (CTS)], defines a set of interfaces that can be used to discover and query terminology content.  The scope of the CTS specification was limited to (a) read-only use cases and (b) only the use cases that were necessary to satisfy near-term HL7 requirements.
  
 
* '''NHS'''
 
* '''NHS'''
Line 19: Line 18:
  
 
'''* Eclipse OHF'''
 
'''* Eclipse OHF'''
−
** A brief blurb about why you are involved and what you are looking for.
+
Users are looking to OHF to provide a CTS implementation under EPL
 +
OHF needs a CTS to support a number of projects in it's future.
 +
OHF is a good and proper place to build a community of developers around an open source reference implementation of CTS
  
 
=== Project Team ===
 
=== Project Team ===
Line 32: Line 33:
 
** Bing Yang
 
** Bing Yang
  
−
* Australian Team (whoever you represent Grahame :)
+
* Eclipse OHF
−
** Grahame Grieve  
+
** Grahame Grieve (Jiva Medical)
  
 
==== Project Lead(s) ====
 
==== Project Lead(s) ====
−
* Open  
+
* Open (gg: Should be Russ Hamm ;-)
  
 
==== Development Lead(s) ====
 
==== Development Lead(s) ====
−
* Open
+
* Dan Armbrust
  
 
=== Infrastructure ===
 
=== Infrastructure ===
  
 
==== The CTS Implementation Wiki (this and related pages) ====
 
==== The CTS Implementation Wiki (this and related pages) ====
−
* Hosted by Mayo Clinic at http://informatics.mayo.edu/wiki/index.php?title=CTS_Implementation
+
* Hosted by Mayo Clinic at https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Common_Terminology_Services
  
 
==== The CTS Implementation Mail Server ====
 
==== The CTS Implementation Mail Server ====
−
* Established by Grahame Grieve. To get someone added to the list, send an email to jamies@kestral.com.au
+
* Established by Grahame Grieve, the mail address is: '''cts-impl@kestral.com.au'''
 +
* To get someone added to the list, send an email to either '''grahame@kestral.com.au''' or '''jamies@kestral.com.au'''
  
 
=== Open Source Development Process ===
 
=== Open Source Development Process ===
Line 54: Line 56:
 
=== Open Source Testing Process ===
 
=== Open Source Testing Process ===
 
* Open
 
* Open
 +
* but we agree that regression testing is that basis of solid implementations
  
 
== CTS Support Tooling ==
 
== CTS Support Tooling ==
−
* Required tooling that falls outside the scope of CTS that may end up being integated into [http://informatics.mayo.edu/wiki/index.php/CTS2, CTS II]
+
* Required tooling that falls outside the scope of CTS that may end up being integrated into [https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Common_Terminology_Services_2 CTS 2]
  
 
=== Front End Tooling ===
 
=== Front End Tooling ===
 
* Front end tooling that supports browsing/viewing the content of a terminological resource via CTS APIs.
 
* Front end tooling that supports browsing/viewing the content of a terminological resource via CTS APIs.
−
 
−
==== The LexGrid Editor ====
 
−
[http://informatics.mayo.edu/LexGrid/index.php?page=lge, The LexGrid Editor]
 
  
 
=== Back End Tooling ===
 
=== Back End Tooling ===
Line 68: Line 68:
  
 
==== The Lexical Grid (LexGrid) data model ====
 
==== The Lexical Grid (LexGrid) data model ====
−
* [http://informatics.mayo.edu/LexGrid/index.php?page=aboutlg, The Lexical Grid]
+
* [https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/LexGrid_Model_and_Schema The Lexical Grid]
  
 
== Eclipse Open Health Framework (OHF) ==
 
== Eclipse Open Health Framework (OHF) ==

Latest revision as of 17:52, 23 March 2011

CTS Implementation WIKI

Existing CTS Implementations

Mayo Clinic CTS Reference Implementation

openEHR CTS C# Implementation

Mayo Clinic Open Source CTS Project

Background

  • HL7 / Mayo Clinic
    • Health Level Seven (HL7), an American National Standards Institute (ANSI) -accredited Standards Developing Organization (SDO) operating in the health care arena, recently published a standard for API’s to access clinical terminologies. This specification, which is called the Common Terminology Services (CTS), defines a set of interfaces that can be used to discover and query terminology content. The scope of the CTS specification was limited to (a) read-only use cases and (b) only the use cases that were necessary to satisfy near-term HL7 requirements.
  • NHS
    • A brief blurb about why you are involved and what you are looking for.

* Eclipse OHF Users are looking to OHF to provide a CTS implementation under EPL OHF needs a CTS to support a number of projects in it's future. OHF is a good and proper place to build a community of developers around an open source reference implementation of CTS

Project Team

  • Mayo Clinic Team
    • Harold Solbrig
    • Thomas Johnson
    • Dan Armbrust
    • Russell Hamm - Hamm.Russell@mayo.edu
  • NHS Team
    • Adam Flinton
    • Bing Yang
  • Eclipse OHF
    • Grahame Grieve (Jiva Medical)

Project Lead(s)

  • Open (gg: Should be Russ Hamm ;-)

Development Lead(s)

  • Dan Armbrust

Infrastructure

The CTS Implementation Wiki (this and related pages)

The CTS Implementation Mail Server

  • Established by Grahame Grieve, the mail address is: cts-impl@kestral.com.au
  • To get someone added to the list, send an email to either grahame@kestral.com.au or jamies@kestral.com.au

Open Source Development Process

  • Open

Open Source Testing Process

  • Open
  • but we agree that regression testing is that basis of solid implementations

CTS Support Tooling

  • Required tooling that falls outside the scope of CTS that may end up being integrated into CTS 2

Front End Tooling

  • Front end tooling that supports browsing/viewing the content of a terminological resource via CTS APIs.

Back End Tooling

  • Back end tooling that supports storage and ersistance of the content of a terminological resources.

The Lexical Grid (LexGrid) data model

Eclipse Open Health Framework (OHF)

  • Ideas on how this project (or parts of it)can/should/may integrate in the domain of the Eclipse OHF

Background

  • Open
Retrieved from "https://wiki.hl7.org/w/index.php?title=CTS_Implementation&oldid=48053"