Introduction

The purpose of this file format is to provide a file format which is easy to generate from the data already being collected in hospitals.

For this reason, it uses DSS and DRS Code Sets and items already defined in DSS.

There are some limitations to the grouping which can be performed using this file format, because it doesn't contain a few data items which are required for grouping ambulatory data:

Specifically, the excluded data items are:

Provider Flags: Medical, Nursing, Physical Therapy, Psychosocial Therapy - these are used for most ambulatory AN-SNAP classes
Focus of Care: this is used for classifying Psychogeriatric Ambulatory episodes
PCPSS: this is used for Palliative Care Ambulatory phases

Please see the section 'Notes and Assumptions' below to understand more about how these data items are interpreted by QuickSnap when this file format is used.

Sample Files

Here are some examples of the QuickSnap DSS Compatible file format:

Excel Template: QuickSnap_DSS_template.xlsx - this file contains a header row and is in Excel format - QuickSnap cannot process this file but it displays the column headers for each data item
CSV Sample: QuickSnap_DSS_sample.csv - this is a sample CSV file in QuickSnap DSS Compatible format - QuickSnap will be able to process this file

Data Items

Col	Item Name	Data Type	CodeSet / Notes
1	RecordIdentifier	String	Up to 64 characters
2	DSS Care Type	Integer	DSS Care Type
3	AN-SNAP Episode Type	Integer	AN-SNAP Episode Type [1 – 5]
4	DSS Episode of Admitted Patient Care – clinical assessment only indicator	Integer	DSS Assessment Only
5	DRS Palliative Care Phase Type	Integer	DRS Palliative Care Phase Type
6	Impairment Code	Decimal	Rehabilitation Impairment Codes
7	Date of Birth	Date
8	Start Date	Date	formerly Episode Admission Date
9	End Date	Date	formerly Episode Discharge Date
10	Leave Days	Integer
11	RUG – Activities of Daily Living (RUG-ADL)	Integer	RUG-ADL Total [4-18]
12	FIM – Motor subscale total	Integer	FIM Motor Total [13-91]
13	FIM – Cognition subscale total	Integer	FIM Cognition Total [5-35]
14	HoNOS 65+ Overactive, Aggressive, Disruptive Behaviour	Integer	HoNOS 65+ Overactive [0-5]
15	HoNOS 65+ Problems with Activities of Daily Living (ADL)	Integer	HoNOS 65+ ADL [0-4]
16	HoNOS 65+ Total	Integer	HoNOS 65+ Total [0-48]
17	DSS Episode of Admitted Patient Care - type of maintenance provided	Integer	DSS Maintenance Type

Abbreviations

RUG: Resource Utilisation Groups
PCPSS: Palliative Care Problem Severity Score
FIM: Functional Independence Measure
HoNOS 65+: Health of the Nation Outcome Scale 65+

Notes and Assumptions

Episode Type is not part of DSS but will need to be included in the file as it is a core AN-SNAP data item. Generally the assumption would be: Episode Type = Overnight (1)
Impairment Code is the AROC v4 Impairment Code, as specified in this document: AROCv4 Impairment Codes.pdf
Start and End Date are interpreted using the rules as per QuickSnap Native Format
Age and Length of Stay will be derived using the rules as per QuickSnap Native Format
PCPSS has been omitted from this file format because it is not part of the DSS Data Set.

QuickSnap will assume PCPSS = ‘missing’
This will result in most Episodes with Case Type: Palliative Care, Episode Type: Ambulatory (Same Day, Outpatient, Community) being ungroup-able

HoNOS 65+ Scores provided in DSS will be mapped directly to HoNOS scores used in AN-SNAP
Focus of Care has been omitted from this file format because it is not part of the DSS Data Set

QuickSnap will assume Focus of Care = ‘missing’
This will result in most Episodes with Case Type: Psychogeriatric, Episode Type: Ambulatory (Same Day, Outpatient, Community) being ungroup-able

Provider Type Flags (Medical, Nursing, Physical Therapy, Psychosocial Therapy) have been omitted from the file format because they are not part of the DSS Data Set

QuickSnap will assume all of these data items are ‘missing’
This would result in grouping errors for the following Case Type/Episode Type combinations:
- Palliative Care – All Ambulatory (Same Day, Outpatient, Community)
- Rehabilitation – Outpatient, Community
- GEM – Outpatient, Community
- Maintenance – All Ambulatory (Same Day, Outpatient, Community)

- Due to the fact that Outpatient and Community ‘Episode Types’ are not relevant for DSS Data Collection, in practise this will only result in grouping errors for Palliative Care and Maintenance All Ambulatory episodes
Different Code Sets: The following data items use different code sets to the native QuickSnap Native Format. QuickSnap will accept the DSS/DRS Code Set and map to the relevant AN-SNAP Code Set as outlined in the tables below:
- DSS Care Type
- DSS clinical assessment only indicator
- DRS Palliative Care Phase Type
- DSS type of maintenance provided

DSS Compatible Format Code Sets and Mappings

DSS Care Type

Value	Description	AN-SNAP Case Type Mapping
2	Rehabilitation Care	Rehabilitation (2)
3	Palliative Care	Palliative Care (1)
4	Geriatric Evaluation and Management	GEM (4)
5	Psychogeriatric Care	Psychogeriatric (3)
6	Maintenance Care	Maintenance (5)

AN-SNAP Episode Type

Value	Description
1	Overnight
2	Same Day
3	Outpatient
4	Community

DSS clinical assessment only indicator

Value	Description	AN-SNAP Assessment Only Mapping
1	Yes	Yes (1)
2	No	No (0)
3	Unknown	Unknown
9	Not Stated	Unknown

Because 3 and 9 map to ‘Unknown’ these values will result in grouping errors for Case Type/Episode Type combinations which require the ‘Assessment Only’ flag.

DRS Palliative Care Phase Type

Value	Description	AN-SNAP Phase Type Mapping
1	Stable	Stable (1)
2	Unstable	Unstable (2)
3	Deteriorating	Deteriorating (3)
4	Terminal	Terminal (4)
9	Not reported	Unknown

Because 9 maps to ‘Unknown’, records with this value will result in grouping errors for Case Type/Episode Type combinations which require Phase Type (almost all Palliative Care episodes)

DSS Maintenance Type

Value	Description	AN-SNAP Maintenance Type Mapping
1	Convalescent Care	Convalescent Care (3)
2	Respite Care	Respite (1)
3	Nursing home type Care	Nursing home type (2)
4	Other maintenance Care	Other Maintenance (4)
98	Unknown	Unknown
99	No Stated/Inadequately Described	Unknown

Because 98 and 99 map to ‘Unknown’, these values will result in grouping errors for Case Type/Episode Type combinations which require Maintenance Type (Case Type: Maintenance, Episode Type: Overnight)