Difference between revisions of "Float Data Hourly"

From SICDB Doc
Jump to navigation Jump to search
(Replaced content with "{{:Data Description Data Float h}}")
Tag: Replaced
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Raw Fields of data_float_h ==
{{:Data Description Data Float h}}
 
{| class="wikitable"
|+ Caption text
|-
! Name !! Description !! Comment
|-
| CaseID || Case identifier ||
|-
| DataID || Reference stored in d_references || DataID=ReferenceGlobalID
|-
| Offset || Time in seconds after admission ||
|-
| Val || Value ||
|-
| cnt || Amount of values aggregated ||
|-
| rawdata || List of 60 floats containing raw data  || Due to excessive storage needs minute values have been aggregated.
|}
 
== Aggregation Description ==
Most signal data is averaged. The field data_float_h.cnt describes the amount of values aggregated. It is to be expected that the first signal values have less than 60 data points, as it is quite unlikely (1:60) that signal starts on minute 0.
 
Raw values are saved in field data_float_h.rawdata, being a list of bytes. (IEEE 754 Single(4 bytes), LittleEndian)
 
Metavision does, in database, not differentiate between qualitative (i.e. blood pressure) and quantitative (i.e. drainage volume) data, this was done programatically saving the sum instead of average.
 
== Known Limitations ==
=== 0 Values ===
All values were aggregated to hourly average values. As in many cases Metavision saves 0 values during signal loss times instead of NULL aggregating these would significantly influence statistics. Think about a patient with constant MAP of 60 is disconnected for 15min, aggregating would result in a average MAP of 45. For this reason 0 values were set to NULL and ignored. This behaviour is expected to represent in nearly all cases the most likely value.
 
In very special cases, like cardioplegia, where 0 would be a correct pulse rate, expect values to be missing. Contact developer in case you need this data.

Latest revision as of 19:52, 31 October 2022

Contains hourly float data associated with a case. If more (minute) data is available, data was aggregated and the corresponding values are stored in rawdata field. Refer to Deserialize Raw Data for more information. Metavision does, in database, not differentiate between qualitative (i.e. blood pressure) and quantitative (i.e. drainage volume) data, this was done programatically saving the sum instead of average. The field cnt indicates the amount of values aggregated.

data_float_h.csv.gz
Name Type Description Comment
CaseID Integer Case identifier
DataID Reference
Offset Integer Time in seconds after admission
Val Float Value The unit (if applicable) is found in d_references where data_float_h.DataID is associated to d_references.ReferenceGlobalID
cnt Integer Amount of values aggregated
rawdata Blob List of 60 floats containing raw data Due to excessive storage needs minute values have been aggregated.
Retrieved from "https://www.sicdb.com/wiki/index.php?title=Float_Data_Hourly&oldid=226"