alist of the representation formats
supported by the service. Example: text/html, text/xml, application/json
the version or release identifier of
the service
the default format used by the
service unless otherwise specified
the set of namespaces recognized by
this service. Because many namespace identifiers tend to be cryptic (i.e. HL7 OIDs, BioPortal
URL's, etc.), <i>knownNamespace</i> includes the namespace name, an optional URI
\emph{and} a place to provide textual detail describing what the namespace references. Note
that namespace names must be unique across an entire CTS2 implementation - the same
namespace name cannot represent one namespace in code system A and a second in code system B.
Note also that namespace names are \emph{local} to a service instance. Information that is
communicated between service instances, recorded in data tables or client software
\emph{must} use full URIs.
a reference to the individual or
organization that provides the service.
the set of service profiles that are
supported by this service implementation
a description of the service, its
use, etc.
a short name that identifies the
particular service and implementation
the particular implementation type(s)
supported by this profile
The set of version tags known to the
service. All services must recognize the "CURRENT" tag, although interpretation is service
specific.
Determine whether a concept domain
binding with the supplied DocumentURI existsDetermine whether a concept domain binding with
the supplied DocumentURI exists
Determine whether a concept domain
binding exists for the specified domain, value set, realm and context. Note that only the
<i>conceptDomain</i> name and/or <i>valueSet</i> names must be
validated. A service implementation may choose whether to validate the URI's or simply assume
that, if not found in the service, they reference external elements.Determine whether a
catalog entry exists that has an <i>about</i> or <i>alternateId</i>
that matches the supplied URI or that has a <i>codeSystemName</i> that matches
the supplied name that is (was) applicable in the supplied
<i>context.</i>
The named <i>conceptDomain</i> is not recognized by the
service
One or more <i>changeSetContext</i> is not supported by the
service
The <i>bindingQualifier</i> is not recognized by the
system.
The value set name or URI is not recognized by the service
Return the concept domain binding
with the supplied DocumentURI.Return the concept domain binding with the supplied
DocumentURI.
The <i>conceptDomainBinding</i> URI is not recognized by the
service
Return the concept binding for the
specified domain, value set, realm and context. Note that only the
<i>conceptDomain</i> name and/or <i>valueSet</i> names must be
validated. A service implementation may choose whether to validate the URI's or simply assume
that, if not found in the service, they reference external elements.Return the catalog entry
that has an <i>about</i> or <i>alternateId</i> that matches the
supplied URI or that has a <i>codeSystemName</i> that matches the supplied name
that is (was) applicable in the supplied <i>context.</i>
The <i>conceptDomainBinding</i> URI is not recognized by the
service
The named <i>conceptDomain</i> is not recognized by the
service
One or more <i>changeSetContext</i> is not supported by the
service
The <i>bindingQualifier</i> is not recognized by the
system.
The value set name or URI is not recognized by the service
A service that provides direct read
access to bindings that are asserted between concept domains and value sets.