Encounter Report Interaction
When an EMS reaches the end of operations, it can hand over the journey to a different EMS or appropriate Healthcare Service.
Notify
The HealthcareService is notified of an Encounter Report by the EMS calling the HealthcareService.endpoint and passing the Encounter ID.
The Encounter Report Receiver (ERR) can also query known endpoints based on patient details such as the NHS Number to find a relevant Encounter. The ERR can then fetch the Encounter Report based on the Encounter.
Structure
The base resource for the Encounter Report is the Encounter. The Encounter will link to a Patient (through Encounter.subject).
The Encounter has a history of the triage journey as a List (linked by List.encounter). The List is composed of assertions (normally Observations), QuestionnaireResponses (which will in turn link to Questionnaires) and CarePlans presented during the journey. If the journey concluded with a ReferralRequest for a type of service, this will be part of the List.
There are a number of supporting resources which are linked from these core resources, or are searchable by encounter (detailed below). Conceptually, these are all part of the Encounter Report as they may be necessary to interpret the patient journey through UEC.
Retrieving the Encounter Report
An Encounter Report can be composed by the ERR after receiving just the Encounter.
The server which ‘owns’ the Encounter must be able to resolve a search request for the List, ReferralRequest, Observation, Condition, CarePlan, Flag, Appointment, Composition or Task resources, based on the Encounter identifier.
Resources in the Encounter Report
The resources presented in the List will follow the guidance in the Evaluate interaction exactly, so full details are not re-presented here. Each resource which is expected to be part of a report is identified below:
| Resource | Linked by | Guidance |
|---|---|---|
| Appointment | Appointment. |
Used to represent an appointment for the UEC patient. |
| CarePlan | CarePlan. |
Used to carry the care advice recommendation given by the CDSS. |
| Composition | Composition. |
Used to represent a human-readable summary of the triage journey for a patient. |
| Condition | Condition. |
Used to carry the chief concern and any secondary concerns which reflect the outcome of triage. |
| List | List. |
Used to represent represent a summary of the triage journey for a patient, including all resources collected during the triage process i.e.:
List per Encounter, for example, where a CDS is managing multiple ServiceDefinition interactions with the EMS for the same patient at the same time.
|
| Consent | Linked to the triage journey by patient and data. |
Patient consent of different types can be carried in a Consent object. This includes Permission To View (PTV) and authorisation as per the 111 Report, but can be extended to any type of consent granted (or withheld) by the patient.
|
| Encounter |
Used to represent represent a summary of the triage encounter.
The patient and practitioner will be CareConnect profiles, and will follow the rules for those profiles |
|
| Flag | Flag. |
Used to carry information about a patient that is not a clinical assertion e.g. Scene Safety, transport requirements, accessibility requirements, patient preferences and reasonable adjustments. |
| HealthcareService | ReferralRequest. |
Once a provider organisation is selected from a directory, the instance is populated as a HealthcareService
|
| Patient | Encounter. |
Used to carry details about an individual receiving care or other health-related services. |
| Practitioner |
Encounter.Patient.
|
Used to represent a person who is directly involved in the provision of healthcare (e.g. physician, dentist, pharmacist, nurse, paramedic etc). |
| ReferralRequest | ReferralRequest. |
The ReferralRequest at handover contains directions to an actual service to which the patient has been referred.
This will include a specific HealthcareService, and may include an Appointment.
|
| RelatedPerson | Encounter. |
Used to convey information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. |
| Task | Task. |
Identifies the next action to be taken, and who is responsible for that action. Tasks belong to the Encounter.
There may be a Task at the end of triage for a professional to carry out. The Task will not be populated where the Encounter Report is for information only (e.g. report to registered GP, or to RCS)
|
