1 / 10

Map Data in CTS II

Map Data in CTS II. Davera Gabriel, RN Stuart Turner, DVM University of California, Davis. Map Data Requirements. Data construct which relates the member of one code system, terminology, ontology or data instance to another.  Standard Content management functions

willa-mack
Download Presentation

Map Data in CTS II

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Map Data in CTS II Davera Gabriel, RN Stuart Turner, DVM University of California, Davis

  2. Map Data Requirements • Data construct which relates the member of one code system, terminology, ontology or data instance to another.  • Standard Content management functions • Creation / authoring information • Versioning • Formal standard or implementation instance • Metadata of map, not enumeration of all instances

  3. Gross Anatomy Target Source Target Source Target

  4. Storyboard 1: Map update A new set of mapping files comes with the versioned release of a terminology. The terminology manager needs to load and validate that the new version of map data is available on the Terminology Server. The new maps as well as the old maps reside on the system. Both can be accessed / viewed.

  5. Storyboard 3: Browse available maps A content analyst responds to a request for creation of maps from one system to another. The analyst requires a viewer to metadata about the maps currently available on the Terminology Server to determine if the creation of a new map set is required.

  6. Storyboard 3: Available map content export A new set of maps has been requested. A content analyst reviews the currently available maps on the terminology server to be able to determine whether a current map will suffice the need, or whether a new set of maps must be developed. A new set of maps needs to be developed. Information about available maps ois exported to a Map editing system

  7. Storyboard 4: Map permissions A new set of mapping files is made available through a data sharing agreement with another organization. These maps are similar to, but not identical to a map set that resides on the Terminology Server. The new maps are uniquely identified and made available only to those organizations that have rights to view the maps data.

  8. Storyboard 5: Map deprecation A content analyst determines that a set of maps is no longer valid or needed. Information about these maps persist in the system, but it is no longer available for use.

  9. Storyboard 6: Harvest Table Metadata A content analyst receives a request for data from two databases. The analyst selects the appropriate map from the Terminology Server to fulfill the data request. This gets passed along to the respective, external dBms’ as a queries. The external systems retrieve the requested harvest tables per the parameters specified in the maps. Harvest table metadata is recorded in the Terminology Server and persists for future reference.

More Related