The Emergency Care eDischarge Specification supports the following care communications:
Emergency Care eDischarge Summary Document – An ITK3 FHIR Document containing information supporting a discharge typically between a hospital emergency care department and a GP practice.
FHIR Messaging components specified within this site have been developed by NHS Digital and use some of the 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 UK health and social care.
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.
The latest version of the PRSB documentation should be consulted for further information regarding Section headings and content http://theprsb.org
Using this guide
This guide has been created to support the adoption of NHS Digital defined FHIR Messages. As such the site is structured around stakeholders involved in building FHIR ITK3 Messaging Solutions including ITK3 Messaging Solution users, developers and architects.
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.