Looking for help?
-
Introduction
-
HIE Components
-
-
Developers Guide
-
System Integration
-
User Workflows
-
Release Notes
-
Implementer's Guide
< All Topics
Print
Concept API
Posted
Updated
Byadmin
The purpose of concept api is to fetch details of concept in context.
The API is based on REST convention and would use JSON format for exchange of data.
This API needs Basic Authentication.
The username and passwords will be of a user created in TR system with role TR API CONSUMER.
Request
GET http://{{tr_server}}/openmrs/ws/rest/v1/tr/concepts/{{identifier}}
Authorization
Username
Password
Response
{ "uuid" : "d6971a0c-82f3-11e5-b875-0050568225ca" , "version" : "0.1" , "datatypeName" : "N/A" , "conceptClass" : "Symptom/Finding" , "retireReason" : null , "fullySpecifiedName" : { "conceptName" : "Vomiting" , "conceptNameType" : "FULLY_SPECIFIED" , "locale" : "en" , "preferred" : true }, "names" : [ { "conceptName" : "Vomiting" , "conceptNameType" : "FULLY_SPECIFIED" , "locale" : "en" , "preferred" : true }, { "conceptName" : "Vomiting" , "conceptNameType" : "SHORT" , "locale" : "en" , "preferred" : false } ], "referenceTerms" : [], "description" : null , "setMembers" : [], "properties" : {}, "conceptAnswers" : [], "set" : false , "retired" : false } |
Table of Contents