BHDP - Outpatient Appointments and Attendances - SMR00

Preview of JSON file

{
  "linkage": {
    "associatedMedia": "https://publichealthscotland.scot/services/data-research-and-innovation-services/electronic-data-research-and-innovation-service-edris/overview/what-is-edris/"
  },
  "summary": {
    "title": "BHDP - Outpatient Appointments and Attendances - SMR00",
    "abstract": "The Outpatients (SMR00) dataset collects episode level data from patients on new and follow up appointments at outpatient clinics in all specialities (except A&E and Genito-Urinary Medicine).\nThis is a subset of data for the Brain Health Data Pilot (BHDP)",
    "keywords": "Outpatient;,;BHDP;,;Brain Health",
    "publisher": {
      "name": "Public Health Scotland",
      "gatewayId": "c40be7ce-f0ca-4fd8-b63c-0632593d2507"
    },
    "inPipeline": "Not available",
    "shortTitle": "BHDP - Outpatient Appointments and Attendances - SMR00",
    "datasetType": "Health and disease",
    "description": "The Brain Health Data Pilot (BHDP) project aims to be a shared database (like a library) of information for scientists studying brain health, especially for diseases like dementia, which affects about 900,000 people in the UK. Its main feature is a huge collection of brain images linked to routinely collected health records, both from NHS Scotland, which will help scientists learn more about dementia and other brain diseases. What is special about this database is that it will get better over time – as scientists use it and add their discoveries, it becomes more valuable. \n\nThis is a subset of the Outpatient Appointment and Attendances (SMR00) dataset for use in the Brain Health Data Pilot (BHDP) project. \n\nAn SMR00 is generated for outpatients receiving care in the specialties listed when:\n\n-they attend a medical consultant outpatient clinic;\n-they meet with a consultant or senior member of his/her team outwith an outpatient clinic session (including the patient's home).\n-they attend a clinic run by a nurse or an AHP identified as the Health Care Professional Responsible for Care for that clinic and who has legal and clinical responsibility for that patient.\n\nThe dataset is generally fully complete and ready for analysis three month preceding the current date.  So for example at the end of August, data is available until the end of May.",
    "contactPoint": "phs.edris@phs.scot",
    "datasetSubType": "Not applicable",
    "populationSize": 820959
  },
  "coverage": {
    "pathway": "All of secondary care in relation to appointments and attendances",
    "spatial": "United Kingdom,Scotland",
    "followUp": "Other",
    "typicalAgeRange": "0-150"
  },
  "required": {
    "issued": "2024-10-08T11:28:19.908813Z",
    "version": "1.0.0",
    "modified": "2024-10-08T11:28:19.908824Z",
    "gatewayId": "76",
    "revisions": [
      {
        "url": "https://web.prod.hdruk.cloud//dataset/76?version=1.0.0",
        "version": "1.0.0"
      }
    ],
    "gatewayPid": "0b09ce12-4099-4d40-93d4-e9e05cdb4d06"
  },
  "provenance": {
    "origin": {
      "source": "EPR",
      "purpose": "Care",
      "imageContrast": "Not stated",
      "collectionSituation": "Secondary care - Outpatients"
    },
    "temporal": {
      "endDate": "2024-05-09",
      "timeLag": "Not applicable",
      "startDate": "2000-01-01",
      "accrualPeriodicity": "Static",
      "distributionReleaseDate": "2014-06-17"
    }
  },
  "observations": [
    {
      "observedNode": "Persons",
      "measuredValue": 820959,
      "observationDate": "2024-06-17",
      "measuredProperty": "Count",
      "disambiguatingDescription": "Outpatient admissions"
    },
    {
      "observedNode": "Events",
      "measuredValue": 11206149,
      "observationDate": "2024-06-17",
      "measuredProperty": "Count",
      "disambiguatingDescription": "Number of Records"
    }
  ],
  "accessibility": {
    "usage": {
      "resourceCreator": {
        "name": "National Services Scotland ;,;Public Health Scotland"
      },
      "dataUseLimitation": "Research-specific restrictions",
      "dataUseRequirement": "Institution-specific restrictions;,;Not for profit use;,;Collaboration required;,;Geographical restrictions"
    },
    "access": {
      "accessRights": "https://publichealthscotland.scot/services/data-research-and-innovation-services/electronic-data-research-and-innovation-service-edris/services-we-offer/",
      "jurisdiction": "GB",
      "accessService": "Scottish National Safe Haven / Trusted Research Environment: https://publichealthscotland.scot/services/data-research-and-innovation-services/electronic-data-research-and-innovation-service-edris/national-safe-haven-nsh/\n\nBrain Health Data Pilot Study",
      "dataProcessor": "National Services Scotland",
      "dataController": "Public Health Scotland",
      "deliveryLeadTime": "Not applicable",
      "accessRequestCost": "https://publichealthscotland.scot/services/data-research-and-innovation-services/electronic-data-research-and-innovation-service-edris/cost-of-services/"
    },
    "formatAndStandards": {
      "formats": "text;,;csv",
      "languages": "en",
      "vocabularyEncodingSchemes": "NHS SCOTLAND NATIONAL CODES"
    }
  },
  "structuralMetadata": [
    {
      "name": "Outpatient Attendance",
      "columns": [
        {
          "name": "Clinic Date",
          "dataType": "Date",
          "sensitive": false,
          "description": "Field Length\n6\n\nPriority\nMandatory\n\nDefinition\nClinic date is the date on which a specific clinic session occurs.\n\nRecording Rules\nEnter the date of the clinic. All dates must be made up to 6 digits (ddmmyy) by entering preceding zeros for single digits in day or month, e.g. 2 April 1999:\n\n0\t2\t0\t4\t9\t9\n\nThis date may be assigned automatically by your computer system.\nPoints to Note\n\nThe record will be queried if the Clinic Date is more than 2 years after Referral Received Date (only if Referral Type = 1 or 2 - New Attendance).\nCross Checks\n\nDate must be in correct date sequence.\nClinic Date is cross-checked against age and specialty."
        }
      ],
      "description": "An outpatient attendance is the occasion of a patient attending a consultant or other medical clinic or meeting with a consultant or senior member of his team outwith a clinic session.\n\nIf the patient is a new outpatient then the attendance is a new outpatient attendance, otherwise it is a follow-up (return) outpatient attendance.\n\nNotes\n\nOutpatient attendances outwith clinic sessions may occur at any location including the patients home (see Home Visit). Those which take place outwith a clinic session on a ward are distinguishable from ward attendances by the fact that the meeting is with a consultant or a senior member of his team rather than with a junior doctor.\nPatients attending clinics usually come from outwith the hospital but may be inpatients. If they are inpatients then usually the inpatient specialty is different from the specialty of the clinic.\nBedside consultations are not outpatient attendances. However, contacts subsequent to a bedside consultation with the same consultant are recorded as outpatient attendances (see Follow Up Outpatients - Recording Rules.\nWard attendances are not outpatient attendances."
    },
    {
      "name": "Outpatient Attendance",
      "columns": [
        {
          "name": "Specialty/Discipline",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Field Length\n3\n\nPriority\nMandatory\n\nDefinitions\n\nSpecialty\nA Specialty is defined as a division of medicine or dentistry covering a specific area of clinical activity and identified within one of the Royal Colleges or Faculties.\n\nClick here for a complete list of Specialties\n\nDiscipline\nA Discipline is a non-medical profession related to healthcare, for which a formal training leading to a recognised professional qualification is undertaken. Examples of disciplines are physiotherapy, nursing, pharmacology.\n\nRecording Rules\nThis field should be coded to the Specialty/Discipline of the consultant/GP/HCP who is in charge of the patient episode. If the consultant is formally recognised and contracted to work in more than one specialty then the patients problem or condition should dictate the specialty.\n\nNote that this is the ONLY rule for completing this field. The designation of the beds is not used.\n\nSpecialty/Discipline comprises four characters, the first three of which are allocated by ISD for each specialty, and is mandatory for completion. For the majority of Specialty/Discipline codes, which are two characters, the 3rd character space must be left blank if the 4th character extension is used. The 4th character is an Optional extension of the code for local special interests.\n\nThe Specialty/Discipline code should be entered in the character spaces provided and left justified.\n\nPoints to Note\n\nA separate SMR record is prepared when a patient changes Specialty, Significant Facility or Consultant on medical grounds\nGPs: Patients under the care of a GP in a GP hospital must be given the Specialty code E12 (GP other than Obstetrics) regardless of whether the patients are in a short stay or long stay facility.\nStaff Wards: The Specialty recorded is that of the consultant/GP in charge of the patient. Record Significant Facility as 11 (Other: including all Standard Specialty Wards, Clinical Facility 1K, Day Bed Unit 1J).\nYounger Physically Disabled: Record the Specialty of the consultant in charge of the patient, which will usually be geriatric medicine. Record Significant Facility as 18 (Ward for Younger Physically Disabled) or 1E (Long Stay Unit for Care of the Elderly).\nSee additional notes under Significant Facility.\nFor SMR02 records this should reflect the speciality of the person who was responsible for the care for the mother on original admission.\nExample 1- If the mother was originally admitted under the care of a midwife in an Alongside Midwifery Unit (AMU) or Freestanding Midwifery Unit (FMU), then the midwifery specialty should be recorded in this section, irrespective of whether the mother was then transferred to an Obstetric unit during labour/delivery. When a transfer has occurred Speciality should NOT be attributed to Obstetrics.\n\nExample 2 - If the mother was originally admitted under the care of a Consultant in an Obstetric Unit then the Obstetrics specialty should be recorded here.\n\nCross Checks\n\nSpecialty is checked against Location Code.\nSpecialty is checked against Consultant.\nSpecialty is checked against the Patients Age (at Date of Admission).\nSpecialty is checked against Duration of Stay calculated between Date of Admission and Date of Discharge.\nSpecialty is checked against Record Type\nSpecialty is checked against Significant Facility."
        }
      ],
      "description": "An outpatient attendance is the occasion of a patient attending a consultant or other medical clinic or meeting with a consultant or senior member of his team outwith a clinic session.\n\nIf the patient is a new outpatient then the attendance is a new outpatient attendance, otherwise it is a follow-up (return) outpatient attendance.\n\nNotes\n\nOutpatient attendances outwith clinic sessions may occur at any location including the patients home (see Home Visit). Those which take place outwith a clinic session on a ward are distinguishable from ward attendances by the fact that the meeting is with a consultant or a senior member of his team rather than with a junior doctor.\nPatients attending clinics usually come from outwith the hospital but may be inpatients. If they are inpatients then usually the inpatient specialty is different from the specialty of the clinic.\nBedside consultations are not outpatient attendances. However, contacts subsequent to a bedside consultation with the same consultant are recorded as outpatient attendances (see Follow Up Outpatients - Recording Rules.\nWard attendances are not outpatient attendances."
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Main Condition/Principal Diagnosis/Problem Managed - ICD10",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n6\nPriority\nMandatory\n\nDefinition\nThis item should be seen as describing the main medical (or social) condition managed/investigated during the patients stay.\n\nRecording Rules\nThe main condition is the condition, diagnosed at the end of the episode of health care, primarily responsible for the patients need for treatment or investigation. If there is more than one such condition, the one held most responsible for the greatest use of resources should be selected. If no diagnosis was made, the main symptom, abnormal finding, or problem should be selected as the main condition.\n\nPoints to Note\n\nFor patients who have died, the main condition is not necessarily the same as the condition recorded as the cause of death.\nThe main condition should be decided by a senior member of the medical staff and recorded in the agreed place in the case notes, on the appropriate form or computer system.\nIf the main condition is coded to a pair of dagger and asterisk codes, the dagger should be entered as main condition.\nIf the main condition is an injury or other condition due to an external cause, the injury or condition should be entered as main condition with the external cause code following the injury (or injuries).\nIn the case of the admission record for SMR04 the admission diagnosis would be as defined in the recording rules (but as diagnosed at the beginning of the episode of healthcare). Further guidance is given in the SMR04 section of the electronic data manual.\nCross Checks\n\nA check is made that each Diagnosis Code is valid as defined by the ICD classification. If not, an error will be reported.\nA check is made that the use of the code (although listed in the ICD Classification) is actually permitted on the record type. If a discrepancy is found, an appropriate error or query will be reported.\nMain condition is cross-checked against:\nSex\nAge (except SMR02)\nRarity (except SMR00, and SMR02)\nAdmission Type (SMR01)\nLength of Stay (SMR01 and SMR04)\nWaiting Time (SMR01 only)\nDischarge Type (SMR01)\nCondition on Discharge (SMR02 only)\nSMR Validation - Main Condition\n\nTags:\nmedical  social  managed  investigated  patient  stay  diagnosed  treatment  ICD10  classification  code  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Condition/Co-morbidity and Complication ICD10 1",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n6\n\nPriority\nLocal\n\nDefinition\nIn addition to the main condition, the record should, whenever possible, also list separately other conditions or problems dealt with during the episode of health care. Other conditions are defined as those conditions that co-exist or develop during the episode of healthcare and affect the management of the patient. Conditions related to an earlier episode that have no bearing on the current episode should not be recorded.\n\nFor further information on co-morbidities and other conditions, please refer to the Scottish Clinical Coding Standards, (in particular Coding Guidelines 21 November 2007) as held on the Terminology Website\n\nPoints to Note\n\nUp to five other significant conditions may be recorded for SMR01 returns.\nOther conditions should be recorded according to the rules outlined in Coding Guidelines 21 November 2007.\nFrom April 2020,this data item is no longer required for national collection on SMR00, though may still be collected locally.\nPriority changed from Mandatory (where applicable) to Local.\nCross Checks\n\nAs for main condition.\nA main condition must be recorded before the Other Condition fields can be completed.\nSMR Validation - Other Conditions\n\nTags:\naddition  main  episode  problem  management  patient  coding  guidelines  care  significant  ICD10  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Condition/Co-morbidity and Complication ICD10 2",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n6\n\nPriority\nLocal\n\nDefinition\nIn addition to the main condition, the record should, whenever possible, also list separately other conditions or problems dealt with during the episode of health care. Other conditions are defined as those conditions that co-exist or develop during the episode of healthcare and affect the management of the patient. Conditions related to an earlier episode that have no bearing on the current episode should not be recorded.\n\nFor further information on co-morbidities and other conditions, please refer to the Scottish Clinical Coding Standards, (in particular Coding Guidelines 21 November 2007) as held on the Terminology Website\n\nPoints to Note\n\nUp to five other significant conditions may be recorded for SMR01 returns.\nOther conditions should be recorded according to the rules outlined in Coding Guidelines 21 November 2007.\nFrom April 2020,this data item is no longer required for national collection on SMR00, though may still be collected locally.\nPriority changed from Mandatory (where applicable) to Local.\nCross Checks\n\nAs for main condition.\nA main condition must be recorded before the Other Condition fields can be completed.\nSMR Validation - Other Conditions\n\nTags:\naddition  main  episode  problem  management  patient  coding  guidelines  care  significant  ICD10  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Condition/Co-morbidity and Complication ICD10 3",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n6\n\nPriority\nLocal\n\nDefinition\nIn addition to the main condition, the record should, whenever possible, also list separately other conditions or problems dealt with during the episode of health care. Other conditions are defined as those conditions that co-exist or develop during the episode of healthcare and affect the management of the patient. Conditions related to an earlier episode that have no bearing on the current episode should not be recorded.\n\nFor further information on co-morbidities and other conditions, please refer to the Scottish Clinical Coding Standards, (in particular Coding Guidelines 21 November 2007) as held on the Terminology Website\n\nPoints to Note\n\nUp to five other significant conditions may be recorded for SMR01 returns.\nOther conditions should be recorded according to the rules outlined in Coding Guidelines 21 November 2007.\nFrom April 2020,this data item is no longer required for national collection on SMR00, though may still be collected locally.\nPriority changed from Mandatory (where applicable) to Local.\nCross Checks\n\nAs for main condition.\nA main condition must be recorded before the Other Condition fields can be completed.\nSMR Validation - Other Conditions\n\nTags:\naddition  main  episode  problem  management  patient  coding  guidelines  care  significant  ICD10  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Condition/Co-morbidity and Complication ICD10 4",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n6\n\nPriority\nLocal\n\nDefinition\nIn addition to the main condition, the record should, whenever possible, also list separately other conditions or problems dealt with during the episode of health care. Other conditions are defined as those conditions that co-exist or develop during the episode of healthcare and affect the management of the patient. Conditions related to an earlier episode that have no bearing on the current episode should not be recorded.\n\nFor further information on co-morbidities and other conditions, please refer to the Scottish Clinical Coding Standards, (in particular Coding Guidelines 21 November 2007) as held on the Terminology Website\n\nPoints to Note\n\nUp to five other significant conditions may be recorded for SMR01 returns.\nOther conditions should be recorded according to the rules outlined in Coding Guidelines 21 November 2007.\nFrom April 2020,this data item is no longer required for national collection on SMR00, though may still be collected locally.\nPriority changed from Mandatory (where applicable) to Local.\nCross Checks\n\nAs for main condition.\nA main condition must be recorded before the Other Condition fields can be completed.\nSMR Validation - Other Conditions\n\nTags:\naddition  main  episode  problem  management  patient  coding  guidelines  care  significant  ICD10  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Condition/Co-morbidity and Complication ICD10 5",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n6\n\nPriority\nLocal\n\nDefinition\nIn addition to the main condition, the record should, whenever possible, also list separately other conditions or problems dealt with during the episode of health care. Other conditions are defined as those conditions that co-exist or develop during the episode of healthcare and affect the management of the patient. Conditions related to an earlier episode that have no bearing on the current episode should not be recorded.\n\nFor further information on co-morbidities and other conditions, please refer to the Scottish Clinical Coding Standards, (in particular Coding Guidelines 21 November 2007) as held on the Terminology Website\n\nPoints to Note\n\nUp to five other significant conditions may be recorded for SMR01 returns.\nOther conditions should be recorded according to the rules outlined in Coding Guidelines 21 November 2007.\nFrom April 2020,this data item is no longer required for national collection on SMR00, though may still be collected locally.\nPriority changed from Mandatory (where applicable) to Local.\nCross Checks\n\nAs for main condition.\nA main condition must be recorded before the Other Condition fields can be completed.\nSMR Validation - Other Conditions\n\nTags:\naddition  main  episode  problem  management  patient  coding  guidelines  care  significant  ICD10  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Main Operation/Treatment/Investigative Procedure/Intervention - OPCS4",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n8\n\nPriority\nConditional\n\nDefinition\nMain Operation/Treatment/Investigative Procedure/Intervention are those aspects of clinical care carried out on patients undergoing treatment:\n\nfor the prevention, diagnosis, care or relief of disease\nfor the correction of deformity or deficit, including those performed for cosmetic reasons\nassociated with pregnancy, childbirth or contraceptive or procreative management\nTypically this will be:\n\nsurgical in nature: and/or\ncarries a procedural risk: and/or\ncarries an anaesthetic risk: and/or\nrequires specialist training: and/or\nrequires special facilities or equipment only available in an acute care setting.\nPoints to Note\n\nPlease refer to the general rules for recording operations/procedures.\nCross Checks\n\nA check is made that each Operation Code is valid as defined by the OPCS Classification. If not, an error will be reported.\nA check is made that the use of the OPCS code is actually permitted on the record type. If a discrepancy is found, an appropriate error or query will be reported.\nIf Main Operation is specified, but the Date of Main Operation is not given, an error will be reported.\nEach operation can have one or two codes. Checks are made to ensure that an Approach, Technique, Site or Laterality code is not supplied on its own or with another such code. If it is an error will be reported.\n\nSMR01\nIf a code is recorded in the second field of a pair as well as the first field, checks are made to ensure that either:\nthe two codes are a recognised pair or\nthe code in the second field is from one of the subsidiary Y or Z chapters.\nFor any two consecutive single-coded operations, a check is made to see if these could be combined as one dual-coded operation. If this is possible, a query is reported.\nIf the patient is a Day Case, a further check will be made on each Operation code to ensure that the Operation is appropriate for such cases. If not, an error or query will be reported.\nIf the patient is an Outpatient, a further check will be made on each Operation code to ensure that the Operation is appropriate for such cases. If not, a query will be reported.\nEach Operation code is checked to ensure that it is compatible with the stated Sex.\nIf a discrepancy is found an error or a query will be reported.\nSMR Validation - Main and Other Operation/Treatment/Investigative Procedure\n\nTags:\nclinical  care  patients  code  classification  undergoing  treatment  surgical  anaesthetic  acute  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Operation/Treatment/Intervention/Investigative Procedures - OPCS4 1",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n8\n\nPriority\nConditional\n\nDefinition\nThese are the additional procedures performed on an individual patient at a particular time.\n\nPoints to Note\n\nUp to three pairs of procedures, in addition to the main procedure, may be recorded for an inpatient or day case episode on the central return. Therefore, if more than four procedures are performed during an episode of care, the clinicians opinion should be sought on which are the most significant. Local systems may allow more than four procedures to be recorded.\nCross Checks\n\nThese are detailed in Main Operation/Treatment/Investigative Procedure/Intervention.\nSMR Validation - Other Operation\n\nTags:\nadditional  patient  inpatient  day  case  episode  performed  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Operation/Treatment/Intervention/Investigative Procedures - OPCS4 2",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n8\n\nPriority\nConditional\n\nDefinition\nThese are the additional procedures performed on an individual patient at a particular time.\n\nPoints to Note\n\nUp to three pairs of procedures, in addition to the main procedure, may be recorded for an inpatient or day case episode on the central return. Therefore, if more than four procedures are performed during an episode of care, the clinicians opinion should be sought on which are the most significant. Local systems may allow more than four procedures to be recorded.\nCross Checks\n\nThese are detailed in Main Operation/Treatment/Investigative Procedure/Intervention.\nSMR Validation - Other Operation\n\nTags:\nadditional  patient  inpatient  day  case  episode  performed  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Other Operation/Treatment/Intervention/Investigative Procedures - OPCS4 3",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n8\n\nPriority\nConditional\n\nDefinition\nThese are the additional procedures performed on an individual patient at a particular time.\n\nPoints to Note\n\nUp to three pairs of procedures, in addition to the main procedure, may be recorded for an inpatient or day case episode on the central return. Therefore, if more than four procedures are performed during an episode of care, the clinicians opinion should be sought on which are the most significant. Local systems may allow more than four procedures to be recorded.\nCross Checks\n\nThese are detailed in Main Operation/Treatment/Investigative Procedure/Intervention.\nSMR Validation - Other Operation\n\nTags:\nadditional  patient  inpatient  day  case  episode  performed  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Date of Main Operation/Treatment/Investigative Procedure/Intervention",
          "dataType": "Date (ddmmyy)",
          "sensitive": false,
          "description": "Format\nDate (ddmmyy)\n\nField Length\n6\n\nPriority\nConditional\n\nDefinition\nThis reflects the date the main operation was performed.\n\nRecording Rules\nThe full date should be entered thus: 5 July 2004 = 05/07/04\n\nCross Checks\n\nDate of Main Operation is checked to ensure it is in the correct sequence with other dates recorded.\nAn error will be reported if there is a Main Operation recorded but the Date of Main Operation has been omitted.\nAn error will be reported if an entry has been made for Date of Main Operation, but the Main Operation has been omitted.\nSMR Validation - Date of Main Operation/Treatment/Investigative Procedure\n\nTags:\nsequence  reported  performed  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Date of Other Operation/Treatment/Intervention/Investigative Procedures 1",
          "dataType": "Date (ddmmyy)",
          "sensitive": false,
          "description": "Format\nDate (ddmmyy)\n\nField Length\n6\n\nPriority\nConditional\n\nDefinition\nThis reflects the date the other operation was performed.\n\nRecording Rules\nThe full date should be entered thus: 5 July 2004 = 05/07/04\n\nCross Checks\n\nDate of Other Operation is checked to ensure it is in the correct sequence with other dates recorded.\nSMR Validation - Date of Other Operation\n\nTags:\nperformed  sequence  recorded  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Date of Other Operation/Treatment/Intervention/Investigative Procedures 2",
          "dataType": "Date (ddmmyy)",
          "sensitive": false,
          "description": "Format\nDate (ddmmyy)\n\nField Length\n6\n\nPriority\nConditional\n\nDefinition\nThis reflects the date the other operation was performed.\n\nRecording Rules\nThe full date should be entered thus: 5 July 2004 = 05/07/04\n\nCross Checks\n\nDate of Other Operation is checked to ensure it is in the correct sequence with other dates recorded.\nSMR Validation - Date of Other Operation\n\nTags:\nperformed  sequence  recorded  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "General Clinical Information",
      "columns": [
        {
          "name": "Date of Other Operation/Treatment/Intervention/Investigative Procedures 3",
          "dataType": "Date (ddmmyy)",
          "sensitive": false,
          "description": "Format\nDate (ddmmyy)\n\nField Length\n6\n\nPriority\nConditional\n\nDefinition\nThis reflects the date the other operation was performed.\n\nRecording Rules\nThe full date should be entered thus: 5 July 2004 = 05/07/04\n\nCross Checks\n\nDate of Other Operation is checked to ensure it is in the correct sequence with other dates recorded.\nSMR Validation - Date of Other Operation\n\nTags:\nperformed  sequence  recorded  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Diagnostic Section"
    },
    {
      "name": "Patient Identification and Demographic Information",
      "columns": [
        {
          "name": "Ethnic Group",
          "dataType": "Characters",
          "sensitive": false,
          "description": "Format\nCharacters\n\nField Length\n2\n\nPriority\nOptional\n\nDefinition\nEthnic group classifies the person according to their own perceived ethnic group and cultural background. (Scotland Census)\n\nPoints to Note\n\nThis is included as an Optional item, but may be made Mandatory at a later date in order to conform to UK-wide requirements.\nThis is the patients perception of his or her own ethnic group, and is intended to assist the monitoring of equality of access to NHS services..\nFor the A&E datamart, please ensure this data item is as complete as possible\nCross Checks\nNone.\n\nNotes\nThe following list is the current ethnicity classification (2011 Census categories). This should be used by NHS Scotland organisations for local and SMR return purposes. Local systems may record more detailed codes as required but these must map to the categories for SMR return purposes.\n\nThe letters that appear in the group headings in the codes and value list refer to positions in the census list and are not valid SMR codes. Please only use the codes in the code list (1A, 1B etc.).\n\nCodes and Values: Ethnic Group (Code order)\n\nGroup A - White\n1A Scottish\n1B Other British\n1C Irish\n1K Gypsy/ Traveller\n1L Polish\n1Z Other white ethnic group\n\nGroup B - Mixed or multiple ethnic groups\n2A Any mixed or multiple ethnic groups\n\nGroup C - Asian, Asian Scottish or Asian British\n3F Pakistani, Pakistani Scottish or Pakistani British\n3G Indian, Indian Scottish or Indian British\n3H Bangladeshi, Bangladeshi Scottish or Bangladeshi British\n3J Chinese, Chinese Scottish or Chinese British\n3Z Other Asian, Asian Scottish or Asian British\n\nGroup D - African\n4D African, African Scottish or African British\n4Y Other African\n\nGroup E - Caribbean or Black\n5C Caribbean, Caribbean Scottish or Caribbean British\n5D Black, Black Scottish or Black British\n5Y Other Caribbean or Black\n\nGroup F - Other ethnic group\n6A Arab, Arab Scottish or Arab British\n6Z Other ethnic group\n\nGroup G - Refused/Not provided by patient\n98 Refused/Not provided by patient\n\nGroup H - Not Known\n99 Not Known\n\nSMR Validation - Ethnic Group\n\nTags:\nethnicity  classification  census  person  perceived  cultural  background  categories  SMR00  SMR01  SMR02  SMR04"
        }
      ],
      "description": "Patient Identification and Demographic Information"
    },
    {
      "name": "Scottish Index of Multiple Deprivation (SIMD)",
      "columns": [
        {
          "name": "SIMD Scotland Quintile",
          "dataType": "INTEGER",
          "sensitive": false,
          "description": "Format\nInteger\n\nField Length\n1\n\nPriority\nLocal\n\nDefinition\nA categorisation which divides the Scottish population into five equal categories based on the range of SIMD scores so that 20% of the population falls into each quintile (population weighted). \n\nPoints to note\n\nFor SIMD2016 \nMost Deprived Quintile = 1\nLeast Deprived Quintile = 5"
        }
      ],
      "description": "The index is an area based measure, calculated at data zone level and has seven domains (income, employment, education, housing, health, crime and geographical access). These have been combined into an overall index. Please note that SIMD values may appear for records prior to 1999, however ISD recommendations are to use SIMD for trend analyses from 1999 onwards. For trend analyses back to 1991, use the 2001 census based Carstairs deprivation.\nFor trend analyses back to before 1991, use the 1991 census based Carstairs deprivation. See the ISD website for further information.\nPlease indicate which SIMD version you would like for each selected variable.\n \nNote on change in ordering of quintiles and deciles\nFollowing the release of the SIMD 2009, ISD changed their ordering of quintiles and deciles to fit with the method that is used by the Scottish Government\n(SG). For SIMD 2009, SIMD 2012 and future releases, the method is now: 1 = MOST deprived, 5 or 10 = LEAST deprived\n \n ISD analyses based on SIMD 2006 or SIMD 2004 will be left in their current format:  1 = LEAST deprived; 5 or 10 = MOST deprived. \nTo avoid confusion, deprivation categories should always be fully labelled. For example, for SIMD 2012, 'decile 1 (most deprived)'… 'decile 10 (least deprived)'.\nFor time trend analyses combining SIMD 2004/2006 with SIMD 2009/2012 it is important to treat all deciles and quintiles in the same way. SIMD 2004/2006 deciles/quintiles should be reversed from 1=LEAST deprived, 5 or 10=MOST deprived to 1=MOST deprived, 5 or 10=LEAST deprived in order to keep the same convention for the deciles and quintiles throughout the analysis."
    }
  ]
}