-
Key: CTS2F2-37
-
Legacy Issue Number: 17118
-
Status: closed
-
Source: Mayo Clinic ( Mr. Craig Stancl)
-
Summary:
ResolvedValueSet needs two additional service entries - a read service that carries:
read (by RVS URI)
resolveAsEntityDirectory
resolveAsCompleteSet
(Same methods as the ValueSetResolutionService except that the argument is a single ResolvedValueSetURI)
and a simple query service that carries:
contains(resolvedSet, EntityNameOrURIList (move from loader)
resolvedSetsFor(EntityNameOrURI, ...) -> tells which resolved sets carry the entity
Logged: https://github.com/cts2/cts2-specification/issues/40
-
Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
-
Disposition: Resolved — CTS2 1.0
-
Disposition Summary:
PIM:
1. Introduce a new type - 'IterableResolvedValueSet' - and change the 'ResolvedValueSetDirectoryEntry' to be a subtype of 'ResolvedValueSetSummary.'
2. Added a new service, 'ResolvedValueSetResolution' Service, which follows the same general resolution patterns as 'ValueSetDefinitionResolution' service. The 'contains' method is moved from 'ResolvedValueSetLoader' to this new 'ResolvedValueSetResolution' service.3. Add a new type of DirectoryURI, "ResolvedValueSetDirectoryURI.
4. In order to query for 'ResolvedValueSets', a new service - 'ResolvedValueSetQuery' Service was added
PSM:
Added an 'IterableResolvedValueSet' type. -
Updated: Fri, 6 Mar 2015 20:58 GMT
CTS2F2 — ResolvedValueSetReadService and QueryService omitted from spec
- Key: CTS2F2-37
- OMG Task Force: Common Terminology Services 2 (CTS2) FTF