NHS Tayside and NHS Fife laboratory data.

MDW Discover  > NHS Tayside and Fife Biochemistry @ 109

MDW Discover

Browse All

London SDE

West Midlands SDE

Kent, Medway & Sussex SDE

MDW - Discover

This data is provided in a format based upon the SCI-Store system. SCI-Store is a data repository which retains patient laboratory test result information at a health board level. Data prior to 2007 for Tayside has been transformed to fit this structure.  Fife data starts in 2005 and all originates from SCI-Store. There is earlier data available for Fife.

HDR UK

NHS Tayside and Fife

PROCHI

Tayside and Fife labs biochemistry data. This data is provided in a format based upon the SCI-Store system.  Data prior to 2007 for Tayside has been transformed to fit this new structure. There is no legacy data for Fife as this data starts in 2005/6 and all comes from SCI-Store.      Data is complete in later years, but for older Tayside data (particularly pre-98), there may be missing patches in Ninewells data.    Perth data incomplete as early computer systems were simply turned off and data was lost.  Stracathro data became computerised much later than the other labs.    This is a complex dataset which is supplied in a hierarchical form, this extract is a flattening of that hierarchy by HIC.     The HIC recommended approach to using this data is to use the lookup file z_LocalClinicalCodeValue. Use the HICDescription column to find the codes you require. Next identify the records in 2 ways: Use the identified ReadCodeValue OR Use the identified ClinicalCodeValue along with the hb_extract.

Biochemistry (Lab Data Restructured)

LabNumberIdentifiable

Contains comments from the original requestor.  May give the reason for requesting the test, or comments on condition, last eaten etc. This field is not populated for legacy (TS < 07) data..

ClinicalDataRequired

ID / short name of the organisation providing the test results. E.G. NINEWELLS.  For full name see ProvidingOrganisationName..

ProvidingOrganisationID

Local name of the organisation providing the test results.  This maybe include location as well as service name, for example:  (NINEWELL) Tayside Clinical Lab Services.

ProvidingOrganisationName

Type of organisation providing the test results. For Example: Hospital.  For legacy (TS < 07) data, this contains either: Hospital - HIC data - Pre98 or Hospital - HIC data - Post98 as appropriate..

ProvidingOrganisationType

Position held by the party requesting the test results, for example, this might be GP or Consultant..

RequestingPartyPosition

The laboratory providing the sample.   For legacy data, this contains the record source, for example:  Ninewells Data prior to Pinnacle  Perth Masterlab  Perth data from Ilims system  Ninewells Pinnacle Data.

RequestingOrganisationName

The type of organisation that the requestor is part of.  This contains values such as:  Hospital  Practice  Ward.

RequestingOrganisationType

This is the discipline code for the laboratory test. For all biochemistry tests, the discipline code is CC, which represents Clinical Chemistry. .

Discipline

This is the alpha and/or numeric Health Board code in which the patient CHI information was extracted from. .

hb_extract

The result of the test being carried out.  This field contains numeric data only.  .

QuantityValue

Units of measure for the test result QuantityValue field..

QuantityUnit

This fieldrepresents additional information to be used in conjunction with the numeric result field QuantityValue.   The contents should be interpreted along with the QuantityValue, for example, some EGFR results may be reported as QuantityValue = 60, with ArithmeticComparator = '>'    This means the result is greater than 60..

ArithmeticComparator

Maximum guideline value for the test result at the time of testing.      HIC Observation: These ranges vary based on relevant criteria such as age, gender, and guidelines will also change over time..

RangeHighValue

Minimum guideline value for the test result at the time of testing.    HIC Observation: These ranges vary based on relevant criteria such as age, gender, and guidelines will also change over time..

RangeLowValue

Units of the guideline values presented in the RangeHighValue and RangeLowValue fields.    HIC Observation: Don't assume that these units match those of the QuantityValue and Unit..

RangeUnit

Interpretation

This field store the test code for the test taken/performed (e.g., CHOL = Cholesterol) as used by the providing organisation.  Note that this field is not always completed.      Legacy Data Mapping: This field replaces Test_code..

LocalClinicalCodeValue

LocalClinicalCodeDescription

The read code allocated to the test.  This field is useful as a standardised grouping for the tests, for example, if you are looking in Serum Total Cholesterol, all records marked with 44P. represent this regardless of the localClinicalCode provided.    HIC Observation:  Restructuring has significantly improved the quality and accuracy of this field.   For legacy data, field completion rates are much greater, with over 95% of the legacy results now featuring a read code.  HIC have also developed a lookup table, which will be used throughout the data project lifecycle and released along with this data set..

ReadCodeValue

Read code scheme used by the local lab system for read code fields, e.g. R1.

ReadCodeScheme

This is a textual description supplied by the local lab systems for the relevant read code.    HIC Observation: This field appears to have not been mapped to the read code standard. The mapping of read code to description often changes, possibly over time, or versions of read code, for example:  44P. may be described as both 'Serum Total Cholesterol' and 'Total Cholesterol (S)' on different records..

ReadCodeDescription

This is a textual description supplied by the local lab systems..

ClinicalCircumstanceDescription

The data load batch that loaded this record, this will be null if the data was not loaded through the RDMP framework..

hic_dataLoadRunID

Part of the internal HIC primary key used in linking the Labs data together.  This field should be used in communicating record specific queries with HIC as it allows us  to locate the record in question.  This is a unique identifier assigned by the lab system based on the order in which the tests were run on the sample.  For legacy data (TS <07), the value of this field is imputed.  .

TestResultOrder

Part of the internal HIC primary key used in linking the Labs data together.  This is a unique identifier assigned by the lab system.   This field should be used in communicating record specific queries with HIC as it allows us to locate the record in question.  .

LabNumber

Part of the internal HIC primary key used in linking the Labs data together.  This is a unique identifier assigned by the lab system.   This field should be used in communicating record specific queries with HIC as it allows us to locate the record in question.  For legacy data (Tayside <2007), the value of this field is constant..

TestReportID

This indicates the type of sample taken for the test. Sample types include:  Blood  Cerebrospinal  Faeces  Fluid  Fluoride Oxalate  Hair  Liver Biopsy  Miscellaneous  Muscle Biopsy  Serum  Skin Biopsy  Stone  Sweat  Urine  Water    HIC Observation: Tayside labs report both Serum and Blood samples with SampleName = Blood.  The read code value / description can be used to interpret the Sample correctly.  This has been confirmed with the Tayside Lab experts..

SampleName

This is the date and time when the sample was taken from the patient..

DateTimeSampled

SampleRequesterComment

For legacy data, this field tells you how the SampleName field was derived.    Where SampleName is completed, the decision on which original sample_type to take is coded as follows:  "RCA": The sample was derived during HICs Read Code Analysis workshops.  HIC, assisted by researchers, clinicians, and validated by Tayside laboratory experts used all of the available data to assign standardised read codes to a large portion of the data (95%+).  The SampleName was derived from the allocated read code.    "Header = lkp": Both legacy sample header and legacy HIC lookup value for the relevant test code matched.  "lkp in header": The legacy sample header consisted of multiple values (e.g. 'B - U - FO'), but contained the HIC lookup value (e.g. 'Blood') for the relevant test code.  For this example, the final SampleName value would be 'Blood.'  "header only": There was no information available other than the legacy sample header type.  "lkp only": There was no information available other than the legacy HIC lookup sample type for the relevant test code.    For SampleName = 'Unknown'  "no lkp, no header" = No information stored in either legacy header or look up for the test code.  "Header only": Only a legacy header sample type was provided, and is ambiguous, e.g.  'B - FO - M'  This original value is recorded in this field, for this example, the stored value would be "Header only - B - FO - M"  "Header: {*} Lookup: {*}" = The legacy header and sample type provide conflicting values.  This field also records the original values.   .

ServiceProviderComment

Part of the internal HIC primary key used in linking the Labs data together.  This is a unique identifier assigned by the lab system.   This field should be used in communicating record specific queries with HIC as it allows us to locate the record in question..

NHS Tayside and Fife Biochemistry

Documentation

Coverage

Provenance

Origin

Temporal

Accessibility

Access

Usage

Format and Standards

Observations

Origin