a non-empty sequence of characters. As terminological resourcesare often multilingual, it is expected that most CTS₂ Platform SpecificModels (PSMs) will require that the String implementation supportinternational character sets. represents an "Instant" as defined in the OWL Time Specification CTS₂ implementations must be able to support temporal units of second, minute, hour, day, month, and year, and be able to represent and compare instances represented in any of these units. DateAndTime can only provide a partial ordering and, as a consequence, is never used as an index, unique identifier or to sequence data or events. "An enumeration defines a set of literals that can beused as its values" _{UML Infrastructure, Version 2.3, Section 10.3.2}. Because enumerations is a built in part of the UML meta model, the \guillemotleft enumeration \guillemotright ~stereotype is used to represent them in the UML rendering. an identifier that uniquely references a class, individual, property or other resource within the context of a specific CTS₂ service implementation. LocalIdentifier syntax must match the PNAME\_LN production as defined in the SPARQL Query Specification . LocalIdentifiers may begin with leading digits, where XML Local Identifiers and NameSpaceIdentifiers may not an identifier that uniquely references thescoping namespace of an Entity (class, role or individual) within a the context of a CTS₂ service NamespaceIdentifier syntax must match the PNAME\_NS production as defined in the SPARQL Query Specification - meaning that it must begin alphabetic character. a Universal Resource Identifier (URI) as defined in IETF RFC 3986. CTS₂ implementations are encouraged to consider implementing this data type using the IRI (RFC3987) specification. represents the relative strength of the result of a search. Represented as a real number $\mathbb{R}$ such that $0.0 < MatchStrength \leq 1.0$. a non-negative integer ($\nat$). NaturalNumber is used exclusively for representing quantities in this specification. a quantity of time. AmountOfTime is used exclusively to represent service timeout limits. An opaque inner type that can contain any well-formed, but arbitrary information. PSM Opaque data is the equivalent of an ASN.1 External Type _{ISO/IEC 8824-1:2008 Information technology -- Abstract Syntax Notation One (ASN.1): Specification of basic notion. Clause 37 - Notation for the external type} or the XML Schema anyType. An OpaqueData instance may represent text with an optional spoken or written language code or a formal structure such as embedded HTLM, XML or MIME encoded data. When a formal structure is included, its type should be specified in the format attribute and, when the type is an XML variant, the corresponding schema (or DTD) should be included in the schema parameter.The OpaqueData data type must be encoded in such a way that the content can be represented by a character string. Binary data is not permitted,although hyperlinks \emph{to} binary data are. The instance value. Note that instance value should be encoded in such a way that it allows embedded structures. As an example, in XML Schema, this encoding should be to xs:anyType or an equivalent. The format or encoding for value. This is typically recorded as the URI of a Mime Type. A reference to the written or spoken language used in value. If the format of the document involves an XML encoding, this contains the URI of a document that carries the corresponding XML Schema or DTD. EntryDescription is a subclass of OpaqueData. The purpose behind this is that there are certain textual fields that some CTS₂ service implementations may want constrain. As an example, Designation text is of type EntryDescription, but implementations may want to restrict the OpaqueData value attribute to a simple string rather than xs:anyType. When OpaqueData appears directly as a model element, implementations must be able to support the full OpaqueData model. EntryDescription, however, may be constrained by implementations or specialized PSMs. A Universal Resource Identifier (URI) that persists across service instances. Persistent URI's have enduring reference and meaning. The unique identifier of a set of change instructions that can potentially transform the contents of CTS₂ service instance from one state to another. A reference to a "work" in the bibliographic sense. It is not necessary that a DocumentURI be directly or indirectly resolvable to a digital resource - it may simply be the name of a book, publication or other abstraction. A URI that names a unique resource. CTS₂ implementations should never assume that ExternalURI is resolvable via an http: GET operation - ExternalURIs should always be first passed to an URI resolution service. A URI whose scope is local to the implementing service. LocalURI cannot be used as a permanent identifier in a message or a data record. The unique name of a query that, when executed results in a list of resources that, in the context of a given service, satisfy the query. A URI that is directly readable by a specific instance of a CTS₂ service implementation. RenderingURI must resolve to Changeable CTS₂ element. The URI or handle of a service implementation. The state of this model element in an externally defined workflow. An indicator that states whether the Changeable element is ACTIVE, and subject to searching and browsing access or INACTIVE, meaning that it is only accessible if its identity is already known or if the service calls specifically state that they want to see inactive service elements. An element that can evolve over time. All Changeable elements must have identity. The current state of the Changeable element. Note that entryState represents the state of the element itself - \emph{not} the state of a given change. The applicability of a given change is identified by its effectiveDate, not entryState. The ChangeAble element is no longer considered to be an active component. The element may still be retrieved if its entryID is known, but it does not appear in search and browse operations unless specifically requested. The Changeable element is considered to be an active member of the containing resource and may appear in any search, browse or query operations. The detailed description of what happened to a changeable resource. ChangeDescription will only be present in service profiles that support either the History or MAINTENANCE profiles. Notes, instructions and other information about the nature and purpose of this change The person or organization responsible for this change. The local identifier and URI of the resource that was cloned in this change if this is a CLONE operation. The type of change that occurred to cause the associated Changeable element to reach the state it is in. An indicator that states whether the change has been committed and is available to service consumers or is still pending while further authoring may occur. committed must always be COMMITTED in services that do not support the MAINTENANCE profile. The URI of the ChangeSet that contains the described change The URI of the ChangeSet that contains the change that immediately preceded this change, if any. The date and time when this change was applied to the \emph{local service instance}. changeDate is only present on committed changes. The date and time that this change is (or was) scheduled to take effect in the \emph{lcal service instance}. Typically this attribute is used to schedule a component to become active on a given date.A change having a future effectiveDate will not be visible to service calls whose reference time is earlier to this time. This attribute may only be present in committed changes. A compliant CTS₂ service implementation MUST not allow a change to be written with a effectiveDate that is earlier than changeDate. The purpose of this requirement is to prevent the "rewriting of history" - making a change effective in the past. An indicator that shows the type of change that occurred that transformed a Changeable element from its immediately previous state to the state that the ChangeType is associated with. The element was newly created. One or more non-identifying attributes of the element changed. Note that UPDATE does not include changes to the Changeable attributes (entryState, status, and owner). These are considered to be METADATA changes. A change occurred to the entryState, status or owner attributes. METADATA changes are separated because they may often be service specific. The changeable element was completely removed from the service and may no longer be retrieved by id \emph{or} search. Service implementations may choose to disable and/or map DELETE operations to some other form, but this exists to allow the complete removal of errors and historically irrelevant information. Create the new versionable resource and create a (virtual) copy of all of the resource's dependents Include the contents of an external The commitment state of an individual change. The specific change is part of an OPEN change set and has not yet been committed to the database. The change is only visible through queries that carry the ChangeSetURI of the open ChangeSet. The specific change is a part of a ChangeSet that has reached a FINAL state, meaning that it is (or will be) considered an official part of the service content. A common base for various change set elements. This exists to allow ChangeSet to be represented as a choice in the "Updates" module PSM The person or organization who initially created the change set. Documentation and instructions about the purpose and application of the change set. A globally unique identifier that signifies this particular change set. The date and time that the change set was initially created. The date and time that this set of changes became (or should become) effective \emph{from the perspective of the authors}. This parameter enables history queries from both the perspective of the service ("What did the service return on July 1") and the perspective of the resource author ("What would the state of the terminology have been on July 1 had it been loaded prior to that date and not been locally modified?"). The date and time that this change set was finalized (state = FINAL). Once finalized, a change set cannot be further modified. The count of the number of Changeable members in the set The Finalizable mixin determines whether a resource version or a change set is still undergoing change (OPEN) or has reached its final state (FINAL). the state of the inheriting resource Possible states of a Finalizable resource The contents of a ChangeSet or ResourceVersionDescription may change, meaning that the contents cannot be determined by using the ChangeSetURI or DocumentURI. The contents of a ChangeSet or ResourceVersionDescription cannot be changed, meaning that they can be unambiguously referenced via the corresponding URI. Provides a directory or list of resources that match a specific filter and are ordered in a specified order. A directory is read-only and is not necessarily immutable.Note that the name of the link to DirectoryEntry is called "entries" rather than "entry". This allows subclasses to use "entry" without type collisions in the Z. The filter(s) that were applied to generate this directory The sort criteria used in the directory. When this is left as optional, there is the possibility that some directories may not be ordered. Some PSMs may chose to make sortCriteria mandatory, meaning that all directory listings must reflect some sort order. An indicator that states whether the complete directory listing is included in entries or whether additional retrievals are needed to get the full listing. The number of entries in this directory segment. Note that this is \emph{not} the total number of entries in the complete directory listing - just the number of entries in this segment. A URI that, when de-referenced, produces the preceding set of entries in the directory. A URI that, when de-referenced, produces the next set of entries in the directory. A LocalURI that resolves to the full resource described by the DirectoryEntry. This should be present if the service either (a) supports the Read functional profile for the specified type or (b) is aware of another service that does. an local identifier that names a unique resource within the context of type and the service context. This attribute must be present if the corresponding element has a local name. Note, however, that some elements (e.g. Association, ValueSetDefinition, etc.) do not A relative measure of the "goodness of fit" of the directory entry within the context of the directoryFilter in the containing Directory. An entry in a directory. DirectoryEntry is a mixin that identifies the attributes that must or may be present in any element that can be represented as an entry in a Directory. An indicator that determines whether a Directory contains all of the qualifying entries or only some. The Directory contains all of the qualifying entries The directory contains only a partial listing of the qualifying entries A DirectoryURI that references a set of Associations. A DirectoryURI that references a set of ChangeSets. A DirectoryURI that references a set of CodeSystemCatalogEntries. A DirectoryURI that references a set of CodeSystemVersionCatalogEntries. A DirectoryURI that references a set of ConceptDomainCatalogEntries A DirectoryURI that references a set of ConceptDomainBindings. A DirectoryURI that references a set of EntityDescriptionDirectory. A DirectoryURI that references a set of MapCatalogEntries. A DirectoryURI that references a set of MapVersions. A DirectoryURI that references a set of MapEntries A DirectoryURI that references a set of Statements. A DirectoryURI that references a set of ValueSetCatalogEntries. A DirectoryURI that references a set of ValueSetDefinitions. The URI, local namespace and name and optional designation of an EntityDescription. EntitySynopsis represents entities when they are referenced from the context of a single code system, such as the resolution of value sets and association graphs. A designation considered appropriate for the entity in the specific context of use The URI, namespace/name (if known) and a list of code systems that make assertions about the entity. The namespace and name by which this entity is known within the context of the service implementation. A reference to a version of a code system that makes one or more assertions about the referenced entity. Note that only one version of a given code system is allowed in the describingCodeSystem list. Unless specified otherwise in a specific call, the code system version with the tag "CURRENT" must be used. The entity URI, which is an ExternalURI if the entityReferenceType is NAMED_ENTITY and a LocalURI is the entityReferenceType is ANONYMOUS_ENTITY. A reference to specific version of a code system that contains assertions about a given entity, including the namespace and name by which the entity is referenced, an optional designation appropriate to the given usage context and an optional RenderingURI that references the full EntityDescription contained in the specific code system version. A reference to the code system version that describes the entity. A contextually appropriate designation for the entity derived from the \\ describingCodeSystemVersion. A RenderingURI that, if followed, will provide a full CTS₂ EntityDescription derived from the corresponding code system version. A list (set) of zero or more entity references A reference to an entity whose name and description is local to the containing code system and service. Information about anonymous entities cannot be shared between services or across code systems the local URI that identifies this entity within the context of the particular service A reference to an entity that is identified through a globally unique URI. a URI that identifies a unique entity in a global context The combination of a namespace identifier and a local name. Scoped entity names are not portable - they only work within the context of a single service instance, as different services may assign different namespace identifiers to the same namespace and different services may make different choices of the appropriate local identifier to use to represent an entity. As an example, one service may choose to use the entity code while a second may use another designation that is known to be unique. An identifier that references a unique namespace URI within the context of the service. The local entity name within the context of the namespace. What is chosen for the entity name is service specific The combination of a URI and/or and ScopedEntityName. The URI that uniquely references the target entity. A URI that resolves to the full EntityDescription represented by this resource An expression in a given ontology language and syntax that describes or defines an entity. Examples might include descriptions of entities in Manchester OWL Syntax, RDF, SNOMED Concept Expression, etc. An expression in a given ontology language and syntax that describes or defines an entity. Examples might include descriptions of entities in Manchester OWL Syntax, RDF, SNOMED Concept Expression, etc. The ontology language and syntax of the expression The actual expression A NameAndMeaningReference consists of local identifier that references a unique meaning within the context of a given domain in a CTS₂ service instance and a globally unique URI that identifies the intended meaning of the identifier. An ExternalURI that references the meaning of a name. Meaning is optional only because the meaning of some of the elements have not been fully specified in some legacy terminology resources. If meaning is not supplied, the intent of a reference cannot be shared among services or between other resources. A RenderingURI that, when dereferenced, results in a CTS₂ compliant representation of the meaning of the given NameAndMeaningReference. This must be present if the implementing CTS₂ service is aware of a CTS₂ resource that carries the definition. A reference to an entity that describes the role that a given value set binding plays for a concept domain. Typical values represent "overall", "minimum" or "maximum", the significance of which can be found in HL7 Version 3 documentation. A reference to an entity that describes significance of the case in term or designation. A reference to a code system. A reference to a specific version of code system and, if known, the code system which it is a version of. A reference to the code system that the version is a version of. Must be present if this information is known to the CTS₂ service implementation. A reference to a concept domain. A reference to a specific binding for a concept domain and, if known, the concept domain that it is a binding for. A reference to the concept domain associated with this binding. This must be present if this information is known to the implementing CTS₂ service references a spoken or written human language A reference to a map version and the corresponding map, if known. A reference to the corresponding map. Must be present if it is known the implementing CTS₂ service An EntityReference that serves the role of predicate. Note that this varies slightly from the base class of NameAndMeaningReference because the name attribute is a namespace/name combination rather than a simple name scoped exclusively by the domain. A reference to a value set definition and the corresponding value set if known A reference to the corresponding value set. Must be present if known to the implementing CTS₂ service General set operators that specify set union, difference or intersection in various contexts Include all members of both sets in the result Include only members common to both sets in the result Remove all members of the second set from the first set producing the result A collection of one or more filters. The result of applying a Filter component is the \emph{intersection} of the sets of qualifying elements. As an example, a filter having two components - one which says that the rights attribute must exist and a second that says that the text "SNOMED" must appear in the synopsis would return all resources having BOTH a rights attribute and "SNOMED" in the description. A restriction on an attribute, property or special field The algorithm to be used for testing the referenced component. Examples might include "starts with", "regular expression match", "exists", "inRange", etc. NOTE: The CTS₂ specification needs to establish a core set of match algorithms that all compliant implementations must support. .The value to be used in comparison. The structure and format of matchValue depends on the specific matchAlgorithm. As an example, a "startsWith" algorithm would be plain text, a "regularExpression" algorithm would have a regular expression while an "exists" algorithm would have nothing in the matchValue attribute. The particular attribute, property or special element to be sorted along with the sort direction The type and name of the attribute, property or special element to be sorted The sort order to be applied to the element. The collating order of a sort. Sort in ascending collation order. Sort in descending collation order. An ordered list of sort criterion. The first entry in the list identifies the primary sort order, the second entry the sub sort order, etc. Indicates whether an entity reference / predicate combination is to be evaluated with the entity reference in the source (left hand side) position of the association query or the target (right hand side or "object) position. The statement is to be resolved with the entity reference in the role of source. The statement is to be resolved with the entity reference in the role of target. A reference to a CTS₂ model element. PropertyReference may reference a model attribute, a Property or a special element such as match strength. The type of thing being referenced The possible types of property references. A reference to an element in a CTS₂ model such as formalName, designation, etc. A reference to a model Property. The reference target carries the name or URI of the property predicate. The target of the reference is a special element such as the match strength of a search. A local identifier for a CodeSystem A local identifier for a CodeSystemVersion A local identifier for a ConceptDomain. A local identifier for a Map A local identifier for a MapVersion A local identifier for a ValueSet A local identifier for a VersionTag Note corresponds to the target of skos:note. It contains an attributed literal that may include a language, format and, when appropriate, schema. The code system version, if any, that asserted the statement from which this not derives. The URI of the Statement from which this note was derived. This will only be present in services that support the Statement profile. The external statement identifier assigned to this note. Text or other representation that is intended to communicate the intended meaning of the associated entity to a human being. While this is intended to be very close in meaning to skos:definition, its intent is slightly different in that the CTS₂ specification does not treat definition as a subproperty of note - rather it views comments, examples and definitions as separate entities. The context(s) in which the definition is considered applicable The role that the definition plays with respect to the defined entity A Note about the history, scope or provenance of the containing element. Comment is differentiated from Example and Definition specifically because it is frequently searched and displayed under different circumstances and usage contexts. Example and Definition are frequently made available to the end users of a code system while Comments are typically consumed by authors and editors. A change note. See: skos:changeNote An example. See: skos:example An editorial note. See skos:editorialNote A history note. See: skos:historyNote A scope note. See: skos:scopeNote The role that a given definition plays for a given entity. the definition is considered to be official or normative by the assigning body The definition is considered to be of value, but not completely normative The language and syntax of an expression in an ontology. Language identifies the expression semantics (e.g. OWL 2.0, RDF, SNOMED Compositional Expression, etc) and syntax identifies how it is represnted (e.g. XML, text/plain, xml/rdf, manchester syntax, etc) The formal language (semantics) of the expression. The syntax of the expression. ResourceDescription represents the shared characteristics common to both abstract and resource version descriptions. ResourceDescription is an abstract type and, as such, cannot be directly created. Resource descriptions are Changeable, meaning that they have identity and can be created, updated and deleted. additional identifiers that are used to index and locatethe resource the class(es) that this resource instantiates A textual summary of the resource - what it is, what it is for, etc. references to documents that provide additional information about the resource the sources the participated in the creation, validation, review, dissemination of this resource and therole(s) they played Copyright and IP information. Note that rights applies to the source resource, not the CTS₂ rendering. an additional note or comment about the resource additional information about the resource that doesnot fit into any of the attributes described above An alternative identifier that uniquely names this resource in other environments as contexts. As an example, if a resource had both an ISO Object Identifier and a DNS name, the DNS name might be assigned as the entryID of the resource by one service while the ISO OID would be recorded as an alternateURI using the "urn:oid" prefix. Note that alternateIds can be added or removed during resource updates. A DirectoryURI that references the set of statements that were used to construct the containing resource. This attribute must (may?) be present if and only if the service supports the Statement profile The (or a) definitive URI that represents the resource being described. Note that this is NOT the URI of the resource description in the CTS2 format, but of the resource itself. As an example, the about URI for the Wine ontology would be "http://www.w3.org/TR/2003/PR-owl-guide-20031209/wine#". The NCI Thesaurus has, amongst others, the about URI of http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl#. HL7 uses ISO Object Identifiers (OIDs) to label resources so, from the HL7 perspective, the about URI of the NCI Thesaurus would be "urn:oid:2.16.840.1.113883.3.26.1.1" The formal or officially assigned name of this resource, if any The resource types that can be described in a CTS₂ service An ontology, classification scheme, thesaurus or code system. A specific release or version of an ontology, classification scheme, thesaurus or code system. A "data element concept" - a specification of the conceptual domain of an element in a database, form, message, etc. A set of rules for transforming a set of entity references into a second set of entity references, drawn from a different code system or value set. A specific version or release of a MAP A set of entity references. A set of rules for establishing which entity references belong to a value set at a given point in time. A DirectoryEntry that identifies the elements of a resource description that appear in every directory of resources of a particular type. ResourceDescriptionDirectoryEntry is an abstract type and is realized in the implementing subtypes listed in CTS2ResourceType A textual summary of the resource - what it is, what it is for, etc. The (or a) definitive URI that represents the resource being described. A local identifier that uniquely names the resource within the context of the describedResourceType and implementing service. The formal or officially assigned name of this resource. A summary of an abstract resource. A summary of a resource version. A label or identifier that was assigned to this version by its publisher Information about the source, format, release date, version identifier, etc. of a specific version of an abstract resource. A URI that identifies the specific version, language and notation of the about resource. documentation about the frequency and natureof releases (version) of this resource._{OMV 2.4.1 pp 18} a format and notation that thereleases (versions) of this resource is available in. Information about the source, format, release date, version identifier, etc. of a specific version of an abstract resource. A description of where the (or a) source of the version may be found, what format and language it is available in, etc. A reference to the name and URI version of the resource from which this current version is derived. The version of the resource that immediately preceded it. A label or identifier that was assigned to this version by its publisher. The date that this resource officially became available from the publishers. The date that this version of the resource is stated to be in effect by the publishers of the resource itself. A URI that identifies the specific version, language and notation of the about resource. This URI needs to be constructed in such a way that, if necessary, it will be possible to differentiate resource versions that were loaded from different document syntaxes. As an example, if an image of a the wine ontology was loaded from a resource that was in Manchester Syntax, it should be given a different URI than the image loaded from the RDF/XML syntax. The reasoning behind this is, even in cases where different syntaxes are 100% compatible, A description of the source from which the ResourceVersionDescription was derived. When possible, SourceAndNotation should include a reference to the actual source document from which it was derived. As an example, if the resource was derived from the W3C Wine Ontology, the URI http://www.w3.org/TR/2003/CR-owl-guide-20030818/wine would unambiguously name the document. In the cases, however, when a definitive source document is not available, a textual description should be provided, instead, in sourceAndNotationDescription. Where possible, the ontology language and ontology syntax should also be provided. In the case of the Wine Ontology above, the ontology language would be http://www.w3.org/2002/07/owl# (OWL) and the syntax would be application/rdf+xml. A textual description of where the specified resource version was derived from. This parameter must be supplied if a reasonable PersistentURI for the source document is not available. A persistent URI that references the document from which the resource version was derived. This URI may be resolvable to a digital resource or may be the name of a book, publication or other external document. The formal language, if any, that the source for the resource version is expressed in. Examples include Common Logic, OWL, OWL-DL, CLAML, etc. The syntax of the source of the resource version, if known. Examples might include rdf/xml, Turtle, Manchester Syntax, CSV, etc. The target of a Statement. StatementTarget represents one of a literal value, a reference to a non-entity type resource, an entity, or an anonymous blank BNODE. The URI and optional namespace/name when the target type is ENTITY The literal target when the statement type is LITERAL. The resource URI when the statement type is RESOURCE A collection of statements about an anonymous subject. An external identifier that has been assigned to the statement with this particular target by the authoring body. As an example, this would carry the SctId if the authoring body were SNOMED CT A statement lacking a named subject. the predicate of the anonymous statement the target of the anonymous statement Assertions whose subject is the statement itself, not the statement subject. A tag/value pair that does not have a corresponding model attribute. Property represent any statement about a resource (e.g. CodeSystem, Entity, etc.) that does not have a corresponding attribute in the CTS₂ model. As an example, the NCI Thesaurus uses a tag named \emph{BioCarta_ID} (C43677) to associate appropriate thesaurus entities with Bio Carta pathway references. This would be represented by a property, whose predicate is the URI for C436777 and the value is the actual id. The name and URI of the property predicate The target of the property. Note that this can only represent the literal format of the property. The details about the original property will be found in the correspondingStatement if the CTS₂ implementation supports the Statement profile. Assertions whose subject is the assertion in the property instead of the property subject. An identifier assigned to this property by an external source. As an example, properties that are asserted in SNOMED-CT would put the SCTID attribute in this field. A link to the original statement from which this Property is derived. Will only be present in CTS₂ implementations that support the Statement profile. Carries either a local identifier (name) or a URI (uri) that references a resource in the service. NameOrURI is only used as an input parameter and its type is always defined by the usage context. Note that service calls that use the name option may not be portable across implementations, as there is no guarantee that any two CTS₂ service implementations will use the same local identifiers for the same resources. Carries either a local identifier (name) or a URI (uri) that references a resource in the service. NameOrURI is only used as an input parameter and its type is always defined by the usage context. Note that service calls that use the name option may not be portable across implementations, as there is no guarantee that any two CTS₂ service implementations will use the same local identifiers for the same resources. a LocalIdentifier that references a unique resource within the context of the service implementation and type of resource being accessed an ExternalURI that references a unique resource within the context of the resource type A set of zero or more NameOrURI elements A reference to a class, property or individual that is described in some Code System. EntityNameOrURI may either reference an entity that is known locally to the service or an entity that is described elsewhere. If the entity is known to the service, it is possible to use the entityName variant, but note that neither scopingNamespace nor the entityName are guaranteed to be the same in different CTS₂ implementations. The entityName variant is intended for use in human/browser interactions and should not be hard-coded into data tables or applications. A reference to a class, property or individual that is described in some Code System. EntityNameOrURI may either reference an entity that is known locally to the service or an entity that is described elsewhere. If the entity is known to the service, it is possible to use the entityName variant, but note that neither scopingNamespace nor the entityName are guaranteed to be the same in different CTS₂ implementations. The entityName variant is intended for use in human/browser interactions and should not be hard-coded into data tables or applications. A combination of a namespace identifier and a local name that, together, uniquely references an entity known to the service An ExternalURI that references a class, property or individual A set of zero or more EntityNmeOrURI elements A return type that indicates a positive or negative answer to the specific question that was posed. A parameter used in queries where multiple elements are provided. It determines whether a candidate element must satisfy all restrictions or just one or more restriction in order to be considered as satisfying the restriction composite The candidate passes only if all of the elements are present The candidate passes if any of the supplied elements are present An indicator that determines whether the given service access request applies only to elements that are currently marked as ACTIVE in the context of the particular query or to both ACTIVE and INACTIVE entries. The inquiry only applies to ACTIVE elements. The inquiry applies to both ACTIVE and INACTIVE entries A parameter in a REST Resource PSM The header information for any REST resource retrieval PSM Message header that wraps all returns. PSM