Skip to main content

Transfer of Care Inpatient Discharge - FHIR

Create and transmit documents containing Transfer of Care information supporting an inpatient discharge.

Overview

Inpatient or day case system
Inpatient or day cas...
MESH
MESH
GP system
GP system
send patient discharge summary
send patient dischar...
receive patient discharge summary
receive patient disc...
Text is not SVG - cannot display Context diagram showing how the Transfer of Care Inpatient Discharge FHIR is used.

 

Use this integration to create and transmit documents containing Transfer of Care information supporting an inpatient and day case discharge.

An Inpatient and Day Case Discharge Summary Document (also known as an ITK3 eDischarge) is an ITK3 FHIR document containing Transfer of Care information supporting inpatient and day case discharges typically between an acute hospital and a GP practice.

For example, a patient attends hospital for elective hip replacement surgery and is discharged by her consultant after a couple of days. The consultant completes and sends an eDischarge document to her GP.

This integration uses MESH to send and receive messages. It is part of a suite of Transfer of Care FHIR message specifications.

Before you begin any development work using this integration, contact us to discuss your best options.

For a non-technical overview of how to build software that deals with referrals and bookings, see Building healthcare software - referrals and bookings.


Status

This integration is in production.


Service level

This integration uses MESH which is a silver service,  meaning it is operational 24 hours a day, 365 days a year but only supported during business hours (8am to 6pm), Monday to Friday excluding bank holidays.

For more details, see service levels.


Technology

This integration uses MESH to send and receive messages.

It uses the following MESH workflow IDs:

  • TOC_FHIR_IP_DISCH
  • TOC_FHIR_IP_DISCH_ACK

The message payload conforms to the FHIR global standard for health care data exchange. Specifically, it conforms to FHIR STU3 and to our ITK3 Messaging Distribution standard.


Interactions

For details of the interactions for this integration, see Transfer of Care message specifications.

For details on the general structure of the interactions, see FHIR.

Last edited: 14 September 2023 5:51 pm