Retrieve Demographics for a Subject Identifier
get
/HSDataService-web/api/3.2.0/subjectapi/subjects/{id}
This endpoint supports the retrieval of Demographics for a Subject Identifier. It returns Subject information like Human Name, Telecom, Address and other Subject associated information.
Request
Supported Media Types
- application/json
- application/xml
Path Parameters
- id
-
Type:
integer(int64)Required:trueSubject Identifier
Response
Supported Media Types
- application/json
- application/xml
200 Response
successful operation
Body
Root Schema : Subject
Type:
object- address
-
Type:
objectAddressModel for a postal address. - birthDate
-
Type:
string(date-time)Date of Birth - deceasedBoolean
-
Type:
booleanDefault Value:falseDeceased or Not - deceasedDate
-
Type:
string(date-time)Deceased Date - endDate
-
Type:
string(date-time)Enrollment End Date - enrollmentDate
-
Type:
string(date-time)Enrollment Date - ethnicity
-
Type:
objectLinkedReference - gender
-
Type:
objectCodeableConceptModel that represents a value as a reference to one or more terminologies or ontologies or defined by the provision of text. - identifiers
-
Type:
arrayidentifiersSpecimen Identifier - maritalStatus
-
Type:
objectCodeableConceptModel that represents a value as a reference to one or more terminologies or ontologies or defined by the provision of text. - name
-
Type:
objectHumanNameModel for a name of a human with text and parts information. - patient
-
Type:
objectLinkedReference - patientIdentifier
-
Type:
stringPatient Identifier - race
-
Type:
objectLinkedReference - startDate
-
Type:
string(date-time)Enrollment Start Date - studyIdentifier
-
Type:
stringStudy Identifier - studyName
-
Type:
stringStudy Name - telecom
-
Type:
objectTelecom
Nested Schema : Address
Type:
objectModel for a postal address.
- city
-
Type:
stringName of city, town etc. - country
-
Type:
objectCodeableConceptModel that represents a value as a reference to one or more terminologies or ontologies or defined by the provision of text. - district
-
Type:
stringDistrict name (aka county). - line
-
Type:
arraylineStreet name, number, direction & P.O. Box etc. - postalCode
-
Type:
stringPostal code for area. - state
-
Type:
objectCodeableConceptModel that represents a value as a reference to one or more terminologies or ontologies or defined by the provision of text.
Nested Schema : LinkedReference
Type:
object- display
-
Type:
string - reference
-
Type:
string
Nested Schema : CodeableConcept
Type:
objectModel that represents a value as a reference to one or more terminologies or ontologies or defined by the provision of text.
- coding
-
Type:
arraycodingRead Only:trueCode(s) defined by a terminology system. - text
-
Type:
stringPlain text representation of the concept.
Nested Schema : identifiers
Nested Schema : HumanName
Type:
objectModel for a name of a human with text and parts information.
- family
-
Type:
stringFamily name (often called 'Surname'). - given
-
Type:
arraygivenGiven names (not always 'first'). Includes middle names. - text
-
Type:
stringText representation of the full name.
Nested Schema : Telecom
Type:
object- use
-
Type:
objectCodeableConceptModel that represents a value as a reference to one or more terminologies or ontologies or defined by the provision of text. - value
-
Type:
stringTelecom Value
Nested Schema : line
Nested Schema : coding
Nested Schema : Coding
Type:
objectModel for a reference to a code defined by a terminology system.
- code
-
Type:
stringSymbol in syntax defined by the system. - description
-
Type:
stringDescription defined by the system. - display
-
Type:
stringRepresentation defined by the system. - sysId
-
Type:
stringIdentity of the terminology system. - sysName
-
Type:
stringName of the terminology system. - sysVersion
-
Type:
stringVersion of the system - if relevant.
Nested Schema : Identifier
Type:
objectIdentifier assigned by a given system
- system
-
Type:
stringSystem which assigned this identifier - value
-
Type:
stringIdentifier value
Nested Schema : given
400 Response
Invalid parameters supplied
404 Response
Subject(s) not found
Examples
The following example submits a GET request.
API URL
http://localhost:700l/HSDataService-web/api/3.2.0/subjectapi/subjects/1
Example of Response Body
The following example shows the response returned in JSON format.
{
"identifiers":
[
{
"system": "CDM",
"value": "1"
},
{
"system": "Customer Defined",
"value": "S1_1"
}
],
"studyName": "STUDY1",
"studyIdentifier": "1",
"patientIdentifier": "P2_2",
"patient":
{
"reference": "/HSDataService-web/api/3.2.0/subjectapi/subjects/1/patients"
},
"name":
{
"text": "Juan MN1 Hernandez",
"family": "Hernandez",
"given":
[
"Juan",
"MN1"
]
},
"telecom":
{
"value": "info@oracle.com",
"use":
{
"coding":
[
{
"code": "CNTCT_INFO_SUBTYP_EML",
"display": "Email",
"description": "Communicate electronically on the computer",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
}
},
"gender":
{
"coding":
[
{
"code": "1",
"display": "Male",
"description": "Male",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
},
"birthDate": "01/01/1945",
"deceasedBoolean": false,
"maritalStatus":
{
"coding":
[
{
"code": "1",
"display": "Married",
"description": "Married",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
},
"address":
{
"line":
[
"SADD11",
"SADD21",
"SADD31"
],
"city": "C1",
"district": "C1",
"state":
{
"coding":
[
{
"code": "1",
"display": "State1",
"description": "State1Desc",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
},
"postalCode": "Z1",
"country":
{
"coding":
[
{
"code": "1",
"display": "USA",
"description": "United state of America",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
}
},
"race":
{
"reference": "/HSDataService-web/api/3.2.0/subjectapi/subjects/1/race"
},
"ethnicity":
{
"reference": "/HSDataService-web/api/3.2.0/subjectapi/subjects/1/ethnicity"
}
}