Main Page

The "final" specification has been submitted to the OMG. Final is in quotes because there is still a significant amount of work that needs to be done before this can be called complete - details of which can be found below.

The specification, as submitted, consists of the following components:

• Submission Inventory of Files
• Main CTS2 Submission - Introductory material
• Platform Independent Model - this section describes the formal model and semantics of the various components of the submission.
  • Core Components - Data Types, structures and building blocks that are shared across more than one of the structural or functional profiles.
  • Code System and Code System Version catalog services - Services to read, query and update catalogs of code systems (aka. "ontologies", "classification systems", "terminologies", etc.) and their releases.
  • Entity Description and Association Services - Services to read, query and update the lexical (Entity Services) and semantic (Association services) content of the contents of code systems.
  • Value Set Catalog and Value Set Definition Services - Services to read, query and update metadata about value sets (Value Set Catalog) and their definitions (Value Set Definition).
  • Concept Domain Catalog and Concept Domain Binding Services - Services to read, query and update catalogs of concept domains (aka. Data Element Concepts) and concept domain bindings (aka. Data Elements).
  • Map Catalog and Map Version Services - Services to read, query and update metadata about maps (Map Catalog) and map content (Map Versions).
  • Statement Model and Services - Services for representing the minimal subject, predicate and object model used in RDF.
  • UML Model of the PIM
  • UML Model of the PIM (XMI)
• Platform Specific Model - this section contains an XML Schema rendering of each of the above components as well as the WSDL and WADL descriptions of the corresponding services
  • WSDL and WADL

While the contents of the above submission is reasonably solid, there is still considerable room for improvement - especially in the area of document and testing. In particular, the following tasks are still outstanding:

• CTS2 Primer - we still need to produce an overview document that describes the various components, provides examples, etc.
• Z Behavioral Specification - Some of the components of the submission have been formally specified in Z. This task, however, is still not complete and will continue to be added. We view the Z as a component of the OMG's "Finalization Task Force (FTF)", whose job it is to correct and solidify the specification as submitted.
• Canonical RDF Specification - An additional PSM for the information model that describes a "canonical" RDF rendering - establishing the tags and structure to represent the various CTS2 resources in RDF format
• ISO 21090 PSM - Portions of the CTS2 model (concept domains and value set resolution) should be representable using the ISO 21090 Healthcare Datatypes. This portion of the modeling still needs to be completed.
• Proof reading, testing and additional documentation - it will quickly become obvious that there is still a great deal of work that could (and should) be done on the submission. This will be an ongoing task for the Finalization Task Force.

The following changes have been applied to the working copy subsequent to its submission to the OMG:

We are in the process of finalizing the documentation, filling in the blanks, filling out some of the more egregious errors, etc. The updated documents are:

• CoreComponents PIM
• EntityDescriptionServices PIM
• CodeSystemCatalogServices PIM
• ValueSetServices PIM
• ConceptDomainServices PIM
• MapServices PIM
• StatementServices PIM

• OMG CTS₂ RFP - the CTS₂ RFP as issued by the OMG
• CTS 2 Service Functional Model (SFM)
• ISO 2010 Editors draft of 11179 Edition 3 Part 3
• CTS Specification (Also an ISO specification now)
• OMG LQS Specification
• OMG MOF 2.0 Specifications
• OMG ODM 1.0 Specifications
• UML 2.2 Superstructure and Infrastructure
• RM-ODP Wiki - jump off point for RM-ODP documentation
• 2009 SKOS Reference Specification
• OWL 1.1 Structural and Functional-Style Syntax - contains UML models of OWL
• OWL Working group home page
• ClaML
• PHIN VADS Functionality

Post OMG Submission Questions and answers

Clonation

Q: In the pim there are some hints about a 'clonation' system as the CLONED value of the ChangeType enum and the ChangeDescription.clonedResource field suggest. But in no service there is reference to cloning, so how could we get a clone of a Changeable resource?

Answer

EntityDescriptionReadService

Q: How can there be multiple entity descriptions when the entityID uniquely identifies the EntityDescription

Answer

CodeSystemVersionReadService

Q: How does the service set the codeSystemVersionTag?

Answer

EntityResourceType

Q: What goes in the CTS2ResourceType for EntityDirectory

Answer

FilterComponents

Q: Can secondary properties (propertyQualifier, correspondingStatement, etc) be used as filter and sort components?

Answer