A brief introduction to getting started with the ITK3 eDischarge.

Introduction

The Transfer of Care eDischarge Specification supports the following care communications:

eDischarge (inpatient discharge summary) Document – An ITK3 FHIR Document containing Transfer of Care information supporting an inpatient discharge typically between an acute hospital and GP practice.

FHIR Messaging components specified within this site have been developed by NHS Digital and use CareConnect profiles created in collaboration with the INTEROPen community.

The INTEROPen vision is to create a library of nationally defined HL7® FHIR® resources and interaction patterns that implementers can adopt to simplify integration and interoperability within England’s health and social care systems.

Find out more on the INTEROPen website.

This documentation provides a FHIR document implementation of the work done by the Academy of Medical Royal Colleges (AoMRC) in defining headings for clinical documents.

Using this guide

This guide has been created to support the adoption of NHS Digital defined FHIR Messages. This site has been developed with input from stakeholders such as ITK3 Messaging Solution users, developers and architects.

Definitions

The keywords MUST, MAY, and SHOULD are to be interpreted as described in RFC2119:

  • MUST: This word, or the terms “REQUIRED” or “SHALL”, means that the definition is an absolute requirement of the specification.
  • MUST NOT: This phrase, or the phrase “SHALL NOT”, mean that the definition is an absolute prohibition of the specification.
  • SHOULD: This word, or the adjective “RECOMMENDED”, means that there May exist valid reasons in particular circumstances to ignore a particular item, but the full implications Must be understood and carefully weighed before choosing a different course.
  • SHOULD NOT: This phrase, or the phrase “NOT RECOMMENDED” mean that there May exist valid reasons in particular circumstances when the particular behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label.
Tags: overview