Service event—date of service, DDMMYYYY

Implementation start date: 01/10/2011

DSS specific information:

For administrative purposes, date of service is reported twice on the collection form (as pages of the form are separated the date of service is reported once on page 1 and once on page 2).

Date of service follows the standard DD/MM/YYYY format except where not enough detail is provided.  In these instances the following codes should be used:
 
'Invalid' :        01/01/1800
 
'Not stated' : 01/01/1900

Implementation start date: 01/04/2012

DSS specific information:

This data element is used to record the date of the operation. The date is recorded as DD/MM/YY. Slashes must be entered.

'01/01/1800' is used to record data that is invalid.

'01/01/1900' is used to record data that is not stated.

Implementation start date: 01/05/2011

Implementation end date: 31/03/2012

DSS specific information:

Date of service follows the standard DD/MM/YYYY format except where not enough detail is provided.  In these instances the following codes should be used:

'Other' :        01/01/1800

'Not stated' : 01/01/1900

Implementation start date: 01/04/2012

Implementation end date: 30/04/2013

DSS specific information:

Date of service follows the standard DD/MM/YYYY format except where not enough detail is provided.  In these instances the following codes should be used:

'Other' :        01/01/1800

'Not stated' : 01/01/1900

Implementation start date: 01/05/2013

DSS specific information:

Date of service follows the standard DD/MM/YYYY format except where not enough detail is provided.  In these instances the following codes should be used:

'Other' :        01/01/1800

'Not stated' : 01/01/1900