1 Overview

"Summary Care Record Phase 4 Implementation" uses replacement only. This domain details generic documents used to nullify documents sent by other CDA domains.

Note :- Nullification documents are only used where is not possible to use the normal replacement mechanism because no correcting document is available. Further details of the normal replacement mechanism is contained within each CDA domain.

Some types of information require the use of CRE-types whereas others prohibit the use of CRE-types - refer to the Implementation Guidance for Suppliers or PSIS Integration Strategy documents for the recommended use of CRE-types.

The CRE Section holds a list of ID's which are associated with the coded entries. The coded entries have a <reference> to the <content> in a text section which allows linking therefore enabling indirect association with a CRE-type. Refer to the latest version of "NPFIT-ELIBR-AREL-P1R2-0178 Technical Guidance for Implementation of Templated CDA Domains" for further information on how sections and entries are linked with text.

1.1 Domain Compliancy Statement

This CDA domain document utilised within this domain complies with the conformance statement from "HL7 Clinical Document Architecture, Release 2.0" (2006 Normative Edition), namely :

"A conformant CDA document is one that at a minimum validates against the CDA Schema, and that restricts its use of coded vocabulary to values allowable within the specified vocabulary domains."

This CDA specifications described in this domain makes use of a templating mechanism that supports both entry-level and section-level templating. NHS CFH have implemented the HL7 guidelines for CDA and have included localisations to aid the navigation of the CDA document.

In the absence of any other machine enforceable templating constraint mechanism the NHS CFH approach is being pre-adopted.

1.2 Use of templates

This domain uses templates, for further information on templates refer to the latest version of "NPFIT-ELIBR-AREL-P1R2-0178 Technical Guidance for Implementation of Templated CDA Domains"

2 Application Roles

The relevant Application Roles used for Nullification are contained within each CDA domain.

3 Trigger Events

The relevant Trigger Events used for Nullification are contained within each CDA domain.

4 Interactions

The relevant Interactions are used for Nullification are contained within each CDA domain..

5 Message Definitions

5.1 Nullification Document - POCD_MT130001UK05

The Nullification Document is designed to be used by CDA domains. It provides functionality for marking documents as nullified (withdrawn).