Retrieve Clinical Encounters for a Patient Identifier
get
/HSDataService-web/api/3.2.0/patientapi/patients/{id}/encounters
This endpoint supports the retrieval of Clinical Encounters for a single Patient Identifier passed. It returns Clinical Encounter information like Type, Encounter Number, Location and other Clinical Encounter associated information.
Request
Supported Media Types
- application/json
- application/xml
Path Parameters
- id
-
Type:
integer(int64)Required:truePatient Row ID
Query Parameters
- limit
-
Type:
integer(int32)Pagination query params: ?limit=2&offset=0- offset
Type:integer(int32)Pagination query params: ?limit=2&offset=0
Response
Supported Media Types
- application/json
- application/xml
200 Response
successful operation
Body
Model for paginated collections of data.
Root Schema : PageableCollectionClinicalEncounter
Type:
objectModel for paginated collections of data.
- count
-
Type:
integer(int64)Number of objects in the 'items' collection. - hasMore
-
Type:
booleanDefault Value:falseA boolean indicating if more pages are available. - items
-
Type:
arrayitemsA collection of paged items. - links
-
Type:
arraylinksA collection of links containing hrefs to the current, next, and previous pages as applicable. - resourceType
-
Type:
stringIdentify the resource type
Nested Schema : items
Type:
arrayA collection of paged items.
-
Type:
objectClinicalEncounterModel for a clinical encounter object in CDM.
Nested Schema : links
Nested Schema : ClinicalEncounter
Type:
objectModel for a clinical encounter object in CDM.
- encounterNumber
-
Type:
stringEncounter Number - identifier
-
Type:
objectIdentifierIdentifier assigned by a given system - location
-
Type:
objectLocation - patient
-
Type:
objectLinkedReference - period
-
Type:
objectDateRange - type
-
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 : Identifier
Type:
objectIdentifier assigned by a given system
- system
-
Type:
stringSystem which assigned this identifier - value
-
Type:
stringIdentifier value
Nested Schema : Location
Type:
object- identifier
-
Type:
objectCdmIdentifierIdentifier assigned by a given system - name
-
Type:
stringName of the facility. - type
-
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 : DateRange
Type:
object- end
-
Type:
string(date-time) - start
-
Type:
string(date-time)
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 : CdmIdentifier
Type:
objectIdentifier assigned by a given system
- system
-
Type:
stringSystem which assigned this identifier - value
-
Type:
stringIdentifier value
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.
400 Response
Invalid parameters supplied
404 Response
Encounter(s) not found
Examples
The following example submits a GET request.
API URL
http://localhost:7001/HSDataService-web/api/3.2.0/patientapi/patients/1/encounters?limit=2&offset=0
Example of Response Body
The following example shows the response returned in JSON format.
{
"resourceType": "Encounter",
"items": [
{
"identifier": {
"system": "CDM",
"value": "1"
},
"type": {
"coding": [
{
"code": "1",
"display": "ENC_TYPE1",
"description": "ENC_TYPE_DESC1",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
},
"location": {
"identifier": {
"system": "CDM",
"value": "1"
},
"name": "FAC1",
"type": {
"coding": [
{
"code": "FAC_SUBTYP_RM",
"display": "Room",
"description": "A space allocated for a function within a building or a floor",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
}
},
"patient": {
"reference": "/HSDataService-web/api/3.2.0/patientapi/patients/1"
},
"period": {
"start": "01/01/1998",
"end": "12/01/1998"
},
"encounterNumber": "ENC1"
},
{
"identifier": {
"system": "CDM",
"value": "2"
},
"type": {
"coding": [
{
"code": "1",
"display": "ENC_TYPE1",
"description": "ENC_TYPE_DESC1",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
},
"location": {
"identifier": {
"system": "CDM",
"value": "1"
},
"name": "FAC1",
"type": {
"coding": [
{
"code": "FAC_SUBTYP_RM",
"display": "Room",
"description": "A space allocated for a function within a building or a floor",
"sysId": "EHA_CUSTOM_CD_SYS",
"sysName": "EHA Custom Code System",
"sysVersion": "1"
}
]
}
},
"patient": {
"reference": "/HSDataService-web/api/3.2.0/patientapi/patients/1"
},
"period": {
"start": "01/01/1998",
"end": "12/01/1998"
},
"encounterNumber": "ENC1"
}
],
"count": 2,
"hasMore": true,
"links": [
{
"rel": "self",
"href": "http://localhost:7001/HSDataService-web/api/3.2.0/patientapi/patients/1/encounters?limit=2&offset=0"
},
{
"rel": "next",
"href": "http://localhost:7001/HSDataService-web/api/3.2.0/patientapi/patients/1/encounters?offset=2&limit=2"
}
]
}