Skip to content
Return to search

GP Out of Hours

Description

NHS Boards provide Primary Care OOH services for patients when their registered GP Practice is closed.

Related tags

Technical information

A JSON file is available with further technical information. This can include details of variables and data classes contained in the dataset.

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": "GP Out of Hours",
    "abstract": "NHS Boards provide Primary Care OOH services for patients when their registered GP Practice is closed.",
    "keywords": "GP",
    "publisher": {
      "name": "Public Health Scotland",
      "gatewayId": "c40be7ce-f0ca-4fd8-b63c-0632593d2507"
    },
    "inPipeline": "Not available",
    "shortTitle": "GP Out of Hours",
    "datasetType": "Health and disease",
    "description": "NHS Boards provide Primary Care OOH services for patients when their registered GP Practice is closed. Scottish Government commissioned the National Services Scotland now Public Health Scotland to develop and introduce a dataset to collect information on GP Out of Hours patients across Scotland. National data collection began in April 2014. Data on patients seen by GP Out of Hours (OOH) services across Scotland are collected and maintained by PHS in the national data warehouse known as the GP OOH datamart. Data is collected on local IT system (Adastra), then extracted and submitted to the DataMart on a weekly basis.",
    "contactPoint": "phs.edris@phs.scot",
    "datasetSubType": "Not applicable",
    "populationSize": -1
  },
  "coverage": {
    "spatial": "United Kingdom,Scotland",
    "typicalAgeRange": "0-150"
  },
  "required": {
    "issued": "2024-10-08T11:28:20.351646Z",
    "version": "7.0.0",
    "modified": "2024-10-08T11:28:20.351658Z",
    "gatewayId": "78",
    "revisions": [
      {
        "url": "https://web.prod.hdruk.cloud//dataset/78?version=1.0.0",
        "version": "1.0.0"
      }
    ],
    "gatewayPid": "59471570-562b-4291-bb0d-715dc6c747a9"
  },
  "provenance": {
    "origin": {
      "imageContrast": "Not stated"
    },
    "temporal": {
      "timeLag": "1-2 months",
      "startDate": "2014-04-01",
      "accrualPeriodicity": "Monthly",
      "distributionReleaseDate": "2020-09-01"
    }
  },
  "observations": [
    {
      "observedNode": "Events",
      "measuredValue": 7996758,
      "observationDate": "2021-01-20",
      "measuredProperty": "Count",
      "disambiguatingDescription": "Consultations"
    }
  ],
  "accessibility": {
    "usage": {
      "resourceCreator": {
        "name": "National Services Scotland"
      }
    },
    "access": {
      "accessRights": "https://publichealthscotland.scot/services/data-research-and-innovation-services/electronic-data-research-and-innovation-service-edris/services-we-offer/",
      "jurisdiction": "GB-GBN",
      "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/",
      "dataProcessor": "National Services Scotland",
      "dataController": "National Services Scotland",
      "deliveryLeadTime": "Not applicable",
      "accessRequestCost": "https://publichealthscotland.scot/services/data-research-and-innovation-services/electronic-data-research-and-innovation-service-edris/cost-of-services/",
      "accessServiceCategory": "TRE/SDE"
    },
    "formatAndStandards": {
      "formats": "text;,;csv",
      "languages": "en",
      "vocabularyEncodingSchemes": "OTHER"
    }
  },
  "structuralMetadata": [
    {
      "name": "PRESCRIPTION FILE",
      "columns": [
        {
          "name": "GUID (Unique Case Reference)",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "Unique Case Reference ID."
        }
      ],
      "description": "The file contains the prescriptions made for the case.\nThere may be multiple prescription records for a single case and multiple records for a single drug prescribed"
    },
    {
      "name": "PRESCRIPTION FILE",
      "columns": [
        {
          "name": "Prescirption GUID",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "The reference ID for the prescription."
        }
      ],
      "description": "The file contains the prescriptions made for the case.\nThere may be multiple prescription records for a single case and multiple records for a single drug prescribed"
    },
    {
      "name": "PRESCRIPTION FILE",
      "columns": [
        {
          "name": "Drug Name",
          "dataType": "Varchar (100)",
          "sensitive": false,
          "description": "The name of the drug."
        }
      ],
      "description": "The file contains the prescriptions made for the case.\nThere may be multiple prescription records for a single case and multiple records for a single drug prescribed"
    },
    {
      "name": "PRESCRIPTION FILE",
      "columns": [
        {
          "name": "BNF Code",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The BNF code of the drug at paragraph level. Format: 99.99.99.99"
        }
      ],
      "description": "The file contains the prescriptions made for the case.\nThere may be multiple prescription records for a single case and multiple records for a single drug prescribed"
    },
    {
      "name": "PRESCRIPTION FILE",
      "columns": [
        {
          "name": "Prescribed from Stock (Y/N)",
          "dataType": "Varchar (1)",
          "sensitive": false,
          "description": "A Y/N flag to indicate if the drug was prescribed from stock."
        }
      ],
      "description": "The file contains the prescriptions made for the case.\nThere may be multiple prescription records for a single case and multiple records for a single drug prescribed"
    },
    {
      "name": "DIAGNOSIS FILE",
      "columns": [
        {
          "name": "Diagnosis Description",
          "dataType": "Varchar (150)",
          "sensitive": false,
          "description": "The description for the diagnosis Read code."
        }
      ],
      "description": "The file contains the diagnosis for the case.\nThere may be multiple diagnosis records for a single case."
    },
    {
      "name": "DIAGNOSIS FILE",
      "columns": [
        {
          "name": "GUID (Unique Case Reference)",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "Unique Case Reference ID."
        }
      ],
      "description": "The file contains the diagnosis for the case.\nThere may be multiple diagnosis records for a single case."
    },
    {
      "name": "DIAGNOSIS FILE",
      "columns": [
        {
          "name": "Diagnosis Code",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The diagnosis Read code."
        }
      ],
      "description": "The file contains the diagnosis for the case.\nThere may be multiple diagnosis records for a single case."
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Priority after Assessment",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "The priority of the treatment determined to be required after assessment, e.g. Routine, 1 hour max response."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Referral Source (unmapped)",
          "dataType": "Varchar (100)",
          "sensitive": false,
          "description": "The source of the referral to the OoH service, which has not been mapped into categories."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Location Referred to Type unmapped",
          "dataType": "Varchar (100)",
          "sensitive": false,
          "description": "The location the patient was referred to from the OoH Service, which has not been mapped into categories."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Call ID (NHS24)",
          "dataType": "Varchar (10)",
          "sensitive": false,
          "description": "A unique call reference number assigned by NHS 24 which will be on records where the patient was referred to the OoH service by NHS 24."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "ECS Consent Given (Y/N)",
          "dataType": "Varchar (1)",
          "sensitive": false,
          "description": "A Y/N flag to indicate if the patient gave permission to access their emergency care summary (ECS)."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "GP Practice",
          "dataType": "Varchar (6)",
          "sensitive": false,
          "description": "The national GP Practice code for the practice the patient is registered with."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Triaged By",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "The organisation which triaged the patient at reception, e.g. NHS 24, OoH Centre Staff, Other. \n \nWhere the NHS 24 Outcome code is UNT1 the Triaged By value will be NHS 24 Untriaged."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "GP Practice Registration Type",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "Identifies patient’s registration status with their GP Practice, e.g. Registered, Unregistered (INT)."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "NHS Board of Treatment",
          "dataType": "Varchar (10)",
          "sensitive": false,
          "description": "The NHS Board cipher for the NHS Board of Treatment.  \n \nThis is included in the file extract because it cannot be derived from location of treatment."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Case Number",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "A number used by users to identify a case on their OoH system. This number is not unique within the dataset and will need to be used in combination with other data items, e.g. Service Contact Start Date, Location of Treatment."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Priority on Reception",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "The priority of the treatment given at triage, e.g. Routine, 1 hour max response. This may have been assigned by NHS24 or by OoH Centre staff (as per Triaged by data item)."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Current Postcode",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The postcode of the location the patient became unwell at. This may differ from the postcode of residence."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Patient Forename",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "The first forename of the patient.  \n \nThe patient forename will include spaces. Only information before the first space will be used to ensure that the name is in the correct format for CHI seeding."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Method of Handover",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "The information handover process, e.g. Email, Fax, Phone, Print, from the OoH service to another NHS healthcare provider."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "GP Consent Given (Y/N)",
          "dataType": "Varchar (1)",
          "sensitive": false,
          "description": "A Y/N flag to indicate if the patient has given consent for the details of their contact with NHS 24/OoH service to be sent to their GP."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "KIS Accessed (Y/N)",
          "dataType": "Varchar (1)",
          "sensitive": false,
          "description": "A Y/N flag to indicate if the KIS was accessed."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Referal Source",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "The source of the referral to the OoH service categorized into groups, e.g. A&E, HCP, Patient is caller."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Priority on Completion",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "The priority of the treatment determined to be required after the treatment has been completed, e.g. Routine, 1 hour max response."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "GUID (Unique Case Reference)",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "Unique Case Reference ID. The GUID can be used to uniquely identify a case. Format: 00000000-0000-0000-0000-000000000000"
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Home Visit Dispatch Date Time",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The date time the vehicle was dispatched for a home visit.  \n \nDate Time format: YYYYMMDDhhmmss"
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Patient Surname",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "The surname of the patient. \n \nRequired for CHI seeding."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Postcode of Residence",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The patient’s postcode of residence.  \n \nThis will be used to derive the NHS Board of residence where a valid CHI number is not available."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Date of Birth",
          "dataType": "Varchar (10)",
          "sensitive": false,
          "description": "The patient’s full date of birth. \n \nFormat: YYYYMMDD  \n \nDate of Birth will be used for CHI seeding and will be used to derive age where a valid CHI number is not available."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Service Contact Start Date Time",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The date time the patient first came into contact with the OoH service.   \n \nDate Time format: YYYYMMDDhhmmss"
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "CHI Number",
          "dataType": "Varchar (10)",
          "sensitive": false,
          "description": "Unique patient identifier for Scottish residents. If the CHI number is 9 digits it will be left zero padded."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "ECS Accessed (Y/N)",
          "dataType": "Varchar (1)",
          "sensitive": false,
          "description": "A Y/N flag to indicate if the ECS was accessed."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "ECS Accessed by HCP (Y/N)",
          "dataType": "Varchar (1)",
          "sensitive": false,
          "description": "A Y/N flag to indicate if the ECS was accessed by a Health Care Professional at the OoH service."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "GP Practice emailed Date Time",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The date time an email was sent to the patient’s GP Practice to advise that they had contacted NHS 24/OoH service.  \n \nThis will only be completed if the email was sent successfully. It cannot be used to determine if/when the email was actually received by the GP Practice.  \n \nDate Time format: YYYYMMDDhhmmss"
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "MASTER FILE",
      "columns": [
        {
          "name": "Gender",
          "dataType": "Char (1)",
          "sensitive": false,
          "description": "The patient’s gender, e.g. 1 = Male, 2 = Female."
        }
      ],
      "description": "The file will be at case level, i.e. a record will include data associated with a patient’s single \nencounter (service contact) with the OoH service. A patient can have multiple submissions\nin a file"
    },
    {
      "name": "APPOINTMENT FILE",
      "columns": [
        {
          "name": "Booked Date Time",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The appointment date. DateTime format: YYYYMMDDhhmmss"
        }
      ],
      "description": "The file contains the appointments made for the case.\nThere may be multiple appointment records for a single case."
    },
    {
      "name": "APPOINTMENT FILE",
      "columns": [
        {
          "name": "Arrival Status",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "Indicates if the patient arrived for their appointment, e.g. DNA, Arrived, Not Arrived, Other"
        }
      ],
      "description": "The file contains the appointments made for the case.\nThere may be multiple appointment records for a single case."
    },
    {
      "name": "APPOINTMENT FILE",
      "columns": [
        {
          "name": "GUID (Unique Case Reference)",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "Unique Case Reference ID."
        }
      ],
      "description": "The file contains the appointments made for the case.\nThere may be multiple appointment records for a single case."
    },
    {
      "name": "APPOINTMENT FILE",
      "columns": [
        {
          "name": "Appointment Cancelled",
          "dataType": "Varchar (1)",
          "sensitive": false,
          "description": "A Y/N flag to identify if the appointment was cancelled."
        }
      ],
      "description": "The file contains the appointments made for the case.\nThere may be multiple appointment records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Location of Treatment Description",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "The description for the location of treatment."
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Clinician Type",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The type of clinician, e.g. Doctor, Nurse."
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Consultation Type (Unmapped)",
          "dataType": "Varchar (100)",
          "sensitive": false,
          "description": "The type of consultation which has not been mapped into categories."
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Consultation Type (PCEC, HV etc.)",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "The type of consultation categorized into groups, e.g. Home visit, Doctor Advice/Nurse Advice."
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Consultation End Date Time",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The date time the consultation ended.  \n \nDate Time format: YYYYMMDDhhmmss"
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Consultaion Start Date Time",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The date time of the start of the patient’s consultation with the OoH service. This may differ from the Service Contact Start Date Time and relates to any type of consultation, e.g. telephone advice, home visit or face to face in base. \n \nThis is the Date Time the clinician arrives at the patient’s home if the Consultation Type is Home \nVisit.  \n \nDate Time format: YYYYMMDDhhmmss"
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "GMC Number",
          "dataType": "Varchar (10)",
          "sensitive": false,
          "description": "National GMC code for the clinician who saw the patient."
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Consultation GUID",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "Unique Case Reference ID. The GUID can be used to identify a consultation. \n \nFormat: 00000000-0000-0000-0000-000000000000"
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Case Number",
          "dataType": "Varchar (50)",
          "sensitive": false,
          "description": "A number used by users to identify a case on their OoH system. \n \nThis number is not unique within the dataset and will need to be used in combination with other data items, e.g. Service Contact Start Date, Location of Treatment."
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "GUID (Unique Case Reference)",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "Unique Case Reference ID. The GUID can be used to uniquely identify a case. Format: 00000000-0000-0000-0000-000000000000"
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "CONSULTATION FILE",
      "columns": [
        {
          "name": "Location of Treatment",
          "dataType": "Varchar (20)",
          "sensitive": false,
          "description": "The code for the location of treatment.  \n \nThis is not a National code. The description associated with a code may vary between NHS Boards."
        }
      ],
      "description": "The file contains the consultations for the case.\nThere may be multiple consultation records for a single case."
    },
    {
      "name": "OUTCOME FILE",
      "columns": [
        {
          "name": "GUID (Unique Case Reference)",
          "dataType": "Varchar (120)",
          "sensitive": false,
          "description": "Unique Case Reference ID."
        }
      ],
      "description": "The file contains the outcome of the case.\nThere may be multiple outcome records for a single case."
    },
    {
      "name": "OUTCOME FILE",
      "columns": [
        {
          "name": "Consultation Outcome",
          "dataType": "Varchar (150)",
          "sensitive": false,
          "description": "The outcome which has not been mapped into categories.  This may be free text."
        }
      ],
      "description": "The file contains the outcome of the case.\nThere may be multiple outcome records for a single case."
    }
  ]
}

Copied to clipboard

Additional information

  • Documentation
    Documentation
  • Language
    English
  • Geographic Area
    Scotland

Related links

Requesting access to this data

This is a secure dataset that can only be accessed by researchers from approved organisations.

  • Publisher
    Public Health Scotland
  • Contact
    phs.edris@phs.scot

Find out how to apply to access this dataset

Synthetic data

Synthetic data is not yet available for this dataset. 

Key Details

  • Formal release or publication date
    01/09/2020
  • Start time period of data covered by this dataset
    01/04/2014
  • End time period of data covered by this dataset
    No information available
  • Documentation
    NHS Boards provide Primary Care OOH services for patients when their registered GP Practice is closed. Scottish Government commissioned the National Services Scotland now Public Health Scotland to develop and introduce a dataset to collect information on GP Out of Hours patients across Scotland. National data collection began in April 2014. Data on patients seen by GP Out of Hours (OOH) services across Scotland are collected and maintained by PHS in the national data warehouse known as the GP OOH datamart. Data is collected on local IT system (Adastra), then extracted and submitted to the DataMart on a weekly basis.
  • Geographic Area
    United Kingdom,Scotland
  • Landing page
  • Language
    English
  • The dataset type
    PHYSICAL
  • Update frequency
    monthly