Maptype

Overview

Terminologies utilise various types of mappings eg SAME AS, NARROWER THAN etc to describe relationships to each other. Both interface and reference terminologies relate to each other using these mapping types. The API exposes a representation of maptype which is normalized across sources.

URI : /rest/maptype

Core Properties

uuid
url
display
displayLocale
retired
properties
auditInfo
resourceVersion

names            # Synonyms, abbreviations, etc.
descriptions
sources          # Indicates sources in which mapType is used

Representations

GET ref	GET Default	GET full	POST create	POST update
uuid url display	uuid url display displayLocale names descriptions sources retired isHidden properties links resourceVersion	uuid url display displayLocale names descriptions sources retired isHidden properties links resourceVersion auditInfo	name description	name description

URIs

URL	Description	Response Code
GET /rest/maptype	Get/search active maptypes	OK / Success Not Found
GET /rest/maptype/?source={source}	Get/search maptypes in the specified source	OK / Success Not Found
GET /rest/maptype/{uuid}	Fetch the specified maptype	OK / Success Not Found
POST /rest/maptype/	Creates a new maptype The message must have a name as a minimum	OK / Success Not Found Duplicate
PUT /rest/maptype/{uuid}	Updates an existing maptype	OK / Success Not Found
DELETE /rest/maptype/{uuid}?!purge	Retire/Void a maptype specified by the uid	OK / Success Not Found
DELETE /rest/maptype/{uuid}?purge	Delete a maptype specified by the uid	OK / Success Not Found

Output Samples

{
    "__type__": "OclMapType",

    "uuid": "35543629-7d8c-11e1-909d-c80aa9edcf4e",
    "url": "/rest/maptype/35543629-7d8c-11e1-909d-c80aa9edcf4e",
    "display": "SAME AS",
    "displayLocale": "en",
    "retired": "false",
    "properties": {
    	"omrsVersion": "1.9"
    },
    "auditInfo": {
        "creator": "admin",
        "dateCreated": "2005-02-17T00:00:00.000+0300",
        "changedBy": null,
        "dateChanged": null
    },
    "resourceVersion": "1.9",

    "names": [
        {
            "name": "SAME AS",
            "locale": "en",
            "preferred": true
        }
    ],
    "descriptions": [
        {
            "description": "equal to",
            "locale": "en",
            "preferred": true
        }
    ],
    "sources": [
    	"ciel",
    	"pih"
    ]
}

Normalization across sources

SNOMED CT provides a mechanism for mapping concepts to other terminologies and classifications. This mapping mechanism consists of three tables: Cross Map Sets Table, Cross Maps Table and Cross Map Targets Table. A Relationship is an association between two Concepts. The nature of the association is indicated by a Relationship Type. Each Relationship is represented by a row in the Relationships Table.

The nature of a Relationship between two Concepts is referred to as the relationship type. The RelationshipType field indicates the ConceptID for the concept in SNOMED that forms the relationship between two other concepts (ConceptID1 and ConceptID2) SNOMED CT has four types of relationships:

• Defining characteristics are IS_A relationships and defining attributes.
Example: “PROCEDURE-SITE = Liver” is a defining characteristic of Liver biopsy.
• Qualifying characteristics are non-defining, qualifying attributes.
• Historical relationships relate inactive concepts to active concepts. For example, a concept may be inactivated because it is a duplicate. In this example a relationship is created when one concept is inactivated and stated to be the “same-as” another concept.
• Additional relationships are other non-defining characteristics, like PART OF which is retained for backward compatibility with SNOMED RT.

No maptype information was obtained for LOINC and ICD10 to contribute to the API design

These datatypes are already normalized within the OCL adopted model of the various maptypes