This resource contains details and outcomes for a patient encounter, which can include one or more providers, locations, and services. Encounters can encompass preadmission, outpatient visits, telehealth visits, inpatient stays, and discharges, depending on the organization and context for the encounter. Encounters can contain references to procedures if a procedure was completed during a patient visit or if a follow-up procedure is scheduled as a result of the encounter.
You can receive or retrieve encounter details.
cURL request example
Request Body Schema
- resourceTyperequired, string
Identifies the type of the resource
Value:Bundle
- typerequired, string
Identifies this bundle as a message
Value:message
- entryrequired, Array of MessageHeader, Encounter, Patient or Other
An array of FHIR resources. At a minimum, an Encounter should include the following entries:
- Patient - the patient
- Encounter - the encounter related to the patient
- resourcerequired, object
Additional metadata about the message including the event
- resourceTyperequired, string
Identifies the type of the resource
Value:MessageHeader
- sourcerequired, object
Information about the sender of the message. This will typically be populated by Redox.
- endpointrequired, string
Identifies the routing target to send acknowledgements to.
- namestring
Human-readable name for the source system.
- eventCodingrequired, object
This describes the message being communicated
- systemstring
The identification of the code system that defines the meaning of the symbol in the code.
- codestring
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Value:Encounter-New
An entry in the bundle containing a FHIR resource
- timestampstring
The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle.