Skip to main content

Encounter

Overview

The Encounter resource provides "an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient." This resource captures the details of healthcare encounters including visits, appointments, and other interactions between patients and healthcare providers.

Resource Schema

Key fields in the Encounter resource:

{
"resourceType": "Encounter",
"id": "example-encounter",
"status": "finished",
"class": {
"system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
"code": "AMB",
"display": "ambulatory"
},
"subject": {
"reference": "Patient/123"
},
"period": {
"start": "2023-01-15T10:00:00Z",
"end": "2023-01-15T11:00:00Z"
},
"participant": [{
"individual": {
"reference": "Practitioner/456"
}
}]
}

Operations

The Encounter resource supports the following operations:

CareRecord / SolutionCreateReadUpdateSearch
GEHRIMED-Yes-Yes
myAvatar-Yes-Yes
myEvolv-Yes-Yes
myUnity-Yes-Yes
TheraOffice-Yes-Yes

Search for encounters using various criteria.

GET Method

Use GET for simple searches with parameters in the query string.

GET /Encounter?parameter=value

POST Method

Use POST for complex searches with form-encoded parameters.

POST /Encounter/_search

Search Parameters

Patient-based Search:

ParameterTypeRequiredDescriptionExample
patientreferenceYesThe patient or group present at the encounterpatient=value
datedateNoA date within the period the Encounter lasteddate=value
statustokenNoplannedstatus=value
_lastUpdateddateNoOnly return resources which were last updated as specified by the given range_lastUpdated=value

ID-based Search:

ParameterTypeRequiredDescriptionExample
_idstringYesThe ID of the resource_id=value
_lastUpdateddateNoOnly return resources which were last updated as specified by the given range_lastUpdated=value

Examples

Search by Patient and Date

curl -X POST https://fhir.netsmartcloud.com/provider/patient-access/v2/{tenant-id}/Encounter/_search \
-H "Authorization: {Bearer Token}" \
-H "Accept: application/fhir+json" \
-H "Content-Type: application/x-form-urlencoded" \
-d "patient=Patient/123" \
-d "date=ge2023-07-10"

Integration Patterns

Common workflows involving Encounter:

  • Visit History: Retrieve patient encounter history for care coordination
  • Encounter Status Tracking: Monitor encounter status changes
  • Care Episode Management: Link related encounters and services

Related resources: Patient, Practitioner, Organization, Location, Condition

Error Handling

For error responses and troubleshooting, see the Error Handling Guide.

Supported Profiles

This API supports the following FHIR profiles: