This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CTS Implementation"
Jump to navigation
Jump to search
| (26 intermediate revisions by 4 users not shown) | |||
| Line 2: | Line 2: | ||
== Existing CTS Implementations == | == Existing CTS Implementations == | ||
| − | === Mayo Clinic CTS Reference Implementation === | + | |
| − | + | === Mayo Clinic CTS Reference Implementation === | |
=== openEHR CTS C# Implementation === | === openEHR CTS C# Implementation === | ||
| Line 9: | Line 9: | ||
== Mayo Clinic Open Source CTS Project == | == Mayo Clinic Open Source CTS Project == | ||
| + | |||
| + | === Background === | ||
| + | * '''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 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''' | ||
| + | ** 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 === | === 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) ==== | ==== Project Lead(s) ==== | ||
| − | * Open | + | * Open (gg: Should be Russ Hamm ;-) |
| + | |||
==== Development Lead(s) ==== | ==== Development Lead(s) ==== | ||
| + | * Dan Armbrust | ||
| + | |||
| + | === Infrastructure === | ||
| + | |||
| + | ==== The CTS Implementation Wiki (this and related pages) ==== | ||
| + | * Hosted by Mayo Clinic at https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Common_Terminology_Services | ||
| + | |||
| + | ==== 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 [https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Common_Terminology_Services_2 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 ==== | ||
| + | * [https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/LexGrid_Model_and_Schema The Lexical Grid] | ||
| + | |||
| + | == 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 | * Open | ||
Latest revision as of 17:52, 23 March 2011
CTS Implementation WIKI
Contents
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
- Hosted by Mayo Clinic at https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Common_Terminology_Services
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
