CTS Conformance

Compliance Issues in CTS I

Listed below are some of the issues found during implementation of CTS I, and proposals for CTS I compliance:

Relationship Code

Issue: The CTS I specification states that the values must be drawn from the "ConceptRelationshipCode" code system. Only a few values are given in the “ConceptRelationshipCode” code system, and no standard is referenced.

Compliance: An implementation of CTS I service shall be considered compliant if it normalizes the relationship codes used by all the coding schemes supported by the service.

RelationshipQualifiers

Issue: No detail about this attribute has been mentioned in CTS I specification.

Compliance: Support of Relationship Qualifiers by an implementation of CTS I is optional. If Relationship Qualifiers are not supported, the API returning qualifiers (areCodeRelated()) shall return null (rather than throwing an exception).

PropertyCode

Issue: A combination of a code system id and concept code that identifies the type of property. Whenever possible, property codes should use the HL7 “ConceptProperty” code system. The definition is not clear. need clarification. If the values are being drawn from “ConceptProperty” code system then how can the property code be a combination of code system ID & concept code?.

Compliance: An implementation of CTS I service shall be considered compliant if it normalizes the property codes used by all the coding schemes supported by the service.

MapQualityCode

Issue: CTS I specification states that the value needs to be drawn from "TranslationalQuality" code system. This code system is missing from the repository.

Compliance: An Implementation of CTS I shall be considered compliant if it normalizes the map quality code used for mapping the concepts in the code systems supported by the service.

Language Code

Issue: CTS I specification states that language code is a code for a spoken or written language that follows the rules described in IETF RFC 3066 – Tag for Identification of Languages.

Compliance: An implementation of CTS I shall be considered compliant if it supports any subset of IETF language codes.

Mime Types

Issue: CTS I specification states that the codes must be drawn from the officially designated HL7 Media Type code system, which is currently OID 2.16.840.1.113883.5.79 - MediaType. Only few values are given in the “MediaType” code system.

Compliance: An Implementation of CTS I shall be considered compliant if it supports a subset of Media Types.