Introduction

1. This guidance explains the circumstances under which Hospital Provider Spells should close and reopen as a result of a merger or demerger, in terms of NHS data standards. It specifies which codes should be used for those Hospital Provider Spells which must be closed and reopened,
   • for DISCHARGE DESTINATION etc, for the closing Hospital Provider Spell and
   • for SOURCE OF ADMISSION etc, for the new Hospital Provider Spell.

   Note that the NHS-wide Clearing Service (NWCS) has also issued Guidance Note NWCS/GN-003 which explains the use of NWCS Exchange Protocols when NHS Trusts merge.

2. This guidance explains the circumstances under which Hospital Provider Spells should close and reopen as a result of a merger or demerger, in terms of NHS data standards. It specifies which codes should be used for those Hospital Provider Spells which must be closed and reopened,
   • for DISCHARGE DESTINATION etc, for the closing Hospital Provider Spell and
   • for SOURCE OF ADMISSION etc, for the new Hospital Provider Spell.

When Hospital Provider Spells Should be Closed and Reopened

2. A Hospital Provider Spell is provided by one ORGANISATION acting as a Health Care Provider. This means that the spell is linked to the ORGANISATION CODE of the provider. If the ORGANISATION CODE changes, the spell must end and another begin with the new ORGANISATION CODE. If the spell does end, the Consultant Episode (Hospital Provider) within the spell must also end.

   The following scenarios explain what this means in terms of NHS Trust mergers or demergers. Note that these assume that nothing changes other than the fact that the NHS Trusts merge or demerge, e.g. the CONSULTANT stays the same, etc.

Mergers

Demergers

The Codes Used when Hospital Provider Spells are Closed and Reopened

3. If Hospital Provider Spells are to be closed and reopened only as a result of NHS Trust mergers or demergers, for most cases the codes below should be used.
   3. If Hospital Provider Spells are to be closed and reopened only as a result of NHS Trust Mergers or demergers, for most cases the codes below should be used.

   The CLOSED Hospital Provider Spell

   DISCHARGE DESTINATIONS

   This depends on the type of WARD the PATIENT is in, but will be either:

   51     NHS Hospital Provider - WARD for general PATIENTS or the younger physically disabled

   52     NHS Hospital Provider - WARD for maternity PATIENTS or neonates

   53     NHS Hospital Provider - WARD for PATIENTS who are mentally ill or have learning disabilities

   DISCHARGE METHOD

   1     PATIENT discharged on clinical advice or with clinical consent

   The REOPENED Hospital Provider Spell

   ADMISSION METHOD

   81     Transfer of any admitted PATIENT from other Hospital Provider other than in an emergency

   Note that this ADMISSION METHOD is classed under "Other Admission". It is not elective and the PATIENT does therefore not have an entry on an Elective Admission List.

   SOURCE OF ADMISSION

   Again, this depends on the type of WARD the PATIENT is in, but will be either:

   51     NHS Hospital Provider - WARD for general PATIENTS or the younger physically disabled or Accident And Emergency Department

   52     NHS Hospital Provider - WARD for maternity PATIENTS or neonates

   53     NHS Hospital Provider - WARD for PATIENTS who are mentally ill or have learning disabilities

   REFERRER CODE

   This will be the referrer to the Hospital Provider Spell within which the PATIENT was receiving care before the merger, i.e. the "original" Hospital Provider Spell.

Introduction

The Paediatric Critical Care Minimum Data Set has been specified as a simple data specification but will be carried within the existing framework of the Commissioning Data Set as supported by the Secondary Uses Service.

Note that this enhancement is only intended to be implemented as a new version in the Commissioning Data Set-XML Message and will not be implemented in the current Commissioning Data Set-EDIFACT Message (NHS005).

Scope:

The definition of Paediatric Critical Care is linked to the definition of Paediatric Critical Care Healthcare Resource Groups.

The scope of the Paediatric Critical Care Minimum Data Set is:

If one or more of these items apply to a PATIENT, then the PATIENT would be counted as receiving Paediatric Critical Care at one of the levels of Intensive Care or High Dependency Care depending on the conditions/interventions which apply.

A number of these interventions will only occur in a Paediatric Intensive Care Unit environment where all PATIENTS are covered by the Paediatric Critical Care Minimum Data Set regardless of treatment. Care for PATIENTS outside of a Paediatric Intensive Care Unit will in practice be dealing with a shorter list of interventions. The Paediatric Critical Care Minimum Data Set should not be collected in facilities other than those with  CRITICAL CARE UNIT FUNCTION:

• Paediatric Intensive Care Unit; or
• Ward for children and young people; or
• High Dependency Unit for children and young people; or
• Renal Unit for children and young people; or
• Burns Unit for children and young people; or
• Non standard location using the operating department for children and young people.

The Commissioning Data Set message will prevent submission of Paediatric Critical Care Minimum Data Set when submitted with a  CRITICAL CARE UNIT FUNCTION other than those listed above.

The Paediatric Critical Care Minimum Data Set will be carried as part of the following Admitted Patient Care Commissioning Data Set Types:

• The Admitted Patient Care Finished General Episode (Commissioning Data Set TYPE 130)
• The Admitted Patient Care Unfinished General Episode (Commissioning Data Set TYPE 190)
• The Admitted Patient Care Delivery Episode (Commissioning Data Set TYPE 140)
• The Admitted Patient Care Unfinished Delivery Episode (Commissioning Data Set TYPE 200)
• The Admitted Patient Care Finished Birth Episode (Commissioning Data Set TYPE 120)
• The Admitted Patient Care Unfinished Birth Episode (Commissioning Data Set TYPE 180)

References:
UK Government Data Standards Catalogue (GDSC), Version 1.0, Agreed 01.01.02. GDSC:
http://www.govtalk.gov.uk/gdsc/html/default.htm

This is the e-GIF standard that should be used for all new and developing systems and for XML messages. For existing CDS EDIFACT messages however, PATIENT NAME should be used.

UK Government Data Standards Catalogue

References:
UK Government Data Standards Catalogue (GDSC), Version 1.0, Agreed 01.01.02. GDSC:
http://www.govtalk.gov.uk/gdsc/html/default.htm

PERSON NAME SUFFIX is the same as PERSON NAME WORD TEXT where the PERSON NAME WORD TYPE equals 'd. Person Name Suffix'.

This is the e-GIF standard that should be used for all new and developing systems and for XML messages. For existing CDS EDIFACT messages however, PATIENT NAME should be used.

UK Government Data Standards Catalogue

This is a type of POSTCODE.

The POSTCODE of the ADDRESS nominated by the PATIENT with ADDRESS ASSOCIATION TYPE 'Main Permanent Residence' or 'Other Permanent Residence'.

If a PATIENT has no fixed abode this should be recorded with the appropriate code (ZZ99 3VZ).

For overseas visitors the POSTCODES OF USUAL ADDRESS field must show the relevant country pseudo postcode commencing ZZ99 plus space followed by a numeric, then an alpha character, then a Z. For example, ZZ99 6CZ is the pseudo-postcode for India. Pseudo-Country postcodes can be found in the NHS Postcode Directory.

The 8 characters field allows a space to be inserted to differentiate between the inward and outward segments of the code, enabling full use to be made of Royal Mail postcode functionality.

See NHS Postcode Directory and Contact Details.

The e-GIF standard POSTCODE should be used for all new and developing systems and for XML messages. For existing CDS EDIFACT messages however, POSTCODE OF USUAL ADDRESS should be used, due to the need to use the exceptional codes listed above.

Notes:
SEX (BABY) is the same as the attribute PERSON GENDER CODE.

The e-GIF standard PERSON GENDER AT REGISTRATION should be used for all new and developing systems and for XML messages. For existing CDS EDIFACT messages however, SEX (BABY) should be used.