Common Terminology Services 2 Avatar
  1. OMG Specification

Common Terminology Services 2 — Open Issues

  • Acronym: CTS2
  • Issues Count: 8
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

CTS2: Documentation is incorrect in SpecificEntityList class

  • Key: CTS213-1
  • Legacy Issue Number: 18872
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    referencedEntity in SpecificEntityList is defined as "the namespace / name or URI of the entity to be included".

    It should read "the URI and optional namespace/name and description of the entity to be included".

    Logged: https://github.com/cts2/cts2-specification/issues/166

  • Reported: CTS2 1.1 — Tue, 13 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: SpecificEntityList description is incorrect

  • Key: CTS213-9
  • Legacy Issue Number: 18871
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The ValueSetDefinition SpecificEntityList states that "the service must include all entities in this list whether they are known to the service or not and whether they are ACTIVE or not".

    We do not believe that this is correct – the service still needs to validate this list when constructing a resolved value set and should NOT allow invalid or non-active entries to make it into a "valid" resolved value set.

    The SpecificEntityList description needs to be updated.

    Logged: https://github.com/cts2/cts2-specification/issues/167

  • Reported: CTS2 1.1 — Tue, 13 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: EntityDescription lacks workflow status entry

  • Key: CTS213-12
  • Legacy Issue Number: 18868
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    EntityDescriptionBase doesn't have a status element of type StatusReference. This prevents us from recording the organization's workflow status.

    We propose adding a status element to EntityDescriptionBase.

    Logged: https://github.com/cts2/cts2-specification/issues/163

  • Reported: CTS2 1.1 — Mon, 12 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: ConceptDomain Binding has no property attribute

  • Key: CTS213-11
  • Legacy Issue Number: 18867
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    There is currently no way to extend a concept domain binding with tag/values. This prevents us from adding the HL7 codingStrength and effectiveDate attributes.

    We propose extending ConceptDomain Binding to support a property attribute.

    Logged: https://github.com/cts2/cts2-specification/issues/164

  • Reported: CTS2 1.1 — Mon, 12 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: Children/Descendants use inconsistent with Value Set

  • Key: CTS213-10
  • Legacy Issue Number: 18866
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The EntityDescription model provides hooks for children and descendants, the interpretation of which is left to the service. Value Set Definition, however, provides no equivalent ability where, instead, the associatedEntities have to provide the specific predicate.

    Would recommend making the predicate optional and, if present, describing the exact behavior that the service needs to exhibit.

    Logged: https://github.com/cts2/cts2-specification/issues/165

  • Reported: CTS2 1.1 — Mon, 12 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: ResourceList entries have double "entry" items

  • Key: CTS213-7
  • Legacy Issue Number: 18853
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The resource List (example CodeSystemCatalogEntryList) specifies that the contents should be represented as
    <entry>
    <entry ...>
    <entry ...>
    </entry>

    This pattern is repeated across all lists.

    Logged: https://github.com/cts2/cts2-specification/issues/161

  • Reported: CTS2 1.1 — Tue, 6 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: Wrong type in CompleteValueSetReference (ValueSetDefinition.xsd)

  • Key: CTS213-5
  • Legacy Issue Number: 18852
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    In ValueSetDefinition.xsd in the complex type CompleteValueSetReference, the type for valueSetDefinition is wrong:

    <xs:element name="valueSetDefinition" type="core:ValueSetReference" minOccurs="0" maxOccurs="1">

    The type should be core:ValueSetDefinitionReference.

    Logged: https://github.com/cts2/cts2-specification/issues/160

  • Reported: CTS2 1.1 — Tue, 6 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: ValueSetDefinitionListEntry in ValueSetDefinition.xsd has wrong cardinality

  • Key: CTS213-6
  • Legacy Issue Number: 18851
  • Status: open  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The type ValueSetDefinitionListEntry in ValueSetDefinition.xsd contains an incorrect cardinality:

    <xs:element name="entry" type="ValueSetDefinition" minOccurs="0" maxOccurs="unbounded"/>

    It should contain one and only one entry:

    <xs:element name="entry" type="ValueSetDefinition"/>

  • Reported: CTS2 1.1 — Tue, 6 Aug 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT