Library

Browse and search developer information

ciao Integration: eDischarge (Transfer of Care)

HSCIC | 18 June 2015

The first user story that was prioritised by the ciao business ambassadors for delivery in ciao was around transfer of care:

User Story: CIAO001EUS – Transmit ‘Transfer of Care’ documents

  • As a Trust,
  • I want to use CIAO to integrate with other providers (and departments)
  • So that I can transmit ‘transfer of care’ documents, e.g. a discharge summary sent to Primary care.

The main goal that lies behind this high level story is providing timely information to improve patient care for patients who have had a hospital encounter. By evaluating this, we can identify some key stakeholders, and some capabilities that would be needed in order to deliver this goal:

ImprovePatientCare

During the development of this ciao integration, each of these capabilities will be evaluated, and where ciao can deliver specific features that deliver the capabilities, these will be incorporated into the CIPs that are developed.

A key initial focus on the development to-date has been on the first capability listed above – i.e. “Take information from my eDischarge system and send it to the GP electronically”.

This has been broken down into some more granular features which could be delivered within the ciao integration and it’s constituent CIPs:

SendeDischargeIn the course of development, these features will be elaborated in more detail, with some supporting scenarios/acceptance criteria.

Implementation Details

The current approach for delivering this ciao integration is a collection of CIPs as shown in the below diagram – all of which are now available in our Github repository:

TransferOfCare

The light blue boxes show the individual CIPs, which can be composed together in a range of ways to suit the needs of the local implementation.

The main input into the ciao integration is a discharge summary document generated from a local clinical system. The ciao-docs-parser CIP can pick these documents up, parse out any content that can be sensibly and safely extracted, if necessary “enrich” that information with other information (either static information about the local trust or department, or information from other local data sources – and in future national sources such as PDS), convert the information into a structured CDA document (in line with nationally defined “transfer of care” standards), and send the generated document to the GP via the Spine (or other routes such as ITK web services).