${taskforce.name} Avatar
  1. OMG Task Force

Common Terminology Services 2 (CTS2) 1.3 Revision Task Force — All Issues

  • Key: CTS213
  • Issues Count: 13
Open Closed All
All Issues

Issues Descriptions

Faulty CTS2 1.1 wsdl files

  • Key: CTS213-13
  • Legacy Issue Number: 19832
  • Status: open  
  • Source: Anonymous
  • Summary:

    The wsdl files provided at http://www.omg.org/spec/CTS2/1.1/ are not correct. #
    We tried to generate java services with wsdl2java using these wsdl and xsd files but got errors due to faulty namespace settings and incorrect fault settings in the methods.

    Where can we obtain the correct wsdl files to implement CTS2 specification conform soap services?

  • Reported: CTS2 1.2 — Thu, 10 Sep 2015 04:00 GMT
  • Updated: Thu, 10 Sep 2015 13:16 GMT

Usage Context Binding Inappropriately Expressed

  • Key: CTS213-2
  • Legacy Issue Number: 18519
  • Status: open  
  • Source: Phast ( Ana Estelrich)
  • Summary:

    The Usage Context (in the PIM the applicableContext) is represented as an attribute of the ConceptDomainBinding class. applicableContext - a realm or context in which the particular binding applies. If not present, the binding applies in any context not stated in another binding.
    In the SFM it is represented as a class entirely apart providing detailed information about the binding. If we have two different value sets belonging to the same Concept Domain but with different usage contexts, this cannot work. Moreover, in most implementation guides, the Concept Domains are not specified, indicting just the Usage Context as Concept Domains are something very specific to HL7 (they can be inferred), and the Usage Contexts are expressed as OIDs and not as URIs (enforcing the fact that we need the possibility to simultaneously define an entity via an URI and an OID)

    Use Case:
    The value set epSOSActiveIngredient 1.3.6.1.4.1.12559.11.10.1.3.1.42.24 consists of the whole ATC and it is the most important piece of information in the medication identification in epSOS. The same value set is being used in 3 different documents in 4 different sections with 4 different entries:

    Prescription Item Entry 1.3.6.1.4.1.12559.11.10.1.3.1.3.2
    Dispensed Medicine Entry
    1.3.6.1.4.1.12559.11.10.1.3.1.3.3
    Medication Item Entry
    1.3.6.1.4.1.12559.11.10.1.3.1.3.4
    Allergy & Intolerance Concern Entry
    1.3.6.1.4.1.19376.1.5.3.1.4.5.3

    Prescription Section
    1.3.6.1.4.1.12559.11.10.1.3.1.2.1
    Dispensation Section
    1.3.6.1.4.1.12559.11.10.1.3.1.2.2
    Medication Summary Section 1.3.6.1.4.1.12559.11.10.1.3.1.2.3
    Allergies and Other Adverse Reactions Section
    1.3.6.1.4.1.19376.1.5.3.1.3.13

    In the follwing documents:
    ePrescription
    eDispensation
    Patient Summary
    Patient Summary

    The corresponding Concept Domain is EntityCode and the subdomain is ActiveIngredientDrugEntityType for all four Usage Contexts; however they are entirely different. Logged: https://github.com/cts2/cts2-specification/issues/146

  • Reported: CTS2 1.0 — Fri, 1 Mar 2013 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Using enumerations instead of using code systems

  • Key: CTS213-3
  • Legacy Issue Number: 18518
  • Status: open  
  • Source: Phast ( Ana Estelrich)
  • Summary:

    The PIM uses enumeration rather than having a code system of its own. This does not allow for new codes to be added easily (need another enumeration), a separate documentation is needed for the definition of what the enumerations mean, and translations are not possible. Two such examples are the enumeration Resource Type with 7 possible values such as CODE_SYSTEM, CODE_SYSTEM_VERSION, CONCEPT_DOMAIN, MAP, MAP_VERSION, VALUE_SET, VALUE_SET_DEFINITION and the enumeration CHANGE TYPE with the enumerations: CREATE, UPDATE, METADATA, DELETE, CLONE, IMPORT. It would good terminology practice for the international specifications of terminology server to use an internal code system rather than use enumerations. Logged: https://github.com/cts2/cts2-specification/issues/145

  • Reported: CTS2 1.0 — Fri, 1 Mar 2013 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CTS2: Documentation is incorrect in SpecificEntityList class

  • Key: CTS213-1
  • Legacy Issue Number: 18872
  • Status: open  
  • Source: Mayo Clinic ( Mr. 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: ConceptDomain Binding has no property attribute

  • Key: CTS213-11
  • Legacy Issue Number: 18867
  • Status: open  
  • Source: Mayo Clinic ( Mr. 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 ( Mr. 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: SpecificEntityList description is incorrect

  • Key: CTS213-9
  • Legacy Issue Number: 18871
  • Status: open  
  • Source: Mayo Clinic ( Mr. 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 ( Mr. 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: "readContext" missing on ResolvedValueSetResolution functions


AssociationQueryServices WSDL corrections

  • Key: CTS213-4
  • Legacy Issue Number: 17181
  • Status: open  
  • Source: Mayo Clinic ( Mr. Craig Stancl)
  • Summary:

    Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.

    Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.

    Rename method 'getSupportedVersionTags' to 'getSupportedVersionTag'.

    In method 'restrictToTargetExpression' change the type of param 'target' to EntityExpression

    In method 'count' add parameter 'timeout'.

    In method 'getAllSourceAndTargetEntities' change the type of param 'directory' to EntityDirectoryURI

    In method 'restrict' change the type of param 'directory' to DirectoryURI

    In method 'restrictToTargetLiteral' change the type of param 'target' to String

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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05: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 ( Mr. 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 ( Mr. 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

CTS2: ResourceList entries have double "entry" items

  • Key: CTS213-7
  • Legacy Issue Number: 18853
  • Status: open  
  • Source: Mayo Clinic ( Mr. 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